Related
TEAM n0ob FIRST RELEASE!
Ok after my OverClock How-To, I decided to play with overclocking and see what exactly can be gained from stock Max regulator Voltage (1.3v). I have found that at stock you can get up to around 1.13ghz. It is slightly faster than what pershoots kernel runs (38400khz).
As persiansown says, the standard stock voltage is set to 1275, and the regulator is maxed at 1.3v.
What Kind of gains will you see?
You will notice a difference in games like Asphalt, that use a lot processor. You will notice a decrease in battery life as well. Your linpack scores will vary from about 8.5-9.5 depending on your chip.
I have included pershoots undervolting, 21MB ramhack, and audio hack as well. Several optimizations, following in the footsteps of the Ivan/intersectRaven Kernels. (You could say we KANGED pershoot and just added two frequencies above his)
The frequencies in the kernel from 1113300-1152000 are at stock voltage(1.3v), and I have included the relevant source files. As such they "should" be safe. You never know though! The frequencies below this are Undervolted down to .925v!
This is using SLUB allocator and Deadline IO scheduler.
The recommendation of Team n0ob, is to use set CPU to set your phone to a frequency below 1.11ghz unless you need the extra power for something. Otherwise your battery life will suck and you will stress your processor for no reason.
This is confirmed working on CM-5.0.6-N1.
WARNING!!! THE LONG TERM EFFECTS OF OVERCLOCKING YOUR PROCESSOR CAN INCLUDE:
1. SHORTENED PROCESSOR LIFE
2. OVERHEATING
3. REDUCED BATTERY LIFE
4. BRICKED (IE DEAD DEVICES)
Mod edit: removed link, till source is link to kernel.
I ask that if you notice anything funny that you flash to a more tested kernel and notify this board immediately. This kernel is at stock voltage, but the increased speeds could have adverse effects. Please let us know if you notice any.
Team n0ob takes no responsibility for any damage that may occur to your device.
Credits: pershoot( thanks for the hard work), Kmobs (same), intersectRaven, Ivan (for beginning optimization trend), Rotohammer(experimental random/music/start fix), Cyanogen for awesome roms (whose source this is pulled from), chris soyars, and coolbho3000, Koush for the anykernel updater.
Team n0ob Testers: jlevey, DAMNiaTX Hell! (Thanks)
Following pershoot, I recompiled the Kernel with VFPv3 Optimizations.
resync to 2.6.33.3, old wifi drivers as everyone has problems with the new ones.
Lowered minV to 925. maxV is still 1.3. Voltages are increased to 1.3 only on the 2 frequencies above pershoots 1.113ghz. The other frequencies are undervolted similar to the Kmobs and or the Pershoot values.
Well, by "lowering processor life", how exactly long will my processor last? Does it depend on my phone? My uses? Im all in it for overclocking, and im very aware of said risk.. But processor life I'm not educated in..
Eclair~ said:
Well, by "lowering processor life", how exactly long will my processor last? Does it depend on my phone? My uses? Im all in it for overclocking, and im very aware of said risk.. But processor life I'm not educated in..
Click to expand...
Click to collapse
Not drastic. Not concrete figures but I've heard figures like instead of something like maybe 6 years, you may get 4-5 years. The processors are designed to last so long that even things that harm them typically still leave them outlasting the upgrade cycle of the user. It depends on the silicon in your phone as well.
Also, Gr8Gorrilla, does this include CM's latest commits from a day or two ago that fixes the pink cam tint issue?
No telling really. It shouldn't be much different than stock. However, as soon as I say that someone will install this brick the phone and blame me. So I am using it and I have a two year contract with T-mobile, I figure it should make it that far.
This is basically pershoots kernel plus 38400 khz. (pershoot in no way endorses this kernel). Take that for what it is worth. The top three voltages 1113, 1132, & 1152, are at stock voltage (1.3v).
I resynced my repo last night before compiling this.
Damn nice kernel is all I have to say
Gr8gorilla said:
I resynced my repo last night before compiling this.
Click to expand...
Click to collapse
Ok thanks! Definitely flashing this now!
Stock voltage is actually 1.275v. The processor is, however, rated to handle 1.3v (it was originally going to ship at 1.3v, but qualcomm decided to have it ship at 1.275v instead)
Gr8gorilla said:
No telling really. It shouldn't be much different than stock. However, as soon as I say that someone will install this brick the phone and blame me. So I am using it and I have a two year contract with T-mobile, I figure it should make it that far.
This is basically pershoots kernel plus 38400 khz. (pershoot in no way endorses this kernel). Take that for what it is worth. The top three voltages 1113, 1132, & 1152, are at stock voltage (1.3v).
Click to expand...
Click to collapse
I also am on a 2 year contract with TMobile, hopefully mine last that long also. Might as well flash this, blah..
persiansown said:
Stock voltage is actually 1.275v. The processor is, however, rated to handle 1.3v (it was originally going to ship at 1.3v, but qualcomm decided to have it ship at 1.275v instead)
Click to expand...
Click to collapse
I stand corrected. I should have said stock max regulator voltage. I will update the OP.
thanks Gr8gorilla
I'm definitely gonna try this out. I've been using intersect's and ivan's, just jumping back and forth. Good to see that there's another kernel out there to play with. Thanks Team n0ob!
Gr8gorilla said:
I have included pershoots undervolting, 8mb ramhack, and audio hack as well. The experimental Rotohammer fix for the headphone jack is compiled in as well, along with several optimizations, following in the footsteps of the Ivan/intersectRaven Kernels. (You could say we KANGED pershoot and just added two frequencies above his)
Click to expand...
Click to collapse
Does this have everything else that the default cyanogenmod's kernal has? (i just want to know if I am going to loose anything from cyan to this kernal)
INeedYourHelp said:
Does this have everything else that the default cyanogenmod's kernal has? (i just want to know if I am going to loose anything from cyan to this kernal)
Click to expand...
Click to collapse
Yes that is correct.
Nexus FireBall 1.15GHz.
I will be also flashing this kernel update to 1.15 GHz tonight. I want to try and optimize my nexus one to its fully potential capabilities. : )
Updated, Changed Kernel optimizations. Since this kernel follows pershoot, he recommends if you are on 5.0.6 to flash the VFPv3 optimized version.
VFP works great
Hi guys when i unzip their 4 files i know the ko and zimage but the other 2 files do i need to install them too?? and how? thanx in advance.
The other two files are the source files. They there so you can research what changes I have made in the voltage and frequencies and also you could compile this on your own if you want.
Can someone port this kernek to ATT?
http://forum.xda-developers.com/showthread.php?t=1263838
tassadar898 said:
Can someone port this kernek to ATT?
http://forum.xda-developers.com/showthread.php?t=1263838
Click to expand...
Click to collapse
Its possible, but there are differences in the softkeys, charging hardware, and nfc at the minimum, so it will take a little work to port that over entirely. What would be better is for one of our current kernel modders to add some of the features of the SIYAH kernel over to their own.
I plan on pulling in 100 MHz support.
He doesn't have that much more, other than extremely experimental features that if you read the thread, tend to break.
Gokhan is quite talented, but he's also VERY aggressive - if you're more careful, you don't have to go through long beta periods with lots of broken releases like he does.
He also released source code for older kernels as megapatches, and now releases as straight full-source tarball drops. It makes separating the good from the bad EXTREMELY difficult.
As far as features he has that I don't currently:
1) 100 MHz support - I plan on this one, it's a fairly high priority as part of my current power management research
2) Crazy wacky alternative governors - these are a great way to somehow combine lag and poor battery life all in one
3) Charge current control - not possible on our devices, we have a different (very crippled) charger IC
4) Touchscreen stuff - I have seen no reports of people having touchscreen issues. If it ain't broke don't fix it.
5) BLN - I'm on the fence on this one. I think the I777 community may actually have the maturity to handle this one. (BLN's dirty little secret on the I9100/I777 - it holds a wakelock while the light is on. This means you lose 50% battery overnight instead of <10% if a notificiation comes in right after bed.)
Entropy512 said:
5) BLN - I'm on the fence on this one. I think the I777 community may actually have the maturity to handle this one. (BLN's dirty little secret on the I9100/I777 - it holds a wakelock while the light is on. This means you lose 50% battery overnight instead of <10% if a notificiation comes in right after bed.)
Click to expand...
Click to collapse
Would it be possible to get past the wakelock issue if you could program that the BLN shuts off after, say 30min, or user defined? That would work in my case but not sure if everyone universally would like it that way. Just a thought...
Hey Entropy nice to see you here! In siyah you can control the GPU voltage for undervolting. I currently do it using the Tegrak kernel module and I reduced the minimum step of 160 mhz to 750mv down from 950mv. I've noticed a nice bump in battery life. In his 2.1 beta version he also has this available feature
SiyahKernel v2.1 - not released yet -
Time to break some records... both performance-wise and battery-wise...
Overclocking part is optimized and bus frequency selection is modified.
User customizable frequency levels. you still have 8 steps, but you will be able to customize them. wanna change 100 to 150 as 100MHz is not stable on your device? wanna change 1400 to 1304 and 1600 to 1504? or increase 1600 to 1696?
User customizable bus frequency selection. no more overheating. if you are a battery freak, just set it to minimum and your device will last more than ever.
Based on Update3 sources...
Thanks for developing for us!!
I'll look into GPU voltage control once I finish my current power management adventures.
Custom frequency steps seems like asking for stability problems. There's no way this is getting ported until he releases 2.1 final, since he isn't very good about GPL compliance.
Thanks! I look forward to testing. If you need a guinea pig let me know.
Entropy512 said:
I'll look into GPU voltage control once I finish my current power management adventures.
Custom frequency steps seems like asking for stability problems. There's no way this is getting ported until he releases 2.1 final, since he isn't very good about GPL compliance.
Click to expand...
Click to collapse
GPU voltage doesn't bring that much other than stabilizing 400MHz, undervolting doesn't go that far down from stock voltages, unless you underclock heavily too.
Also get off his horse about GPL . The license states that you've got 90 days to release your code, until now he released it within the day for final versions, and betas are no longer released on XDA to get off that technicality of the 5 day rule.
There's enough kernels out there with the "stable" philosophy, some of which barely differentiate from stick sources, so people can go and use those if they want to. Siyah is more a Swiss army knife, but you'll have to be careful not to cut yourself, and it's more fun for some to tinker with the phone.
Edit: What you should port though, is update3 sources, those bring significant upgrades in battery life, speed and sound quality.
AndreiLux said:
GPU voltage doesn't bring that much other than stabilizing 400MHz, undervolting doesn't go that far down from stock voltages, unless you underclock heavily too.
Click to expand...
Click to collapse
Yeah, I figured as much, which is why it's pretty low on my priorities list
Also get off his horse about GPL . The license states that you've got 90 days to release your code, until now he released it within the day for final versions, and betas are no longer released on XDA to get off that technicality of the 5 day rule.
Click to expand...
Click to collapse
It says that nowhere. HTC claimed they had 90 days and that is a GPL violation. Easy enough to Google that one. It kind of bit them in the ass though - http://thread.gmane.org/gmane.linux.kernel/1048027 and https://freedom-to-tinker.com/blog/sjs/htc-willfully-violates-gpl-t-mobiles-new-g2-android-phone
After much media pressure they backed down and released sources in only 7 days.
GPLv3 gives an explicit 30-day grace period for resolving violations, but the kernel is not v3, it's GPLv2.
I really should stop pointing Gokhan towards fixes since he's a one-way street.
There's enough kernels out there with the "stable" philosophy, some of which barely differentiate from stick sources, so people can go and use those if they want to. Siyah is more a Swiss army knife, but you'll have to be careful not to cut yourself, and it's more fun for some to tinker with the phone.
Click to expand...
Click to collapse
Yup - If someone else wants to port his more aggressive features they can try - it's just not coming from me.
Edit: What you should port though, is update3 sources, those bring significant upgrades in battery life, speed and sound quality.
Click to expand...
Click to collapse
I'll have to look into that - As of a few weeks ago, the AT&T I777 sources were new enough that I9100 kernels (including Siyah) started to be based off of them. The question is - while Update2 to Update3 is a big improvement, is I777 to update3 such an improvement?
I'll have to check those out tonight and diff them.
update3 is a vastly bigger update than what the AT&T sources were to update2. Performance wise, it's a clear-cut, audio too. As for battery life check back in the AOS thread.
Looking forward to see the update being incorporated.
AndreiLux said:
update3 is a vastly bigger update than what the AT&T sources were to update2. Performance wise, it's a clear-cut, audio too. As for battery life check back in the AOS thread.
Click to expand...
Click to collapse
I'm going to start this over the next week - I've split update3 into what should be separate independent patchsets by component (touchkey, audio, wifi, etc.)
Last one is likely going to be the machine-specific ARM stuff - because that means rewriting the clock control patches completely.
Thread closed.
Thread closed..
Thread closed...
Thread closed...
Thread closed.....
Reserved.
amazing!
will try it on SlimBean rom
thanks mate
SignalX said:
amazing!
will try it on SlimBean rom
thanks mate
Click to expand...
Click to collapse
Just gimme another hour or so, I've a few Linux versions to go to be at 3.0.52
JP.
Hey JP!
Nice to see you made an aosp kernel,bravo!
I was considering trying an aosp based rom but i was wondering...
Are there any bugs or anything that's not working on aosp roms compared to sammy ones?
The last thing i remember that was an issue(a long time ago... )
Was that cm10 had memory leak,which now is fixed...
nfsmw_gr said:
Hey JP!
Nice to see you made an aosp kernel,bravo!
I was considering trying an aosp based rom but i was wondering...
Are there any bugs or anything that's not working on aosp roms compared to sammy ones?
The last thing i remember that was an issue(a long time ago... )
Was that cm10 had memory leak,which now is fixed...
Click to expand...
Click to collapse
Well I've been running Paranoid Android 2.54 for one day with stock kernel, and I liked it that much that I decided to "port" my Sammy kernel to CM10, or to be more precise, to add the same mods to a CM10 base as those I added to the Sammy kernel.
I'm test-compiling 3.0.45 right now, next step will be 3.0.52
JP.
Ok, time to shoot, here it is, just readily cooked, be carefull, still hot
Changelog v1.0
Based on CyanogenMod CM10 kernel for i9300 sources (Linux 3.0.31)
updated to kernel.org Linux 3.0.52
using Paranoid Android 2.54 ramdisk
swap support
/proc/config.gz support
optimized for size
Aroma installer with options
USB Forced Fast Charge v1.2a (Yank555.lu)
CPU OC up to 1.6GHz (Yank555.lu)
Triangle Away support (Chainfire)
Dynamic fsync control (faux123)
TCP westwood congest ctrl (faux123)
Proport. Rate Reduction TCP (faux123)
ARM AES/SHA1 (faux123)
JIT compiler for packet filters(faux123)
fix ipv6 protocol lookup (faux123)
ipv4 check ret.val. dst_alloc (faux123)
ipv6 check ret.val. dst_alloc (faux123)
updated LZO compression (faux123)
do_fsync() to fget_light() (faux123)
reduce mali utilization sampling timeout (AndreiLux)
mdnie: custom settings (AndreiLux)
Includes hardcore sharpnes fixes, and black gamma curve adjustment for black crush
ntfs (rw) support (kernel support only)
zram support (Android optimized)
Download link (MD5 fd4bbc970ef350621a8a3ed9c8003e8c)
Please do consider this v1.0 as beta, I've started working on this CM10 kernel this evening, and it's just done compiling, so you're testing this with me
Yank555 said:
Well I've been running Paranoid Android 2.54 for one day with stock kernel, and I liked it that much that I decided to "port" my Sammy kernel to CM10, or to be more precise, to add the same mods to a CM10 base as those I added to the Sammy kernel.
I'm test-compiling 3.0.45 right now, next step will be 3.0.52
JP.
Click to expand...
Click to collapse
I see...
Looking good!
Is anything not working or have bugs mate? (on the aosp side i mean not on your kernel)
I think you get that some want to have some info before flashing things on their phones.
nfsmw_gr said:
I see...
Looking good!
Is anything not working or have bugs mate? (on the aosp side i mean not on your kernel)
I think you get that some want to have some info before flashing things on their phones.
Click to expand...
Click to collapse
Well the base (CM10 stock kernel) behaved perfectly well, today (I've not used it any longer, as I got my second S3 only yesterday )
So far, I'm running v1.0 since I compiled it about 1 hour ago, looking peachy, but well 1 hour is quite a little too short to make any conclusions.
JP.
Yank555 said:
Well the base (CM10 stock kernel) behaved perfectly well, today (I've not used it any longer, as I got my second S3 only yesterday )
So far, I'm running v1.0 since I compiled it about 1 hour ago, looking peachy, but well 1 hour is quite a little too short to make any conclusions.
JP.
Click to expand...
Click to collapse
A second S3, wow. :silly:
I use this kernel with Helly_Bean (CM10) and everything is just fine!
Can I change the voltage settings and the touch-boost level?
Thanks!
BenjaminX2 said:
A second S3, wow. :silly:
I use this kernel with Helly_Bean (CM10) and everything is just fine!
Can I change the voltage settings and the touch-boost level?
Thanks!
Click to expand...
Click to collapse
Voltage control is something I'm not keen on introducing, as it brings close to no battery gain (nothing you could actually really measure) but adds a whole lot of risk of instability, especially users pushing the limits or even slightly above I wouldn't want any flooding with weird random reboot reports due to this
CPU and GPU (governor) behaviour is stock (except for the CPU OC ti 1.6GHz).
JP.
Yank555 said:
Voltage control is something I'm not keen on introducing, as it brings close to no battery gain (nothing you could actually really measure) but adds a whole lot of risk of instability, especially users pushing the limits or even slightly above I wouldn't want any flooding with weird random reboot reports due to this
CPU and GPU (governor) behaviour is stock (except for the CPU OC ti 1.6GHz).
JP.
Click to expand...
Click to collapse
I like to undervolt the CPU 100mV and the GPU 25/50mV. That is stable for me and reduces the temperature of the phone a bit. Most noticeable with the touch boost turned down to 200 MHz.
Let's see if a governor change can help.
BenjaminX2 said:
I like to undervolt the CPU 100mV and the GPU 25/50mV. That is stable for me and reduces the temperature of the phone a bit. Most noticeable with the touch boost turned down to 200 MHz.
Let's see if a governor change can help.
Click to expand...
Click to collapse
Not sure using a different gogernor than pegasusq is going to work well...
UV for temperature might be a good idea, but not for better battery as that doesn't realy make any measurable difference, brings only the risk of instability.
JP.
Sent from my Paranoid Android 2.54 / Yank555.lu CM10 kernel v1.0 (3.0.52) powered Galaxy S3 i9300 using Tapatalk 2
Okay,i switched over from hoxhound to helly bean and i must say this is great!
Your kernel works fine here...
I really really reallyyyy hope you update this kernel like the other one!
nfsmw_gr said:
Okay,i switched over from hoxhound to helly bean and i must say this is great!
Your kernel works fine here...
I really really reallyyyy hope you update this kernel like the other one!
Click to expand...
Click to collapse
Will keep them in line each time I change something that can fit both
Just moved my daily to PA, switched S3, the white one's in my pocket now
So no worries there
JP.
Sent from my custom ARHD 14.0 / Yank555.lu JB kernel v2.5 Aroma (JB-U6 / Linux 3.0.52) powered Galaxy S3 i9300 using Tapatalk 2
Yank555 said:
Will keep them in line each time I change something that can fit both
Just moved my daily to PA, switched S3, the white one's in my pocket now
So no worries there
JP.
Sent from my custom ARHD 14.0 / Yank555.lu JB kernel v2.5 Aroma (JB-U6 / Linux 3.0.52) powered Galaxy S3 i9300 using Tapatalk 2
Click to expand...
Click to collapse
That's great man!Cheers!
Presenting EM Kernel or EMk for short for the Galaxy Note 8.0 (N5100), other variants will face development once this kernel is reported working. Features are pretty basic for now, haven't made any extensive changes, but expect them soon . All of my developments for the Note 8.0 will be faster and better (considering that I won't have to request for testers and files), if I have the device in hand, so if you think of me as worthy, consider making a donation, every single one is highly appreciated
My Github: github.com/emwno
You will my custom recovery i.e CWM to flash this kernel.
Features:
I will only be listing major or noticeable changes. Read commits @ github for details
Overclock Support
Intelligent write-back
Network speed tweaks (crypto)
I/O Schedulers: Sio, Row, Zen
Governers: InteractiveX, Savagedzen, Zzmoove, PegasusQ, Lulzactive, SmartassV3 (only listing which I've added)
ARM specific optimizations
Triangle Away support
Boeffla Sound support
Google Snappy drivers
Sudden Death addressed*
Releases:
EMk-03: N5100 | N5110
Changelog:
03
OC fix
Attempted Wifi fix for N5110
Governers added: Lulzactive, SmartassV3
Some more IO's (dont remember names)
Roll back to stock voltages
Boeflla Sound support
Triangle Away support
Lz4 compression (faster boot)
02
Support for N5110
Various build fixes
Zzmoove governer
Row / Zen IO Schedulers
Fixed up write-back
PegasusQ governer alterations (github)
AIO temp remove
01
Initial release
I am a giant knucklehead - I read "note 8" and didn't pay attention to the model #.
The test was done on a 5110 - I somehow missed the actual model # it was written for.
It does sound like the data reminded emwno about a detail, though.
That said, the restore technique does work (and I didn't softbrick my device.)
Thanks for taking a run at this!
The new boot.img took a really long time to get from initial Galaxy model # screen to the blue and white Samsung logo on first boot.
Wifi not working with the new kernel on first or second boot.
Did in fact boot, though. Antutu thinks cpu metrics are a hair slower than stock, and the UI feels a little slower also.,
A recovery zipfile would be super cool.
I mounted the external sd, then used
dd if=/dev/block/mmcblk0p5 of=/external_sd/bootrecover.img bs=1M
to backup and
dd if=/external_sd/bootrecover.img of=/dev/block/mmcblk0p5 bs=1M
to restore and now have wifi again.
roustabout said:
Thanks for taking a run at this!
The new boot.img took a really long time to get from initial Galaxy model # screen to the blue and white Samsung logo on first boot.
Wifi not working with the new kernel on first or second boot.
Did in fact boot, though. Antutu thinks cpu metrics are a hair slower than stock, and the UI feels a little slower also.,
A recovery zipfile would be super cool.
I mounted the external sd, then used
dd if=/dev/block/mmcblk0p5 of=/external_sd/bootrecover.img bs=1M
to backup and
dd if=/external_sd/bootrecover.img of=/dev/block/mmcblk0p5 bs=1M
to restore and now have wifi again.
Click to expand...
Click to collapse
Man..... i forgot modules....
Anyways it will be slow until all the backports are complete. thanks for the report!
emwno said:
Presenting EM Kernel or EMk for short for the Galaxy Note 8.0 (N5100), other variants will face development once this kernel is reported working. Features are pretty basic for now, haven't made any extensive changes, but expect them soon . All of my developments for the Note 8.0 will be faster and better (considering that I won't have to request for testers and files), if I have the device in hand, so if you think of me as worthy, consider making a donation, every single one is highly appreciated
My Github: github.com/emwno
You will my custom recovery i.e CWM to flash this kernel.
Features:
Overclock Support (upto 1.8Ghz)
Intelligent write-back
Network speed tweaks (crypto)
I/O Schedulers: sio
Governers: InteractiveX, Savagedzen (only listing which I've added)
AIO backported (from linux 3.6 kernel)
ARM specific optimizations
ARM Topology enabled
Modified LMK
Releases:
EMk-01: http://d-h.st/mDP
Changelog:
01
Initial release
(read features)
Click to expand...
Click to collapse
Great Job! Now we need one for the N5110.
An observation on the Samsung kernel and OS: for a good bit of time after a reboot, the cores are all running flat out at 1.6 ghz.
The immediate cause is apparently that the device is scanning the internal memory and sdcard and this is a somewhat processor-intensive task.
What surprised me, though, was that after installing cpu usage monitor, only one of the cores was doing most of the work - but all 4 were running at 1.6 ghz for a lot of the time.
Hopefully I'll be restarting less this evening and can look to see if this is true in more casual usage. If others are noticing this, it seems like better multicore management by the kernel would go a LONG way to ameliorating the relatively poor battery life.
The device uses the pegasusq governor, which does support core hotplugging, but is either just not that good at doing so or isn't configured to release unused cores very quickly.
I haven't had a chance to compare the settings I have with the explanations in this excellent post on the governor and what it's doing:
http://forum.xda-developers.com/showpost.php?p=24233103&postcount=3
I have yet to modify governers for specificds such as battery life and speed. Its scanning because of the intelligent write back, which does the major work faster with all cores at while booting.
I spent some time looking at governor settings last night.
When I finished, I'd used the device for about 5 hours, did 6 reboots and a number of benchmark cycles and had gone from 90% charge to 45% charge.
So if that holds up, I'm getting about 3 hours more per cycle. One thing I noticed: if you run an Antutu benchmark, you may want to reboot your device - Antutu seems to lock all four cores at 1.6 ghz for a long time after it runs.
I landed on two modifications via set CPU:
first mod: set ignore_nice_load =1
"ignore_nice_load - Setting to 1 causes governor to ignore load resulted by nice processes while making scaling decisions. Nice processes are the one i/o scheduler refers to as low priority process.
UNIT: Boolean 1 or 0"
Basically, a process which is nice is one that will get out of the way if I'm doing something else, and I'm not interested in, even for 15-20 minutes, running all four cores at full speed to get it done. It looks to me as if media scanning is a process with the nice flag set.
Second mod: changed freq_step from 37 to 12.
"freq_step - Defines how much as a percentage of maximum frequency, governor should increase CPU frequency each time CPU load reaches up_threshold.
UNIT: Percentage"
As shipped the processors step in giant increments.
Setting that value to a 12% step rate gives me 200 mhz increments, and I see that my processor is spending much more time in the 400-600 mhz range than before,.
I'm probably going to do additional tests with a 6% step rate (100 mhz increments) at some point.
The nice setting emerged from looking to see what was running at boot time and coming across threads on the behavior such as this one:
http://forum.xda-developers.com/showthread.php?t=1994650
I'm happy with the performance I'm seeing in this setup, and happier still with the battery life I'm seeing. Your mileage may vary, of course, but waiting a few milliseconds more for the processor to cycle all the way to 1600 mhz hasn't made the device feel stuttery to me.
Still on my to-do list is getting the cores to up and downshift more independently. The governor tends to let only one core lag the others, so I almost always see three cores at once at the same frequency, even if only one appears to be doing anything.
EMk02 Live.
Just took a run at emk02-5110 - still no wifi.
Bluetooth was fine, boot was speedy.
My tools for looking at CPU reported that the clock speeds available were 50 mhz-1600 mhz.
It seems possible that the high end was truncated at 1600 mhz by chip reporting something inaccurately, and that as a result the low end was also pushed very low?
The kernel seemed just fine aside from no wifi, though!
roustabout said:
Just took a run at emk02-5110 - still no wifi.
Bluetooth was fine, boot was speedy.
My tools for looking at CPU reported that the clock speeds available were 50 mhz-1600 mhz.
It seems possible that the high end was truncated at 1600 mhz by chip reporting something inaccurately, and that as a result the low end was also pushed very low?
The kernel seemed just fine aside from no wifi, though!
Click to expand...
Click to collapse
Only till 1600? I remember adding upto 1800... About the no wifi, flash the attachment and let me know of the result.
Still no wifi.
Clock still tops at 1600 reported.
The attached wifi fix file has scsi_wait_scan.ko in it -- I'd thought that was a filesystem module?
Did it replace anything? I hope not, as it doesn't seem to make a backup of the original?
roustabout said:
Still no wifi.
Clock still tops at 1600 reported.
The attached wifi fix file has scsi_wait_scan.ko in it -- I'd thought that was a filesystem module?
Did it replace anything? I hope not, as it doesn't seem to make a backup of the original?
Click to expand...
Click to collapse
That is the only module that was generated. thats the stock one. taking a look at source again..
EDIT: try flashing this. built kernel again. (all generated modules added)
Hmmmm
OK, I poked around a bit first on my device and then I extracted /system from the firmware blob, used simg2img and mounted the output in a linux system to get a look at what Samsung delivers.
I did not see a scsi_wait_scan in their flashable system. I found a folder called dhd which apparently relates to networking.
The installed system doesn't use these files, though - is that because Samsung integrates them all into the kernel?
At any rate, I know I won't overwrite anything when I get time to flash now, at least
OK, tried flashing in the boot.img and the files in 2.zip. Still no wifi.
Also, the files in 2.zip are *.ko, the other files are *.so, and in the extract of system, there no .ko files -- is that part of what's what?
To make testing simpler down the road, I also made a flashable boot.img restore file, which folks can get a copy of here
http://www.mediafire.com/download.php?w89vgdn4kdds781
emwno said:
That is the only module that was generated. thats the stock one. taking a look at source again..
EDIT: try flashing this. built kernel again. (all generated modules added)
Click to expand...
Click to collapse
fixed 2.zip,still no wifi
Why... did i do something so dumb... the libs are placed elsewhere.... making a new zip.
let us know when you got the wifi working I am really looking forward to flashingthis
Does anyone want sound mods supported? Such as Boeffla Sound snd Wolfson Sound. All kernel based.
emwno said:
Does anyone want sound mods supported? Such as Boeffla Sound snd Wolfson Sound. All kernel based.
Click to expand...
Click to collapse
Yes please!
New change log for kernel. Ignore the one on OP. If you have any requests, present them to me.
03
OC fix
Wifi fix for N5110
Governers added: Lulzactive, SmartassV3
Some more IO's (dont remember names)
Roll back to stock voltages
Faster USB charging
Boeflla Sound support
Triangle Away support
CPU voltage control
Lz4 compression (faster boot)
Some back ports from linux 3.4 mainline (will post which after confirmed working myself) - no more
emwno said:
New change log for kernel. Ignore the one on OP. If you have any requests, present them to me.
03
OC fix
Wifi fix for N5110
Governers added: Lulzactive, SmartassV3
Some more IO's (dont remember names)
Roll back to stock voltages
Faster USB charging
Boeflla Sound support
Triangle Away support
CPU voltage control
Lz4 compression (faster boot)
Some back ports from linux 3.4 mainline (will post which after confirmed working myself)
Click to expand...
Click to collapse
Do we have a download yet?
Ok, please respect my time spend on that kernel and read at least those few opening posts and last pages of topic.
Many users reported that overclocking doesn't work for them, they got SODs etc. most probably because of gpu overclocking. So I present you a kernel with LiveOC feature that should be good for every user.
1. Main features
2. Tunables
3. Source
4. FAQ
5. Credits
6. Download
1. Main features (more in changelogs and on mine git)
* LiveOC
* Fastcharge
* CustomVoltage
* 441mb of RAM
* 400,800,1000,1100,1200,1300,1400 frequency steps with stock gpu&bus speed
* BFS
* Lowmemorykiller from 3.4
* Frandom
* 3.0.8
* Fsync disabled
* Lowered screen minimum brightness (I hope so that this is our hardware limit)
* default SIO and conservative
* opitmal readahead
* mine touchscreen values
* wifi works at normal speed when device is locked
* battery is charged to its 100%
* Touchscreen undervolted 20%
* Maaany other fixes and small features
2. Tunables
For managing those features you are supposed to use apk like NSTools or any other, but that one is highly recomennded
LiveOC
I implemented it so everybody can overclock as he wants to, total personalization and freedom of choice. And possibility to squeeze maximum performance.
LiveOC simply overclocks CHOOSED cpu frequencies by a % choosed by YOU, user.
As the gpu&bus frequency is simply cpu frequency divided by a number, it also is overclocked by choosed %.
Unfotunatelly cpu frequency and gpu&bus frequency are linked so choosed % affect both of them.
As I said, you can also choose which frequencies to overclock which is great facility.]
You won't probably be able to overclock more than 127% because of our BUS which can't achieve such a frequency (most devices)
For example, you choosed minimum frequency affected by LiveOC as 1300mHz and maximum as 1400mHz.
You set LiveOC % to 110., then:
1,1*1300 ==> 1430mHz
1,1*1400 ==> 1540mHz
1,1*200 ==> 220mHz - gpu&bus frequency for both of the frequencies
Now you probably think: Ok, I can overclock even to 1,7gHz but my device will reboot for sure because of too low voltages! That is why I also implemented CustomVoltage. Although when you overclock it slightly then you possibly won't have to adjust voltages.
*WARNING*
Some frequencies seem to not like liveoc, for me it is 1300mhz. Also some liveoc values can be laggy, use different then.
CustomVoltage
CustomVoltage allows to set you custom voltage for both cpu and gpu&bus.
Perfect solution for undervolting and overvolting when using liveOC
ARM voltage - voltage given to CPU
INT voltage - voltage given to GPU&BUS
Fastcharge
Fastcharge make charging via USB as fast as via normal A/C charger
You can simply turn it on and off whenever you like.
Minimum Brightness
Now your device can be even dimmer when using it at night.
*WARNING* You have to use RootDim apk for this thing. Lowering brightness via setting or on statusbar would require rom modification
I highly recommend seting up a custom tile, you choose Rootdim night1 and for example system icon "cloud".
Then you open RootDim, set your brightness to 1 and longpress Night1 button.
Voilla! You have a custom tile that sets your brightness to 1
I hope that it set brightness to our hardware minimum.
I also recommend switching off keys backlight by a script or manual permissions change
3. Source
https://github.com/KOala888/blahblah
anyway some changes are still only on my HDD
4. FAQ
This will be created in future
Some terms:
BFS - http://en.wikipedia.org/wiki/Brain_****_Scheduler
Frandom - http://billauer.co.il/frandom.html
Fsync - http://forum.xda-developers.com/showthread.php?p=33381928
Readahead - http://en.wikipedia.org/wiki/Readahead
5. Credits
JackpotClavin - for his 3.0 kernel for our lovely venturi and other contributions and helping me to build
Mevordel - For verything he has contributed us and explaining me many kernel things
android1234567 - For his source, advices, discoussions with him, helping me to build and solve errors, answering in my threads
Ezekeel - for creating LiveOC and many useful features
ts1506 - for his repo and advices
Fishears - For his awesome repo and advices
DerTeufel - For CustomVoltage and modification to liveOC and his ideas
Stratosk - For his epic work for aries and his repo
morific - For his EPIC work to many devices, inspiration and origial idea
The order doesn't matter. If I forgot someone then I am sorry and please point me that
5. Downloads
Downloads:
usa:
http://www31.zippyshare.com/v/27472720/file.html
intl:
http://www2.zippyshare.com/v/42191562/file.html
CHANGELOG
7th July 2013 - Release 2.1
*3.0.85
*Updated GPU drivers
*less debugging and ram dedicated to it
*new wifi drivers? not sure if we use same as aries
*some fixes to SLUB
*KSM and VM tuned
*async I/O improved
18th June 2013 - Release 2
*3.0.82
*Build with A8 cortex optimized toolchain
*Some optimization for flags - feels smoother
*Finally found my dream governor - intellidemand, seems to be perfect for my idea of the kernel
*Update zip contains script turning off our keys backlight! From now with the minimum brightness mod you can enjoy using player at night
31th May 2013 - Release 1
*unnecessary governors removed & conservative - default - can cause laggy UI - still have to find proper governor
*even dimmer screen
26th May 2013 - Beta 2
*linux 3.0.8
*removed 100&200mhz frequencies to eliminate SODs
*Battery is charged to its 100%
19th May 2013 - Beta 1
*initial release
Download is up so please enjoy
LiveOC helps to squeeze 100% from EVERY device
woah another kernel from you already, woot time to flash
The only one supported. Old are totally aborted. I just had to start from a scratch again.
I hope that youtube and kerys will work for usa, not sure
ok so far i been testing international kernel on latest iurnait's cm10.1 , tried vice city on medium graphics and it works pretty smooth, the touchscreen tweaks makes it really easy to control, cpu freq 100mhz-1400mhz, performance as governor and SIO as scheduler are just working great for heavy usage, best performance on my galaxy player so far, good job :good:
@KOala888 you should add instructions on how to configure liveOC so far Ezekeel's liveOC is pretty interesting but it doesn't scale up voltage and it doesn't OC the GPU well
BTW you should add credit for Ezekeel in the OP because he made the liveOC
1 last thing: there's no UKSM in the kernel
peztoa said:
ok so far i been testing international kernel on latest iurnait's cm10.1 , tried vice city on medium graphics and it works pretty smooth, the touchscreen tweaks makes it really easy to control, cpu freq 100mhz-1400mhz, performance as governor and SIO as scheduler are just working great for heavy usage, best performance on my galaxy player so far, good job :good:
Click to expand...
Click to collapse
Thank you, you should try liveoc for sure Maybe later when I will add more detailed instructions.
android1234567 said:
@KOala888 you should add instructions on how to configure liveOC so far Ezekeel's liveOC is pretty interesting but it doesn't scale up voltage and it doesn't OC the GPU well
BTW you should add credit for Ezekeel in the OP because he made the liveOC
1 last thing: there's no UKSM in the kernel
Click to expand...
Click to collapse
There are some accualy
Also, I did everything in hurry, and as you can see I have written that I have to make better opening post in future, so don;t worry everything will be added, like credits But thank you.
Also it isn't exacly ezekeel's liveoc I think. Why it doesn't OC gpu well? Stratosk has voltages scallable, but it is very individual feature. Most often you overclock 1-2 frequencies, not all of them, so not too much to adjust
I will add suggested configurations and voltages in future. I like liveoc because you can get literally maximum performance from overclocking here.
About UKSM, not sure, git doesn't match my HDD repo to well ;c
KOala888 said:
Thank you, you should try liveoc for sure Maybe later when I will add more detailed instructions.
There are some accualy
Also, I did everything in hurry, and as you can see I have written that I have to make better opening post in future, so don;t worry everything will be added, like credits But thank you.
Also it isn't exacly ezekeel's liveoc I think. Why it doesn't OC gpu well? Stratosk has voltages scallable, but it is very individual feature. Most often you overclock 1-2 frequencies, not all of them, so not too much to adjust
I will add suggested configurations and voltages in future. I like liveoc because you can get literally maximum performance from overclocking here.
About UKSM, not sure, git doesn't match my HDD repo to well ;c
Click to expand...
Click to collapse
It is Ezekeel's, he originally made it for the Nexus S and I believe his name is in the copyright for the liveOC file. By bad GPU overclocking I mean that the GPU is barely being overclocked at all (unless it doesn't have GPU overclocking). For example, in my kernel the GPU runs at 229MHz when the CPU is at 1600MHz. In Nenamark2 with my kernel and CPU at 1600MHz I get 33fps. In this kernel I set the liveOC to 115% and set the CPU to 1680MHz and I only scored 30fps.
Sent from my HTC Sensation 4G using xda app-developers app
Well I wouldn't say it is anything related to liveoc overclocking gpu in a bad way. It can be voltage, other kernel changes, toolchain (which I will change too), anything
I prefer hardcoded overclocking, but liveoc gives same performance and you can push it to the limits
And I don't need it to be the best in benchs, I want it to be universal. For me it is the best anyway
In epic citadel I got 41 fps
Wysłane z mojego Nexus S za pomocą Tapatalk 2
I hope im not the only one who wants this or i most surely will look like a boob...but is there any chance you could make a kernel like this for gingerbread? Entropy512's is just seeming so outdated after seeing the amazing features in the jellybean kernels . I and i hope some others would greatly appreciate if you just considered creating a gingerbread kernel. Thank you
Sent From My USA Galaxy Player 5.0
Okay so with live oc my over clock will increase when needed and remain low when not...
So it's like on demand?
Sent from my GT-I9300 using xda premium
Nope. If you overclock it to 120% then every affected frequency will stay at 120% unless you change it to 100%
Feel free to ask
And about gingerbread, I don't use it. It literally sucks comparing to 4.2.x
So sorry but I can't. Hardware acceleration and many useful features do the thing.
But maybe in future, as an experiment, to see whether it isn't faster while gaming. I already had gb kernel some time ago but discraded.
Wysłane z mojego Nexus S za pomocą Tapatalk 2
An1mus said:
Okay so with live oc my over clock will increase when needed and remain low when not...
So it's like on demand?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
LiveOC is not automatic, you have to configure it and use it manually. Basically, it allows you to increase the frequencies by a percent between 100 and 150 that you put in. Let's say you put in 110%, then the speed of all the frequencies will go up by 10%, so 1400MHz will become 1540MHz, 1300MHz will become 1430MHz, and so on.
Sent from my HTC Sensation 4G using xda app-developers app
But I included tunable selective liveoc too. So you can choose frequencies to overclock
Than you for help android1234567, btw do you use it? how is it?
Goodnight guys
Wysłane z mojego Nexus S za pomocą Tapatalk 2
KOala888 said:
But I included tunable selective liveoc too. So you can choose frequencies to overclock
Than you for help android1234567, btw do you use it? how is it?
Goodnight guys
Wysłane z mojego Nexus S za pomocą Tapatalk 2
Click to expand...
Click to collapse
I tested the kernel and it works well
How do I use the selective overclock?
Sent from my HTC Sensation 4G using xda app-developers app
Man, these 5.0 kernels are just amazing. The ram, OC, and everything. I'm really hoping that we'll see kernels with these features on the 4.0 sometime soon!
I'm curious, how much of a battery improvement does the LCD UV make? On the 4.0, the display eats tons of battery, tons and tons more than anything else. Wondering if we brought that to the 4.0 that it might fix that issue.
With this kernel every time I turn my screen on it doesn't come back on
Sent from my YP-G70 using xda premium
Is just me or the compass is fixed now? Its working perfect on Google maps
Sent from my YP-G70 using xda app-developers app
android1234567 said:
I tested the kernel and it works well
How do I use the selective overclock?
Sent from my HTC Sensation 4G using xda app-developers app
Click to expand...
Click to collapse
In NSTools in cpu card you have values like OC target low and OC taget high. If you choose for example 800 and 1200 then every frequency from 800 to 1200 will be overclocked
WHib96 said:
Man, these 5.0 kernels are just amazing. The ram, OC, and everything. I'm really hoping that we'll see kernels with these features on the 4.0 sometime soon!
I'm curious, how much of a battery improvement does the LCD UV make? On the 4.0, the display eats tons of battery, tons and tons more than anything else. Wondering if we brought that to the 4.0 that it might fix that issue.
Click to expand...
Click to collapse
Hm, just take from batterystats the % of battery that your LCD takes and multiply it by 0,8 Also, you have other display
An1mus said:
With this kernel every time I turn my screen on it doesn't come back on
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
See first post, set minimum frequency to 400mhz until I won't fix it
peztoa said:
Is just me or the compass is fixed now? Its working perfect on Google maps
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
I never used it. If I foxed it then by accident
Wysłane z mojego Nexus S za pomocą Tapatalk 2