Hello everybody,
Based on the kernel from DooMLoRD and FXP and wanting to make a more clean kernel in relations to Stock Kernel and add some personal changes, I make my own kernel that I am posting below.
He is based on 4.0.2.A.0.61_62 source kernel, and adding the follow changes:
v1.0:
New Governor Option:
SmartAssV2
Smartass
Smoothass
BrazilianWax
Interactive
Savaged-Zen
Scary
I/O Schedulers:
Noop (default)
Anticipatory
Deadline
CFQ
Overclock option to 1.9 Ghz
Enabled SWAP support
Enable some file systems:
EXT2
EXT3
EXT4
NTFS (Read & Write)
CIFS
DoomKernel Ramdisk:
With autorooting (prerooted)
init.d scripts/binaries execution support
support /sd-ext backup/restore
modCWM-v04 TouchEdition Recovery
and other (see http://forum.xda-developers.com/showthread.php?t=1172885 for full changelog of DoomKernel Ramdisk)
Default Sony Xperia boot logo.
v1.1:
Have the same features that v1.0, only bug fix on compiler configuration.
v1.2:
Improve battery life
Change Sony source code base, now base on 4.0.2.A.0.61_62 source
v1.3:
Great improve of battery life by disable NETWORK_FILESYSTEMS (CIFS and NFS)
v1.4:
Enable CPU undervolting options (the kernel frequencies is not undervolted, but you can undervolt (recommend using IncrediControl)
WiFi undervolting
v1.5:
Disable duplicate voltage scaling frequency, for better manager of cpu frequency and better battery life.
From FreeXperia: salvage some more ram by removing unused pmem_adsp_cache
From FreeXperia: salvage some more ram by removing unused pmem_audio
Disable verbose procfs contents
Adding scripts for better battery life and overall performance:
Internet speed tweaks
Misc kernel tweaks
Battery tweaks
Journali smoff
Defrag DB
Loopy smoothness
Sick
Zipalign
Zipalign Defrag DB
Change sched_latency_ns to 600000
Change sched_wakeup_granularity_ns 400000
v1.6:
WiFi Power Management Tweak
Increase CPU voltage of some frequency for better stability
CPF Frequency Tweaks and Enable CPU AVS (Adaptive Voltage Scaling)
Revert: change sched_latency_ns to 600000
Revert: change sched_wakeup_granularity_ns 400000
Enable EXT3 and EXT4 Posix ACL and XATTR
Disable YAFFS ECC Check
Enable YAFFS empty lost and found folder at mount
Disable YAFFS block refreshing
Change pll2_fixup onverclock control
New compiled WiFi modules
WiFi modules included in Ramdisk
In general this version is for improve the battery life and resolve the problems of WiFi don't work because of user using not default WiFi modules (DoomKernel Modules)
Ps. For user with WiFi don't work just restart twice.
v1.7:
Enable 1200Mhz frequency
Add IO SCHEDULE BFQ
Add CM torch interface (base on Blendkernel v02 from Jason Stain)
Use disable_irq_nosync() from within irq handlers (base on Blendkernel v02 from Jason Stain)
Prepare I/O context code for BFQ
Custom tweaks in kernel config
v1.8:
Revert change in acceleration sensor support. Fix acceleration sensor error.
v1.9:
Upgrade busybox to fix the execution of user script (init.d).
Remove some scripts that were causing problems.
The instalation is the same from other kernel:
Code:
fastboot flash boot boot.img
PS.: for CPU undervolting I recomend using IncrediControl (https://market.android.com/details?id=com.incredicontrol)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I want to warn that THIS IS A TEST KERNEL, so he may have some bug.
By
Adriano Martins
-----------------------
Source at https://github.com/AdrianoMartins
I'm testing... thanks.
Just flashed it! I will report soon! Thanks for sharing!
Subscribed....
Sent from my LT15i
kindly tell me what do u mean by a
less "invasive" kernel in relations to Stock Kernel
Click to expand...
Click to collapse
i am growing tired of this... people just use our sources without even bothering to ask first, use the exact same features, rebrand as their own work and if something problematic is found happily blame/point the finger at us...
try get some more features to Xperia 2011 device kernels...
instead of floating same/similar kernels help out in searching for the battery drain issue... if anyone is at all bothered atleast help in testing...
or if no one is interested then atleast tell me that way i wont spend my time working on ARC... wait may be i should stop all kernel work for ARC...
I have an early observation to report, that seems quite interesting.
I lost 8% in 57 minutes using this kernel and BetterBatteryStats app indicates that the phone isn't sleeping properly and there is an entry in Kernel Wakelocks I have never seen in stock kernel, deleted_wake_locks.
Hope this helps!
DooMLoRD said:
kindly tell me what do u mean by a
i am growing tired of this... people just use our sources without even bothering to ask first, use the exact same features, rebrand as their own work and if something problematic is found happily blame/point the finger at us...
try get some more features to Xperia 2011 device kernels...
instead of floating same/similar kernels help out in searching for the battery drain issue... if anyone is at all bothered atleast help in testing...
or if no one is interested then atleast tell me that way i wont spend my time working on ARC... wait may be i should stop all kernel work for ARC...
Click to expand...
Click to collapse
Doom, although it's not my place to say anything, I figured I'd go ahead and do it anyway.
I understand your frustration because I know how much work you put in your kernels and you are without a doubt one of the most active developers.
And I have to agree that you are the "leader" around here, in the sense that if you don't introduce new features for our phones, no one else does.
The only thing that I wanted to point out is that, in my view, you shouldn't be disappointed when people use your work, if of course they credit you properly,
which I feel is the case here. Adrianom compiled this kernel for his personal use and thought he'd share, which objectively is not such a bad thing.
It's certainly not something that should make you feel like giving up on the Arc altogether, as this would be very sad.
And maybe also consider the way you started compiling kernels using zdzihu's sources and ramdisk (legendary Power To The People )
and slowly learned and shifted to your own sources...
So maybe that will be the case for the people currently using your sources.
I am sure that at the end of the day, your work is truly appreciated the way it deserves to be.
Just my 2 cents.
DooMLoRD,
DooMLoRD said:
kindly tell me what do u mean by a
Click to expand...
Click to collapse
I just wanted to say I wanted a cleaner kernel compared to Sony, that's all. I did not want at all say that something is wrong with your kernel.
DooMLoRD said:
i am growing tired of this... people just use our sources without even bothering to ask first, use the exact same features, rebrand as their own work and if something problematic is found happily blame/point the finger at us...
Click to expand...
Click to collapse
Here I think you're wrong, I did not say anything was wrong with your kernel, on the contrary, said even that was based on his and the FXP kernel, and I believe that I don't have to ask permission to use an Open Source code, you ask Sony? Google? Linus? I think not.
DooMLoRD said:
try get some more features to Xperia 2011 device kernels...
Click to expand...
Click to collapse
I don't want new features, that is the point....
DooMLoRD said:
instead of floating same/similar kernels help out in searching for the battery drain issue... if anyone is at all bothered atleast help in testing...
Click to expand...
Click to collapse
I am searching... on my own, or do you think that a developer community should consist of only one person developing and the others sending it logs?
I think you misunderstand my post, I just wanted to provide something that I'm using.
This is the principle of an open source system, people can move the way they want it. And that's what I'm doing.
Just wanted to help someone who wants the same as me.
By.
iridaki said:
I have an early observation to report, that seems quite interesting.
I lost 8% in 57 minutes using this kernel and BetterBatteryStats app indicates that the phone isn't sleeping properly and there is an entry in Kernel Wakelocks I have never seen in stock kernel, deleted_wake_locks.
Hope this helps!
Click to expand...
Click to collapse
Thanks for the feedback.
I don't have this problem but, I'll see what can be.
iridaki said:
Doom, although it's not my place to say anything, I figured I'd go ahead and do it anyway.
I understand your frustration because I know how much work you put in your kernels and you are without a doubt one of the most active developers.
And I have to agree that you are the "leader" around here, in the sense that if you don't introduce new features for our phones, no one else does.
The only thing that I wanted to point out is that, in my view, you shouldn't be disappointed when people use your work, if of course they credit you properly,
which I feel is the case here. Adrianom compiled this kernel for his personal use and thought he'd share, which objectively is not such a bad thing.
It's certainly not something that should make you feel like giving up on the Arc altogether, as this would be very sad.
And maybe also consider the way you started compiling kernels using zdzihu's sources and ramdisk (legendary Power To The People )
and slowly learned and shifted to your own sources...
So maybe that will be the case for the people currently using your sources.
I am sure that at the end of the day, your work is truly appreciated the way it deserves to be.
Just my 2 cents.
Click to expand...
Click to collapse
Iris u have known me since X10 days... so thanks for ur post...
adrianom said:
DooMLoRD,
I just wanted to say I wanted a cleaner kernel compared to Sony, that's all. I did not want at all say that something is wrong with your kernel.
Here I think you're wrong, I did not say anything was wrong with your kernel, on the contrary, said even that was based on his and the FXP kernel, and I believe that I don't have to ask permission to use an Open Source code, you ask Sony? Google? Linus? I think not.
I don't want new features, that is the point....
I am searching... on my own, or do you think that a developer community should consist of only one person developing and the others sending it logs?
I think you misunderstand my post, I just wanted to provide something that I'm using.
This is the principle of an open source system, people can move the way they want it. And that's what I'm doing.
Just wanted to help someone who wants the same as me.
By.
Click to expand...
Click to collapse
very interesting point of view...
this is not the first time such a thing is happening and may be i am a bit edgy today... anyways...
FYI, kindly read
12. Using the work of others.
Click to expand...
Click to collapse
REF: http://forum.xda-developers.com/announcement.php?f=965
regards,
DooMLoRD
iridaki said:
I have an early observation to report, that seems quite interesting.
I lost 8% in 57 minutes using this kernel and BetterBatteryStats app indicates that the phone isn't sleeping properly and there is an entry in Kernel Wakelocks I have never seen in stock kernel, deleted_wake_locks.
Hope this helps!
Click to expand...
Click to collapse
iridaki,
I think I found the problem, I compile a new version and did some testing for a while and did not generate any deleted_wake_locks.
I would appreciate if you can test again. The boot image is on attach.
Thank you again for your feedback.
adrianom said:
iridaki,
I think I found the problem, I compile a new version and did some testing for a while and did not generate any deleted_wake_locks.
I would appreciate if you can test again. The boot image is on attach.
Thank you again for your feedback.
Click to expand...
Click to collapse
That was fast! I'll update this post with my findings!
Thanks!
iridaki said:
That was fast! I'll update this post with my findings!
Thanks!
Click to expand...
Click to collapse
It would be nice if you could clear the cache before also, to eliminate any problem of applications that may be interacting with the kernel.
Thanks.
adrianom said:
It would be nice if you could clear the cache before also, to eliminate any problem of applications that may be interacting with the kernel.
Thanks.
Click to expand...
Click to collapse
Yeaps, I always do that after flashing kernels, as some of my apps FC when I switch kernels. It is my advice to everyone:
clear cache and dalvik cache immediately after flashing a new kernel.
iridaki said:
Yeaps, I always do that after flashing kernels, as some of my apps FC when I switch kernels. It is my advice to everyone:
clear cache and dalvik cache immediately after flashing a new kernel.
Click to expand...
Click to collapse
I think version 1.1 was the same problem that version 1.0.
I was led to understand that was not happening because of what I think is a bug in BetterBatteryStats. It change the name of the wifi wakelock to deleted_wake_locks when wifi is disable. I'll keep looking, now for the wifi problem.
Thanks.
iridaki said:
Yeaps, I always do that after flashing kernels, as some of my apps FC when I switch kernels. It is my advice to everyone:
clear cache and dalvik cache immediately after flashing a new kernel.
Click to expand...
Click to collapse
+1
I'll test your kernel for a few days and give a feedback.
I flashed to v1.1 and doing a full charge and delete batterystats to ensure freshness of battery.
Sent from my LT15i
superlimau said:
I flashed to v1.1 and doing a full charge and delete batterystats to ensure freshness of battery.
Sent from my LT15i
Click to expand...
Click to collapse
Just bear in mind that when you wipe batterystats, you might notice battery percentage decreasing faster at first or inconsistently, so test the kernel for at least 2 battery cycles.
iR¡[email protected]!* via Tapatalk
Doing so now.
Sent from my LT15i
Made test with 1.0. I think battery drain here too.
my settings that i only changed is:
122Mhz - 1.4Ghz
smartass v2
com.sonyericsson.android.server.dormant = 642 wakeups What is it?
tRippinthehead said:
com.sonyericsson.android.server.dormant = 642 wakeups What is it?
Click to expand...
Click to collapse
It's Fast Dormancy, a network feature. Does your provider support it?
iR¡[email protected]!* via Tapatalk
Related
Hey everyone, welcome to viperMOD for the EVO, Incredible, Nexus One, Desire GSM, Thunderbolt, Nexus S, Nexus S 4G, Desire HD, and Inspire 4G. Many people are having great success with this mod and I hope you enjoy my work
I would like to turn this into an app! If someone would like to help out that has Java knowledge, please contact me!
What does this do?
Kernel developers make their kernels to be "universal". By universal, they want the kernel to work on as many phones as possible so they may only mildly undervolt. However, some phones can handle a more aggressive undervolt. Some can't. viperMOD allows you to undervolt to your choosing for better battery life or allow you to overvolt to make your phone more stable.
How do I run this?
Once you flash the .zip go into your Terminal app (I use Android Terminal Emulator set to 10pt font) and type:
su
vipermod
I really only use Terminal for my mod and there is something really cool you can do with Android Terminal Emulator (and maybe others). Menu > Preferences > Initial Command > Press Enter and type su > Press Enter again and type vipermod
Every time you start Terminal now, it will open right into viperMOD. You can quickly exit by pressing Enter if you need to use Terminal for something else
UPDATE 6/14
viperMOD v3 beta RC2.4 is live!
Fixed some coding that was giving errors on certain ROMs and phones. Everyone please update to this!
Please see the updated FAQ and changelog for more information!
UPDATE 5/31
viperMOD v3 beta RC2.3 is live!
MUCH better support for NS/NS4G Netarchy kernels and other enhancements!
Please see the updated FAQ and changelog for more information!
UPDATE 5/29
viperMOD v3 beta RC2.2 is live!
Initial support for Desire HD/Inspire 4G and more!
Please see the updated FAQ and changelog for more information!
{
"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"
}
Please see viperboy.tiamat-dev.com for downloads, more information, changelog, and FAQ!
You can find the answers to all of your questions there!
Feel free to support this mod with a userbar in your sig
Credit to:
- snq_ for the VDD support
- Cayniarb for his awesome Tiamat kernel, hosting, and website!
- Netarchy for his amazing guidance and patience!
- My IRC friends ekarelis, bigrushdog, and morph3k for all their help!
- Ziggy for the adjustable sysfs interface
- Anyone who has done testing for me or helped me at all
- Everyone who contributes to Android development
- Let me know if I left anyone out!
FAQ
[Q] Will this work on Sense kernels?
[A] Technically, yes. None of the current Sense kernels support the sysfs interface but a few of ziggy's old kernels do. I don't know if anyone still runs his kernels but if you do and you want to see it supported, please contact me. You can also compile your own 2.6.32 Sense kernel and build in the sysfs interface. To do so, please read here (thanks chad0989!)
Reserved...
What kind of battery life are we looking at here? There's so many variables as to what affects life. I can chew through my 1500 in 24 hrs or 10, it depends.
I'll try it out, what kernel is this based off of?
shoman24v said:
What kind of battery life are we looking at here? There's so many variables as to what affects life. I can chew through my 1500 in 24 hrs or 10, it depends.
I'll try it out, what kernel is this based off of?
Click to expand...
Click to collapse
It's hard to say because, as you said, it depends what you do with your phone. I have noticed that I get a full day out of my phone when I never used to before. Just to give you an idea though, here is what ffolkes found out after some testing...
ffolkes said:
I spent hours (well, days, no, a week actually) methodically doing stability tests and tweaking voltages for all 24 frequencies. I then went back to a fresh install of CM7, installed Tiamat 3.3.7 and used my Evo for about 30 minutes - doing whatever I normally do, few texts, lots of RSS reading, browser, it isn't important since this is a relative and not absolute test. I then took 10 samples from that time in Battery Monitor Widget and averaged them, resulting in 485mA. Then I installed my customized voltages, and repeated the experiment, and the average was 374mA. That equates to about a 23% decrease in power consumption.
Click to expand...
Click to collapse
In my eyes, anything I can do to get a little bit more battery life is great and this mod will help with that
Is this.something that you would flash over the kernel or for devs to add in while they are creating them?
bradm23 said:
Is this.something that you would flash over the kernel or for devs to add in while they are creating them?
Click to expand...
Click to collapse
Flash over a kernel. Basically, it adds a script to /system/etc/init.d that loads these undervolt values everytime your phone starts up.
Interesting. I think I will keep an eye on this one!
Sent from my ADR6300 using XDA Premium App
So, is it not possible to do make this mod available to sense ROM kernels, or just involves doing things no one has done yet?
dscribe said:
So, is it not possible to do make this mod available to sense ROM kernels, or just involves doing things no one has done yet?
Click to expand...
Click to collapse
You just need a kernel with the HAVS sysfs interface is all. Would take about 5 minutes to put into a sense kernel. It will be in a future 2.6.37 sense kernel I put out if I ever figure out the funky artifacting issue.
dscribe said:
So, is it not possible to do make this mod available to sense ROM kernels, or just involves doing things no one has done yet?
Click to expand...
Click to collapse
chad0989 said:
You just need a kernel with the HAVS sysfs interface is all. Would take about 5 minutes to put into a sense kernel. It will be in a future 2.6.37 sense kernel I put out if I ever figure out the funky artifacting issue.
Click to expand...
Click to collapse
It could work with a Sense kernel, actually. I just didn't make one for the EVO because Calkulin already did that in his own thread. But I will get it working on Sense for the Incredible for you guys.
Looks like I need 5 Sense testers now!
-viperboy- said:
Looks like I need 5 Sense testers now!
Click to expand...
Click to collapse
I'll be happy to test it for ya.
dscribe said:
I'll be happy to test it for ya.
Click to expand...
Click to collapse
Sent you a PM. Still need a few more testers!
I was able to drop it 50mV going past that would booted but would hot-boot instead of booting all the way.
Still happy. Now to test how much more time I have on my battery
Thanks again viperboy.
cuban11182 said:
I was able to drop it 50mV going past that would booted but would hot-boot instead of booting all the way.
Still happy. Now to test how much more time I have on my battery
Thanks again viperboy.
Click to expand...
Click to collapse
No problem like I said, every phone will handle this mod differently. I don't know if this has happened to anyone in the Incredible forum but some people in the EVO forum have a problem that they can't flash any custom kernel because the kernel is too undervolted so I made an overvolt script that I will post over here as well.
Confused
Is this mod only involving the making of flashable scripts that lower voltage values?
Does it involve anything like modifying kernels, basically making them HAVS kernels, if they are not currently?
Who else wants to help me test?! I need people that are running a Sense-based ROM!
dccoh said:
Is this mod only involving the making of flashable scripts that lower voltage values?
Does it involve anything like modifying kernels, basically making them HAVS kernels, if they are not currently?
Click to expand...
Click to collapse
No, the kernel you are using needs to have on-the-fly HAVS editing built in.
-viperboy- said:
It could work with a Sense kernel, actually. I just didn't make one for the EVO because Calkulin already did that in his own thread. But I will get it working on Sense for the Incredible for you guys.
Looks like I need 5 Sense testers now!
Click to expand...
Click to collapse
-viperboy- said:
No, the kernel you are using needs to have on-the-fly HAVS editing built in.
Click to expand...
Click to collapse
Which no sense kernels do, with the exception of some of the ziggy ones floating around somewhere. I've long since abandoned my 2.6.32 source in favor of 2.6.37 (I only have time for one at a time), but there is an odd artifacting issue that has prevented me from releasing a sense version.
If someone wants to put out a 2.6.32 sense kernel with the sysfs interface here's everything you need:
My 2.6.32 source:
https://github.com/Chad0989/incredikernel
Sysfs interface commit:
https://github.com/Chad0989/android_kernel_common/commit/15d469a1aabc76d549c94bc7150678fe808a51d8
Note that 2.6.32 its acpuclock-scorpion.c instead of acpuclock-qsd8x50.c
I can test sense for you if you would like
Putting this up for those who've been inquiring...I simply integrated bits & pieces for the legend to improve what is already an awesome rom. I take no credit for this. Doesn't hurt to hit the thanks button though if this helps .
{
"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"
}
How's this different from CM7?
2.6.35 kernel (boots by default to 768/256-interactive; max=806, min=120)
smartass & smartass2 governors
compache/swap
deodexed & zip-aligned
tweaks for deodexed rom and sd read-ahead (3072 by default)
removed rom manager & some default themes/wallpapers
moved file manager to /data/app
modified lock screen icons
flying-in menu animations
TGF's notification bar (notbar) patch integrated
What doesn't work/untested?
wifi tethering - activating them produces an error & breaks wife, in which case, a reboot is required
gps
Is this faster than CM?
can't claim that as i don't see a big jump in quad/linpack scores, though there are improvements & it does feel snappier (I may be biased though). you decide...
full rom here: DOWNLOAD
flash attached:
drowningkernel-8-9-1_mod1.zip
kernel w/ the last three items above included for flashing unto cm7
drowningkernel-8-9-1_mod.zip
just the kernel
CAUTION
do backup before doing anything
see alex' comments, post #9
if you encounter reboots/freeze (not getting this myself though) & wanna revert to your original/stock kernel, simply advance restore boot only
usual liability disclaimer applies
feedback is/are most welcome! if you have questions on TGF's notbar patch, please post on that thread instead.
CREDITS
cyanogen/cm team
alex
drowningchild (kernel)
tosha15 (compatible modules)
TGF
Serris (animations)
ZduneX25 (lockscreen icons)
Thx maxq1, I'll download but will test it only after I get my Legend repaired
Rapier said:
Thx maxq1, I'll download but will test it only after I get my Legend repaired
Click to expand...
Click to collapse
I think this time you took the big hammer and hit it hard
good work man, going to check this out........
smartsreenath said:
I think this time you took the big hammer and hit it hard ..
Click to expand...
Click to collapse
Yeah digitizer is defective...it seems like it happens this after a while (1 year or so). I saw alot of people complaining about this also movies on YouTube showing the issue. I'l send it in service next week I hope
The drowningkernel-8-9-1_mod.zip works fine with CM7.1.0 for me. THX a lot!
I like your lockscreen-icons and the statusbar-patch, but not the flying-in-animation, so I flashed the non-modified one.
What governors do you prefer? I'm using interactive, but never had a smartass/smartass2 kernel on my phone. Does one of these two give me advantages over interactive?
Or can you give me some details about smartass/smartass2 Min-Max-values for the legend?
I have constant cpu usage of 50-75% with this rom :-(
What governors do you prefer? I'm using interactive, but never had a smartass/smartass2 kernel on my phone. Does one of these two give me advantages over interactive?
Or can you give me some details about smartass/smartass2 Min-Max-values for the legend?
Click to expand...
Click to collapse
you could learn more about it here. i'm using 806/122-smartass2. if you try to underclock below stock 245, it seems only the smartass governors give a quick response from sleep.
Suppe123 said:
I have constant cpu usage of 50-75% with this rom :-(
Click to expand...
Click to collapse
which governor are you using?
Just a small comment regarding kernel 2.6.35:
In my tests 2.6.35 was not significantly (or at all) faster than .32, neither could I observe improved battery life.
What actually held us back implementing .35 were the crappy WLAN and missing access point drivers. The sources HTC released are significantly broken - even for their original target "Espresso", and this is still a clear violation of the GPL (the sources they used to compile tiwlan_drv for Espresso/Legend are not at all equivalent to what they released).
That being said, if you don't care about WLAN at all you can use 2.6.35. I seriously wouldn't recommend that kernel though and would request you to add a warning to your post to make sure people don't start to complain about random reboots in CyanogenMod.
Thanks man,looks great will test it soon.
Sent from my HTC Legend using XDA App
File does not exist!
Sent from my HTC Legend using XDA App
if you deodex rom ... take data space after install ... cm 7 179mb free data ... your rom ... ... less
Bad bad bad...
^ i couldn't quite get what you're saying, man. did it drop down to <100mb?!? i'm no expert or dev but is that an effect of deodexing? if any, i just moved file mananger (a couple of kb, i guess). in any case, most of you will be using some sort of apps/data..2..sd/ext anyway. kindly enlighten...
File does not exist!
Click to expand...
Click to collapse
hmm..link works just fine from where i'm at..try again, bro
Sesme said:
if you deodex rom ... take data space after install ... cm 7 179mb free data ... your rom ... ... less
Bad bad bad...
Click to expand...
Click to collapse
Hey E.T, you drunk bro' ?
Okay,now it's working I think Megaupload was just down....Okay I test it now
Sent from my HTC Legend using XDA App
So bad that Wifi is crashing all the time
stevenstrike said:
So bad that Wifi is crashing all the time
Click to expand...
Click to collapse
update your radio!!!
maxq1 said:
^ i couldn't quite get what you're saying, man. did it drop down to <100mb?!? i'm no expert or dev but is that an effect of deodexing? if any, i just moved file mananger (a couple of kb, i guess). in any case, most of you will be using some sort of apps/data..2..sd/ext anyway. kindly enlighten...
Click to expand...
Click to collapse
What he wants to say is that, if you deodex rom, there is more space used in system since instead of having apk+odex as separate files you put the odex inside the apk thus ocuppying more space. So for a deodexed ROM you have less space remaining.
Of course since most of us are using some sort of data2ext this is no big deal, I just wanted to "translate"
Sesme said:
update your radio!!!
Click to expand...
Click to collapse
Huh ? This is a known issue caused by crappy Wifi drivers given by htc for Kernel .35 :
Just a small comment regarding kernel 2.6.35:
In my tests 2.6.35 was not significantly (or at all) faster than .32, neither could I observe improved battery life.
What actually held us back implementing .35 were the crappy WLAN and missing access point drivers. The sources HTC released are significantly broken - even for their original target "Espresso", and this is still a clear violation of the GPL (the sources they used to compile tiwlan_drv for Espresso/Legend are not at all equivalent to what they released).
That being said, if you don't care about WLAN at all you can use 2.6.35. I seriously wouldn't recommend that kernel though and would request you to add a warning to your post to make sure people don't start to complain about random reboots in CyanogenMod.
Click to expand...
Click to collapse
BTW Radio has nothing to do with wifi.
Edit : Plus my radio is up to date !
Edit Plus : I tried this rom (K.35) and official 7.1 Rom (K.32) and i found that the both kernels have the same issue, being on K32 or K35 is the same thing for me, i got the same random crashes, which was not the same thing on the old RC1 (which just sometimes crashes when you just power on wifi with sync enabled).
Too bad, Cyanogen 7.1 passed "stable" with this bug.
^ have you tried this, bro?
{
"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"
}
ARM.
The Next Reliable Managed Architecture.
NOTE
- ARM or Android Reliant Management, Aims to bring full battery saving to our devices and add features not introduced. This would of course reduce battery hunger and at the same time, sustain the performance of our phones.
THIS IS A MODDED Kernel with Many fantastic features within. I am not responsible or credited for the kernel source codes whatsoever. I only modify the kernel to my needs and add more features not available from the base which will be beneficial to all of us. This Kernel is GPL Compliant and is fully Open Source. Please provide a CLEAR Credit should you use this Source as your base.
Click to expand...
Click to collapse
- Undervolted Clock values for more battery life
- Various Tweaks In Kernel
- Optional OC
- Each Clock Speed fully utililises its Voltage
- Powersave Tweaks on various modules
- Dimmer LED Lights for more Energy savings
- Lower Battery Consumption
- Maximised Minimal Brightness ! >v5.10 !
- UnderClocked minimal value to <300MHz
Click to expand...
Click to collapse
Source Code Distribution
Github [CM] - Source
Github [Stock] - Source
===============CHANGELOG=================
Base : CyanogenMod 10
Maintainers : nicholaschw & JaredMLG
v5.06
- Initial Release
v5.11
- Fixed 5.10 Wakelock Bug
v5.11a
- Fixed Issues on Source
- Final Compile for KU Only Source
- Tweaked 200Mhz again
v5.12b
- Changed Source for v30B
- Removed v5.12a Commits
- Compile with v30b Drop commit
v5.2 FINAL
Milestone Codename : EXO
- Fix OPP Segmentation Fault
- Fully implement Smartreflex fixes
- Add Voltage Control for AOKP
- Bump down Vibration
- Added 2012 SIO Scheduler
- Re-added SmartAssV2
- Re-added InteractiveX
- Re-added OndemandX
- Fix SmartAssV2 Lags
NEXT RELEASE : v5.2
Following Release : v5.2a
Click to expand...
Click to collapse
====================
Base: Stock v30B bproj
Maintainer: nicholaschw
NOTE: ALL v0 are not released publicly.
v0.01
- Re-build from bproj source
v0.02
- Switch in toolchain to better fit source
- Fix a few compile errors
v0.03
- Integrate LED 1mA
- Integrate Minimal Brightness
- Cleaned Source
v0.04
- Update 4.4.3 tool chain
- Fix a few flickering LED bugs
- Bump up the value for OPP
- Add 1.1GHz OC
- Reduced Minimal Sleep Clock to bypass minimum limit
NEXT RELEASE : v1
Following Release : v1.1
Click to expand...
Click to collapse
Bugs + CM +
--------
- LED on errors as shown in dmesg (All CM10 versions has this)
- Setting brightness flickers the LEDs
Bugs + STOCK +
--------
- LED on errors as shown in dmesg (All CM10 versions has this)
- Setting brightness flickers the LEDs
-Credits-
CyanogenMod, for providing AND fixing the source codes actively
YOU, Readers, for providing me a place to allow you to give me suggestions
Xonar, For assisting in many parts of the modifications
cyclon, for introducing new modifications
Google, For allowing me to identify whatever errors i face.
> XDA Community, Giving comments on whatevers best for implementations
This Thread is Started due to our previous moderator, Reinbeau who suggested not to re-open the old thread and instead, start a fresh one.
ANY FLAMING OR CRITICISM WILL BE REPORTED.
ARM., Is not to be mistaken with ARM. ARM. Is not related to ARM Whatsoever in terms of name.(We use ARM for our processor, so we are related somehow abit.)
+DO NOT MIRROR+
EVERYTHING IS GOING ACCORDING TO DATE OF RELEASE.
How To Install
- Download the flashable zip below
- Put it into your sdcard (Anywhere you like. Just remember its location)
- Boot into recovery
- Wipe cache, Dalvik Cache (NO NEED TO WIPE DATA UNLESS YOU WANT TO)
- Install the zip package
- Reboot
- Enjoy the Excitement!
Link List - CYANOGENMOD BASED
AVAILABLE ON ROM MANAGER!
ARM-Project-v5.06.zip - 4.68 MB
ARM-Project-v5.10.zip - 4.68 MB
ARM-Project-v5.11.zip - 4.68 MB - *Current Most Stable*
+ Should there be wakelocks, Flash the Official CyanogenMod and then flash the kernel.
+ Flashing on other CyanogenMod-based ROMs are experimental. Always ask in the thread of the ROM whether it works with ARM. . Never attempt anything that fails.
EXPERIMENTAL/NIGHTLY BUILDS
==================
All Builds below are experimental. Flash at your own risk.
ARM-Project-v5.10N2.zip - 4.68 MB
ARM-Project-v5.10N3.zip - 4.68 MB
ARM-Project-v5.12b.zip - 4.68 MB
Link List - STOCK BASED
None yet
EXPERIMENTAL/NIGHTLY BUILDS
==================
All Builds below are experimental. Flash at your own risk.
None yet
FAQs
+ Q: Whats the difference?
A: Read the disclaimer.
+ Q: Will I get worse performance than the Official CyanogenMod Kernel?
A: It depends on what commits are added. My Kernel only fixes bugs i can fix and which are unsolved and Of course, I will add more features not available in CyanogenMod Official
+ Q: What makes the stock kernel different?
A: You get goodies, and furthermore, better battery life and performance in this project.
After I flashed your kernel, I noticed Google Now's voice response does not work anymore - English (United States) is set as default.
chuayx1 said:
After I flashed your kernel, I noticed Google Now's voice response does not work anymore - English (United States) is set as default.
Click to expand...
Click to collapse
The point is that CM10 Nightlies dont even have Google Now Working properly. Besides, tell me how Google Now links to the Kernel. What, it needs more power? Note that Google Now may or may not work on each CM10 Build.
Afternoon.
nicholaschw said:
The point is that CM10 Nightlies dont even have Google Now Working properly. Besides, tell me how Google Now links to the Kernel. What, it needs more power? Note that Google Now may or may not work on each CM10 Build.
Click to expand...
Click to collapse
Most of the nightlies have the Google Now working....
@skate4life stop the hate dude, if you don't like Nick's work, just ignore him. Maybe he is crazy maybe he is not, but one crazy in this forum is enough.
sent from my Optimus Black V28c
chuayx1 said:
Most of the nightlies have the Google Now working....
Click to expand...
Click to collapse
I will see to that issue if its related to my kernel. But one thing sure is my kernel stops BLN from working.
Sent from my GT-I9300 using xda app-developers app
chuayx1 said:
Most of the nightlies have the Google Now working....
Click to expand...
Click to collapse
Sry for OT but apparently Google Now voice thingamabob does not work for me and im on stock kernel.Weird cuz the first few nightlies has it working
EDIT: I found a fix,First set your language in the language and input settings to Engish(United States)
then set the language of Google Now to English(US).After that,it should work with or without ARM kernel.Thanks for trying the kernel though...
re4lsk said:
@skate4life stop the hate dude, if you don't like Nick's work, just ignore him. Maybe he is crazy maybe he is not, but one crazy in this forum is enough.
sent from my Optimus Black V28c
Click to expand...
Click to collapse
Because of this I really wonder if this is really a custom kernel or not. *refers to Jellybam thread*.
chuayx1 said:
Because of this I really wonder if this is really a custom kernel or not. *refers to Jellybam thread*.
Click to expand...
Click to collapse
It is because the kernel now has a noticeable feature from CM kernel. It has a dimmer Backlight.
Sent from my GT-I9300 using xda app-developers app
nicholaschw said:
It is because the kernel now has a noticeable feature from CM kernel. It has a dimmer Backlight.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
The dimmer backlight only works fine if you also mod the rom. So i would (like i did) release a rom with kernel.
I have a link somewhere how to do it, someone on xda is the original source for backlight modifications, if you're interested i can send you the diffs for the mod.
cyclon1978 said:
The dimmer backlight only works fine if you also mod the rom. So i would (like i did) release a rom with kernel.
I have a link somewhere how to do it, someone on xda is the original source for backlight modifications, if you're interested i can send you the diffs for the mod.
Click to expand...
Click to collapse
Its better if you inject it into your ROM. That way i do not have to add a ROM into this thread. I told myself to fully work ONLY on kernels and thus this thread will only be purely kernels.
Hope you understand
So, inject my kernel into your ROM if, you want to combine both of our works. You should notice Dark Mod has still a bright backlight,which if you add this, will benefit into a darker environment
...i'm not trying to be pushy or anything, but will there be a chance of OC to 1.3 just like the Zeus Rom??
xX3m0Xx said:
...i'm not trying to be pushy or anything, but will there be a chance of OC to 1.3 just like the Zeus Rom??
Click to expand...
Click to collapse
Yes. Definitely.
Please try this out, Its been tested. I just need to see if Underclocking works to reduce battery drain.
This Nightly has reduced battery drain with 200MHz Underclocking
ARM-Project-v5.10N2.zip - 4.68 MB
nicholaschw said:
Its better if you inject it into your ROM. That way i do not have to add a ROM into this thread. I told myself to fully work ONLY on kernels and thus this thread will only be purely kernels.
Hope you understand
So, inject my kernel into your ROM if, you want to combine both of our works. You should notice Dark Mod has still a bright backlight,which if you add this, will benefit into a darker environment
Click to expand...
Click to collapse
The dark mod sets the brightness in aat2870_bl.c
val = (unsigned char) (level * 0x1F / 255);
val = 0xE0 | val;
aat2870_write_reg(client, AAT2870_REG1, val);
so we set in the register 0XE0 as lowest value for the brightness.
This is according to the aat2870 doku (http://www1.futureelectronics.com/doc/ANALOGICTECH - AATI/AAT2870IUW-DB1.pdf)
the absolute lowest technically possible value for the chip.
So, no, nothing is darker than dark mod
Except you use screen filters, but that wont save battery.
There are some really interesting information about ALS, and other things in the document. You'll realize that the driver is badly written and the hardware is... not assembled as optimal according to the document. lg should have used an additional cheap part of hardware for the als....
nicholaschw said:
Yes. Definitely.
Please try this out, Its been tested. I just need to see if Underclocking works to reduce battery drain.
This Nightly has reduced battery drain with 200MHz Underclocking
ARM-Project-v5.10N2.zip - 4.68 MB
Click to expand...
Click to collapse
After reading your posts history...well, can I trust your words on your developing?
I've flashed this kernel once more, I hope you're really committed and not repeat the same mistakes as said by the others on your previous thread..
All 4 touch LED buttons blue light up when one key is pressed. That's a bug. And if you can make an option somewhere to turn the entire front lights off/on at free will maybe you can try it. It it flickers when it's turned on from standby mode. Also, the screen getting brighter for 1 sec before returning to normal when the screen is turned on from standby mode, maybe that can be fixed too. I'm not a dev, but i'm testing out all.
have set your 200Mhz for underclocking, but I think it's best to leave the 1000Mhz clock frequency for those who don't wish to overclock their device - 900Mhz is what i'm using now, and not everyone might want to be on 1100mhz. just my 2 cents.
nicholaschw said:
ARM-Project-v5.10N2.zip - 4.68 MB
Click to expand...
Click to collapse
One question: what's not working in this? Cause there's just "LED on errors as shown in dmesg (All CM10 versions has this)" in OP... and last time I got SOD...
So I asked.
chuayx1 said:
All 4 touch LED buttons blue light up when one key is pressed. That's a bug. And if you can make an option somewhere to turn the entire front lights off/on at free will maybe you can try it. It it flickers when it's turned on from standby mode. Also, the screen getting brighter for 1 sec before returning to normal when the screen is turned on from standby mode, maybe that can be fixed too. I'm not a dev, but i'm testing out all.
Click to expand...
Click to collapse
... i'm having the same exact problems... hopefully, this will be fixed soon
Sent from my LG-P970 using xda premium
nicholaschw said:
ARM.
The Next Reliable Managed Architecture.
NOTE
- ARM or Android Reliant Management, Aims to bring full battery saving to our devices and add features not introduced. This would of course reduce battery hunger and at the same time, sustain the performance of our phones.
COMPATIBLE WITH (Kernel)
- ALL CyanogenMod 10 Based ROMs
Source Code - Github
Last Commits: 6 December 2012
Screenies
Base : CyanogenMod 10
Maintainer : nicholaschw
v5.06
- Re-Initialized Release
- Initital Public Release
- Reduce both White and Blue LEDs to 1mA
- Added SmartAssV2
- Fixed SmartAssV2 Compiling errors
- Reduce 400MHz clock rate to 300MHz
- Reduce voltages on all clock rates
v5.10 Nightly 1
- Attempted 1.2GHz
v5.10 Nightly 2
- Removed Previous attempt for further OC
- Added 200MHz Underclocking for more battery life
Click to expand...
Click to collapse
Bugs
--------
- LED on errors as shown in dmesg (All CM10 versions has this)
-Credits-
+ CyanogenMod, for providing AND fixing the source codes actively
+ YOU, Readers, for providing me a place to allow you to give me suggestions
+ Xonar, For assisting in many parts of the modifications
+ Google, For allowing me to identify whatever errors i face.
♥ XDA Community, Giving comments on whatevers best for implementations
This Thread is Started due to our previous moderator, Reinbeau who suggested not to re-open the old thread and instead, start a fresh one.
ANY FLAMING OR CRITICISM WILL BE REPORTED.
Click to expand...
Click to collapse
The main theme to use some KERNEL is to get good speed and performance of phone.
After seeing the benchmark in ur post, it looks funny for me.
Bcoz, without using ur Kernel, I am getting the same or above benchmark of CM10 ROM, then why to use ur Kernel ?
Click to expand...
Click to collapse
Moretz Kernel 0.2.2 - Galaxy Note 8.0 EditionGT-N5110 & GT-N5100
Features:
Linux 3.0.101
Frandom
Network speed enhancements
Dynamic read ahead
CPU OC to 1.8GHz
GPU OC to 533MHz
CPU Voltage Control (OV/UV)
Tuned ZZMoove CPU governor (removed all other governors)
Intelligent CPU core hot plugging
Touchboost control, set to 800MHz
ARM CPU topology
LCD frequency switching (40Hz on screen dim, 60Hz on active)
Intelligent GPU scaling (Mali GPU control)
Lots of other fixes/tweaks
Intelligent zipalign at boot (init.d)
Intelligent sql db optimization at boot (init.d)
So, what's so special here?
A few things actually. I grabbed various code bits from many well known developers and worked some of my own magic on this build. First, I bumped the kernel up to 3.0.101 (FINAL) form kernel.org as a base on top of the stock CM 11.0 kernel. Once I pushed all of the enhancements listed above, I focused on tuning ZZMoove to balance performance and battery. I believe I've succeeded in that realm, so all other governors have been removed. This is a flash and forget kernel package. That's what makes it special ... the users do not have to do any tuning, it works, and it works well.
Credits:
Faux123, Andy P, googyanas, psndna88, ryukuri, sbrissen, Cyanogenmod team and may others. Please let me know if I missed you.
Source Code:
https://bitbucket.org/carvsdriver/android_kernel_samsung_smdk4412 (Moretz-New Branch)
Standard Disclaimer:
By flashing this you hold the developer (car vs driver) and anyone else not responsible or liable for any damage to your device, up to and including hard bricking. Basically, there's no warranty - flash at your own risk.
This release is not affiliated to CyanogenMod or Cyanogen Inc. This is my own personal work with lots of kangs from others.
This was tested with CM-11 on a GT-N5110 device. Any other devices or ROMs may not work or exhibit poor behavior. That being said, I only support use of this kernel with CM-11 and the GT-N5110.
Requirements:
Device - Samsung GT-N5110
ROM - CyanogenMod 11.0
XDA:DevDB Information
Moretz Kernel - Galaxy Note 8 Edition (N5110 & N5100), Kernel for the Samsung Galaxy Note 8.0
Contributors
car vs driver, psndna88, faux123, googyanas, AndiP, sbrissen
Kernel Special Features: GPU/CPU OC, UV/OV, UKSM, HotPlug, ARM Topology, LCD Freq Scaling, Linux 3.0.101
Version Information
Status: Stable
Current Stable Version: 0.2A
Stable Release Date: 2014-03-21
Created 2014-03-21
Last Updated 2014-07-03
Change Log:
Moretz 0.2.2 -- Upstream CM11.0 Changes Merged -- 7.4.2014
98865a3: n_tty: Fix n_tty_write crash when echoing in raw mode
7735075: mc1n2: Allow swapping of microphone ADC channels
ed8b659: smdk4412: update sound soc and codecs
5e96596: d710: build stage2 initramfs into kernel
8a5d38c: Fix CVE-2014-3153
6922ae0: Merge "synaptics_s7301: add disabling keypad" into cm-11.0
daf9635: Merge "smdk4412: cypress-touchkey - add keydisabler" into cm-11.0
fd94358: n_tty: Fix n_tty_write crash when echoing in raw mode
969b384: mc1n2: Allow swapping of microphone ADC channels
eba4e20: smdk4412: update sound soc and codecs
Moretz 0.2.1 -- Upstream CM11.0 Changes Merged -- 4.8.2014
c0dce37: dm crypt: optionally support discard requests
15b6c83: dm table: share target argument parsing functions
1886fef: dm: ignore merge_bvec for snapshots when safe
2b791d9: dm: suppress endian warnings
Moretz 0.2a -- Initial Release -- 3.21.2014
Instructions:
1. Download the flashable zip
2. Reboot into recovery
3. Flash the zip
4. Reboot
5. Done
I like to make things simple. Let your device boot up and that's it. No configuration necessary. But, if you want to screw with the CPU governor and ZZMoove settings, I made that easy for you. Just edit the zzmoove file in your init.d directory with the settings you want and reboot.
Click to expand...
Click to collapse
Code:
[CENTER][SIZE="5"][COLOR="Magenta"][B]GT-N5110 Download link:[/B][/COLOR][/SIZE]
[url]http://d-h.st/Gkd[/url]
[B]Version[/B]: Moretz-0.2.2
[/CENTER]
Code:
[CENTER]
[SIZE="5"][B][COLOR="magenta"]GT-N5100 Download link:[/COLOR][/B][/SIZE]
[url]http://d-h.st/ZyZ[/url]
[B]Version[/B]: Moretz-0.2.2
[/center]
Just a couple more things ...
Please do not post mirrors, if one is needed just let me know and I'll post one.
Please leave a review on this project by clicking here.
If you like my work, feel free to buy me a beer or pack of guitar strings by donating.
Click to expand...
Click to collapse
[/CENTER]
How to properly report bugs:
When reporting a bug, you must provide me with some very specific information so that I am able to either reproduce the problem or diagnose it based on logs. If you cannot provide information that I need, I cannot attempt fix the issue.
If the device is crashing:
Please make a copy of your last_kmsg immediately after rebooting the device.
Please make a copy of your logcat for the subsequent reboot.
Attach both files to your bug report and specifically state exactly what happens (are there steps to reproduce it?).
In all cases, please provide a logcat of when the issue occurs or specifically describe what is happening and how you can reproduce the error.
If you have any current issues prior to flashing my kernel, don't expect me to fix them.
The more detail you provide, the more helpful your bug report will be for me.
Feature Requests:
I'll make this one easy, I don't do feature requests. I used to do that, it became a real pain in the ass to keep everyone happy and the project I was working on bug free. Put simply, I put this together to work specifically for me and then decided to share it here. If at some point I decide to add new features, then I'll release new versions to you.
car vs driver said:
Reserved just in case.
Click to expand...
Click to collapse
I'm looking into building my own kernel for the konawifi because I feel like we need more kernel options, so thank you for this awesome customized kernel.
ztotherad said:
I'm looking into building my own kernel for the konawifi because I feel like we need more kernel options, so thank you for this awesome customized kernel.
Click to expand...
Click to collapse
You're welcome, that's what this one is for. Makes the device scream and battery life is excellent.
Sent from my Nexus 5 using XDA Premium 4 mobile app
car vs driver said:
You're welcome, that's what this one is for. Makes the device scream and battery life is excellent.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
freakin' nice. definitely can't wait then! thanks again for your awesome gift to the Note 8.0 family.
is n5100 model will be supported in next future ?
messi2050 said:
is n5100 model will be supported in next future ?
Click to expand...
Click to collapse
Would you be willing to test? Only reason I didn't publish for n5100 is because I don't have one to verify that I didn't break anything.
I just have to update a few configs and run a new build, let me know.
as an owner of the n5100 I´ll be very interested in your work. so my first question - will this kernel work with probam 1.3.2? maybe I could test it
redukt said:
as an owner of the n5100 I´ll be very interested in your work. so my first question - will this kernel work with probam 1.3.2? maybe I could test it
Click to expand...
Click to collapse
I suppose it should, I did a quick check and looks like that ROM uses the same base 3.0.y kernel that CM 11.0 does. The partition scheme on the devices is the same too (both devices us /dev/block/mmcblk0p5 for the boot partition) ...
There's only one real way to find out though, someone has to flash it - worst case is that it doesn't boot up.
Go ahead and give this a rip and let me know how it goes. It's the same build as the OP with the 5100 defconfig updated to include the features that I added for the 5110.
Download:
REMOVED ... SEE OP FOR DOWNLOADS
MD5:
7864a8e5eb18321c2201cba314fc7a06
If it doesn't boot, just reflash your previous ROM - that'll replace this kernel with whatever one is included there.
Yeah, kernel runs nice So I`ll kept my device on standby, make a wow raid and check the battery stats
Thx for your hard work
Assuming all goes well, I'll update the op to state that both devices are supported and working.
Sent from my Nexus 5 using XDA Premium 4 mobile app
car vs driver said:
Would you be willing to test? Only reason I didn't publish for n5100 is because I don't have one to verify that I didn't break anything.
I just have to update a few configs and run a new build, let me know.
Click to expand...
Click to collapse
i'm using original rom 4.1.2 now so i can't test it sorry
3,5 h standby time loosing NOTHING in battery percentage - full 100% So I`ll check this tomorrow and report my results
edit: very nice
{
"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"
}
edit: bug: no 3g network :/
Hmmm ... no 3G? Y'know what, I think I know why. I'll post another build for you to test in a bit.
Edit: @redukt .... give this one a rip: <EDIT>SEE OP FOR DOWNLOADS.</EDIT>
car vs driver said:
give this one a rip:]
Click to expand...
Click to collapse
3G runs now
Many thanks for your quick reply
Excellent. I'm going to update the OP and support both devices then. Thanks for the quick turn around with testing, I appreciate it.
does anybody tested it on AOSB rom?
lolek2382 said:
does anybody tested it on AOSB rom?
Click to expand...
Click to collapse
yeppp, runs with AOSB 1.3.2
car vs driver said:
Hmmm ... no 3G? Y'know what, I think I know why. I'll post another build for you to test in a bit.
Edit: @redukt .... give this one a rip: <EDIT>SEE OP FOR DOWNLOADS.</EDIT>
Click to expand...
Click to collapse
3G is working on my N5100 did I download the updated file just install a few minutes ago oh thankyou for supporting our tab the the Devs on the the better
brisK Kernel
brisK is a KitKat kernel for stock-based ROMs for the Samsung Galaxy S4 mini LTE (GT-I9195).
It aims to be faster and more a bit more battery-friendly than the stock kernel, while retaining its stability.
To prevent bloat I will only apply useful features like BLN. Adding 10 random governors and schedulers is not useful in my eyes, and is also not the goal of this kernel.
Goals
Stability: The original Samsung kernel is stable, so let's not go too far away from it. This kernel doesn't need bleeding edge code - it just works(TM).
Efficiency: Less power consumption by faster computation.
Battery: A battery drain patch is included, which is not in Samsungs original code.
Speed: Minor changes, for example: Trade some screen smoothness for less kernel overhead. Should not be noticeable, though. Also lowers power consumption slightly.
Changelog
v6 (brisk_kk-stock_2015-07-28_15-07-08_64d9234.zip)
Removed more KNOX stuff (--> This fixed some random reboots!)
Finally upgraded to new toolchain: Linaro GCC 4.9.4-2015.06 (Cortex-A15)
Thanks @impactor and @SilviuMik for providing help!
v5
Revert default IO scheduler back to CFQ
Apply changes from new released kernel source (GT-I9195_EUR_KK_Opensource.zip - I9195XXUCOA2)
Apply changes from new released kernel source (GT-I9195_EUR_KK_Opensource.zip - I9195XXUCOE4)
Older versions
v4
Fixed USB-to-PC problems by re-enabling some debugging code
v3
Users reported: USB-to-PC (MTP) doesn't work? (Logfiles appreciated)
Apply changes from Samsungs GT-I9195_EUR_KK_Opensource_Update1.zip
Replace stock Wlan module with kk_2.7_rb1.43
Various kernel config changes:
Disable various unused and debugging features
Re-enable heap randomization
Enable "Optimize very unlikely/likely branches"
Set default IO scheduler to noop
Reduce preemption from "Low-latency desktop" to "Desktop"
Disable Samsungs Rooting Restriction
Added init.d support
v2
Added OTG support (UNTESTED) - Edit: NOT WORKING YET
Removed TIMA
Change to XZ compression
Add BLN support (UNTESTED) - Edit: NOT WORKING YET
v1
Added battery drain patches
Optimize kernel for speed, not size
Preparation for init.d support
Permissive SELinux
Future plans
Add proper Prima WLAN driver - Done!
Add a few more optimizations - Done!
Add init.d - Done!
JellyBean Kernel
The old JellyBean kernel is no longer maintained, but it is stable and its uptime was above 2000 hours on my device. I published it here too, in case someone is happy with their JellyBean ROM and wants this.
Features: BLN, Battery drain patches, kernel config optimized, most debugging code deactivated
Source: https://github.com/TheBootloader/android_kernel_samsung_msm8930-common/tree/jb-stock
Awesome people
@SilviuMik for helping me getting started and providing useful tips - You rock!
@Christopher83 for his toolchains
@F4k for providing source code where I can snoop around
@junkyde for his kernel and his OTG and BLN patches
@arco68 for being another great resource
Downloads & Sources
Source code is on my GitHub.
Releases are at the bottom of this post and on GitHub.
See 2nd post if you need checksums.
PLEASE MAKE FULL BACKUP (/system TOO!) BEFORE FLASHING ANYTHING. The strangest things can happen if you don't have a backup - even if it *should* work.
Downloads are ordered from oldest to newest, so the newest release is at the bottom.
Checksums
brisK JB (brisk_jb_2014-05-16_16-40-39.zip)
MD5: 0f916929e85ae1f8d7b2d1aa8c4e5e1f
SHA256: 8cb1b01358eeb6bc7fb68bbb2fd641d5cda852b78d7e22605ffb28eba6da4156
brisK KK v1 (brisk_kk_2014-08-19_17-33-50_cd36751.zip)
MD5: 8edf28d8a2d1d89d40f8a8f1863d7b57
SHA256: aed1caf0d13ada04888e7c3a020fa6b679fc0fc36ad89678e617ae9a36d637e6
brisK KK v2 (brisk_kk-stock_2014-08-21_01-04-03_765f3f6.zip)
MD5: c004e49779f21f706e76a00233f8fb80
SHA256: df57729a66d425a970d8c8ef222edf6073e4cfc562d8dccea96f12ac0eac7aef
brisK KK v3 (brisk_kk-stock_2014-12-07_00-57-00_23da34c.zip)
MD5: d64b2c7049339eaed9d14bafdc8a9ee3
SHA256: 47741a492077d3e385e120c3596bf6df63426930fffcaa7aa84c924ff43fee91
brisK KK v4 (brisk_kk-stock_2014-12-07_15-31-03_1091455.zip)
MD5: d5fb48434fe9a206a9544968081ee654
SHA256: 122189fb11068be07e6d24cbe179ed57a9872944664e028d0d288fcf804ea4d2
brisK KK v5 (brisk_kk-stock_2015-07-23_23-57-24_518a15c.zip)
MD5: 2a5086c1354e6f475d73b77b41bcfe40
SHA256: 7dce6a173c9e6ddf6f573c802cc8aea7900239a2253ca31722e651e791bb6e6e
brisK KK v6 (brisk_kk-stock_2015-07-28_15-07-08_64d9234.zip)
MD5: 567d7e6ea8762559d218bb092c4cdac4
SHA256: b5b3b41fa7ed10210e4964fa2cd98d14d4572a30b68f7b939e945a3458063a43
Samsungs stock JellyBean Kernel (samsung_jb.zip)
Description: Reverts all changes made by brisK JB by overwriting it with Samsungs original JB kernel (extracted from I9195XXUBML4).
MD5: 388336cec2e9686e258985d0dded0dc9
SHA256: 35777926edee3558208175d5359ef1c466dc3d4dbb1276e233f6727d64b83aa3
Samsungs stock KitKat Kernel (samsung_kk2.zip)
Description: Reverts all changes made by brisK KK by overwriting it with Samsungs original KK kernel and files (extracted from I9195XXUCNE6).
MD5: c71112214620a50841731f4899dd2ca2
SHA256: d2d70f212ee898cf1cedef2d84b3e6345e2388a13579a7112181a254a2c2f3de
Installing
To flash any of these zip-files, you need to install a custom recovery on your phone. (For example: http://forum.xda-developers.com/showthread.php?t=2364980 )
Put zip file on your phone or on its microSD
Boot into recovery: Hold "Volume UP", "Home Button", and "Power Button" when it is off or rebooting
MAKE A FULL BACKUP BY USING THE BACKUP-MENU
Select "Install from zip" or something similar
Navigate to your zip file, select it, and flash it
Reboot your phone
Uninstalling
If you want to go back to Samsungs stock kernel or flash another kernel, you need to install "samsung_jb.zip" or "samsung_kk.zip" first.
brisK uses custom kernel modules. When you run on brisK and then directly install another custom kernel which has no custom modules, you will probably experience issues with WLAN and other stuff. To solve this, flash "samsung_jb.zip" or "samsung_kk.zip" (which flashes the stock modules), and THEN flash whatever custom kernel you want. - Of course you do NOT need to do this if you update to a newer version of brisK.
thank !
GREAT !!!
but for governors and schedulers , i agree with you in half ... but "few" of them are very useful !
what do you think about the recent "zen" ...or "row" ( by default in all customs like cyanogenmod ) ?
for you ,what are the "best" (more adapted ) for better compromise in performance/baterry save ?
why you don't add just 1 or 2 among the best of ones ?
Now running on brisK
{
"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"
}
Loulou-13 said:
but for governors and schedulers , i agree with you in half ... but "few" of them are very useful !
Click to expand...
Click to collapse
I agree that some governors might actually improve performance, but there isn't much information available, some people say governor A is better, some say B is best...
But also: Kernel goal nr. 1 is stability, and ondemand is well tested. That's why I probably won't add any new governor before testing them a lot.
Can you suggest any governors? And do you have proof or URLs why they are better? Thanks!
If you want more features, more governors, etc, f4k will probably release a stock kernel soon. So keep an eye out for that!
Loulou-13 said:
what do you think about the recent "zen" ...or "row" ( by default in all customs like cyanogenmod ) ?
for you ,what are the "best" (more adapted ) for better compromise in performance/baterry save ?
why you don't add just 1 or 2 among the best of ones ?
Click to expand...
Click to collapse
Zen: I don't know what this does different than other schedulers, I have to read about this first.
I considered "row" when I had an Evo 3D, but I didn't notice a difference between "noop" and "row" in normal daily usage, so I'm not sure yet if I will include it or not - needs more testing.
ladislav.heller said:
Now running on brisK
Click to expand...
Click to collapse
Awesome!
If you have any problems, please report them here. And if you don't have any problems at all, please report that here too!
TheBootloader said:
I agree that some governors might actually improve performance, but there isn't much information available, some people governor A is better, some say B is best...
But also: Kernel goal nr. 1 is stability, and ondemand is well tested. That's why I probably won't add any new governor before testing them a lot.
Can you suggest any governors? And do you have proof or URLs why they are better? Thank!
If you want more features, more governors, etc, f4k will probably release a stock kernel soon. So keep an eye out for that!
Zen: I don't know what this does different than other schedulers, I have to read about this first.
I considered "row" when I had an Evo 3D, but I didn't notice a difference between "noop" and "row" in normal daily usage, so I'm not sure yet if I will include it or not - needs more testing.
Click to expand...
Click to collapse
Same thinking as me ...
ondemand for CPU Gov / No-op for I/O sched , they work great and don`t cause problems
SilviuMik said:
Same thinking as me ...
ondemand for CPU Gov / No-op for I/O sched , they work great and don`t cause problems
Click to expand...
Click to collapse
Yes, my experience too!
Although, when I copy big files with "noop", android freezes for the duration of the copy process. That's the nature of "noop", but "row" might actually fix that. But then again: I rarely need to copy big files, so "noop" is okay for now.
TheBootloader said:
Awesome!
If you have any problems, please report them here. And if you don't have any problems at all, please report that here too!
Click to expand...
Click to collapse
No problems, everything works well.
Please add support for USB Host with additional power supply, is very necessary !!!!
killov1982 said:
Please add support for USB Host with additional power supply, is very necessary !!!!
Click to expand...
Click to collapse
+1 for USB OTG support.
Working good so far
Thanks
TheBootloader said:
Yes, my experience too!
Although, when I copy big files with "noop", android freezes for the duration of the copy process. That's the nature of "noop", but "row" might actually fix that. But then again: I rarely need to copy big files, so "noop" is okay for now.
Click to expand...
Click to collapse
NOOP hangs in general when the read/write task becomes too intensive. Consider CFQ if you're going to do a bit write operation, else ROW is better. That my two cent when I tried on my S3 with Boffela kernel.
PS. ZEN hangs even worse than NOOP.
ladislav.heller said:
+1 for USB OTG support.
Click to expand...
Click to collapse
I second that
thank for your work...
is your kernel working with old knox-free bootloaders like Silviumik's kernel?
thanks
battery life compared with carbon 4.4.4 ? PLEASE
s.goten said:
thank for your work...
is your kernel working with old knox-free bootloaders like Silviumik's kernel?
thanks
Click to expand...
Click to collapse
For now i think no, because he did not remove Knox reference from source, i could be wrong tho !
I just released a new version!
A lot people asked for OTG, so here you go! I added OTG and BLN (untested!!!), thanks to junkyDE!
The highest kernel goal is stability, but I don't have time to test these features right now - maybe I can do one quick emergency fix tomorrow if something breaks, but after that I will probably not respond for 2 weeks or more.
So, have fun and enjoy!
brisK v2
Added OTG support (UNTESTED)
Removed TIMA
Change to XZ compression
Add BLN support (UNTESTED)
-----
s.goten said:
thank for your work... is your kernel working with old knox-free bootloaders like Silviumik's kernel?
Click to expand...
Click to collapse
SilviuMik said:
For now i think no, because he did not remove Knox reference from source, i could be wrong tho !
Click to expand...
Click to collapse
I removed TIMA in brisK v2, so.... it -should- work now right?
If it doesn't boot, just restore your boot partition from a backup or re-flash your previous kernel if you had any.
-----
TNCS said:
NOOP hangs in general when the read/write task becomes too intensive. Consider CFQ if you're going to do a bit write operation, else ROW is better. That my two cent when I tried on my S3 with Boffela kernel. PS. ZEN hangs even worse than NOOP.
Click to expand...
Click to collapse
Thanks a lot for your input! Now I know I don't need to consider ZEN, and will stay with NOOP, and aim for ROW when I have time to add it.
I9192?
Sent from my GT-I9192 using XDA Premium 4 mobile app
SilviuMik made a 9192 kernel:
http://forum.xda-developers.com/showthread.php?t=2592308