Related
[KERNEL] [2.6.29.6] [Flashable-.zip] [LAGFIX][BFQ][Oc][Uv] #3 "Patches 'O Klick"
So after countless hours of failure, I finally found my issue. It was an embarrassing one, but O well. What we have here is a fully stable kernel for the Vibrant. I have spent many hours on this and have been running it on my vibrant for some time now. Be sure to read the changelog for full info. At 1.2 Ghz I was getting MFLOPS scores pushing 10 MFLOPS! Performance is surely nice on this one. Another thing to note is the undervolting on my kernel. This will give optimal battery life for users. So, please enjoy, and post and errors with a logcat
This is compiled for the stock ROM. It will work on FrankenTwiz, Bionix, and many ROMs. Let me know what ROMs you try it on, and what ones it works best with.
hurrpancakes said:
This would be my first time using an oc/uv kernel. I know to get the oc, I have to go into setcpu and put the scaling to conservative, which I've already done. Ran quadrant, and got a score of 2790!
Great kernel!
Click to expand...
Click to collapse
mygti02 said:
wow......this kernel is amazingly fast......screw quadrant....mine is only coming up in the 900's but its way faster than the last lag fix i was using that was giving me 2700+ ratings in quadrant.
Great job!!
Click to expand...
Click to collapse
Instructions:
- Download the latest .zip provided below
- Put it on the root of your storage (the 14Gb one)
- Go into ClockWork Recovery
- Flash the .zip like you would a ROM
- Reboot
ENJOY!
Credits: Cyanogen, Wesgarner, Euegene_373, Barakinflorida
Download: http://kingxklick.com/forum/viewtopic.php?f=27&t=230
All my code is on
As you would expect, I am not responsible for anything that happens to your device
If you like my work follow me on Twitter:
CFS Changelog
Kernel #3
- NOW patched up to 2.6.29.6 from .29 (In settings it will still read as just 2.6.29)
- Many bug fixes to the kernel itself from the linux project
- Numerous patches to the CPU scheduler 'CFS' which we are currently using
- *NEW* 'Interactive' CPU Governor (You can enable this in SetCPU)
- Bluetooth patch: Enter active mode before establishing a SCO link. *thanks for finding the code Wesgarner*
- Root UID 0
- Root GUID 0
- AUFS2 standalone patches *via Cyanogen*
- Built with Cortex-a8
- Compiled with Neon Optimizations
- Using CT-NG toolchain *optimized for our CPU's*
- IPv6 fixes via mainline
- Netfilter tether: Fix unaligned memory access
- Netfilter stability enhancements *all via mainline, thank them*
- Much more I will add
Kernel #2
- Implemented "Speedy King Lag Fix"
- Some more voltage tweaks since it is going well
- NEW 'Interactive' Governor support
- Conservative governor tweaks (via Herver)
- Touchscreen is more responsive
- Compiled with optimizations (forgot to do this on #1)
- Compiled with neon opt
- Kernel compacted a little
Kernel #1
- Based off of Samsung Kernel Source
- Overclockable up to 1.2 Ghz! (thanks for the code unhelpful)
- Undervolted mid range frequencies for long battery life!
- Bluetooth patches (via Nick Pelly)
- Capped boot speed at 1 Ghz
- Using CFS CPU scheduler
- Added NEW BFQ I/O scheduler support! (thanks dark)
- Added CGROUPS block for BFQ
- BFQ scheduler set to default
- Anticipatory scheduler support
- Deadline scheduler support
- CFQ scheduler support
- Noop scheduler support
- Conservative CPU Governor set to default
- Ondemand CPU governor support
- Userspace CPU governor support
- Added support for EXT4 filesystems
- More I will add
thanks man, nice to have something we dont' have to flash in Odin
Great work!
Nice to see you in the vibrant neck of the woods king. I'll give this a shot in the morning. If I'm not going to oc will I notice much of a difference between this and the stock kernel?
Cyanogen, King...feel right at home coming from a 32B phone.
Paging Dr B said:
Nice to see you in the vibrant neck of the woods king. I'll give this a shot in the morning. If I'm not going to oc will I notice much of a difference between this and the stock kernel?
Click to expand...
Click to collapse
most definately, overclocking should be fairly stable though, ftw
kingklick said:
most definately, overclocking should be fairly stable though, ftw
Click to expand...
Click to collapse
is this cool too flash with the leaked JI2 Rom?
cdw9800 said:
is this cool too flash with the leaked JI2 Rom?
Click to expand...
Click to collapse
as long as samsung has not changed anything vital in their initramfs we should be just fine !
kingklick said:
as long as samsung has not changed anything vital in their initramfs we should be just fine !
Click to expand...
Click to collapse
ok ima give it a shot and report back
This is gonna sound noob but here it goes. I've never done research on what exactly kernels are and this is all new to me.
This new kernel I can flash like Rom will over clock my device to 1.2ghz or will it give me the option to? Can overclocking hurt my device in the long run?
Does this come with tools to over and underclock when I need to?
Any other info would be great. I'm on Eugene Franklin twis v2, no voodoo or lagfix yet.
Any other info would be awesome.
Sent from my SGH-T959 using XDA App
Works awesome on Frankin-Twiz update 1
buttery smooth
Works with Bionix
Installed, booted fast. Thanks for your hard work.
Good to see you back, King! Do you think this will work ok on Eugene's Hybrid R3? Also, I know some Vibrants (like mine) didn't like jacs OC kernel. Same issues here, or did the undervoltage kernel fix it?
Sent from my SGH-T959 using XDA App
Can we have info on how to revert this kernal back to stock if needed?
Very nice, glad to see another person compiling Vibrant kernels. Have you considered including the voodoo beta4 in one of your future builds?
Working fine on Vibrant 9
Will this work with a lagfix already installed?
What does the bluetooth patch do? I'm hoping improved A2DP quality, please say its so
Sent from my SGH-T959 using XDA App
so.. is it working with JI2?
all4degame said:
Can we have info on how to revert this kernal back to stock if needed?
Click to expand...
Click to collapse
You should just be able to flash it through recovery. It's available as a flashable zip in one of Eugenes threads.
Sent from my SGH-T959 using XDA App
Netarchy Nexus represents my foray into the world of kernel development for the Nexus S, having previously been working on kernel builds for the Evo 4g.
Current Change List vs the stock kernel:
- BFS (Courtesy of work by Con Kolivas) *In builds as marked*
- Overclocking up to 1.4ghz enabled *overclocking not active by default, use a tool such as SetCPU or CM7's cpu performance settings to overclock* (Remember kids, not all phones tolerate overclocking equally)
- BFQ (Courtesy of work by Paolo Valente)
- Voodoo Sound driver - Courtesy of Project Voodoo
- Voodoo Color (as of 1.2.4) - Courtesy of Project Voodoo
- CIFS support
- TUN support
- NFS support (as of 1.2.4)
- Updated kernel base
- Cpu policy fix to avoid crashes with SetCPU and screen off profiles (Courtesy of work by coolbho3000)
- EXT4 remount tweak
- Interactive Governor (Use a tool such as SetCPU to change governors if you want to use it *still in need of some tuning*)
- BLN on i9020 models (As of 1.3.0.1) Thanks to work by Neldar.
- BLN on i9023 models (as of 1.3.0.8) Thanks to work by akent.
- Sysfs interface to custom-under/over volt in realtime (As of 1.3.0.4)
- Smartass Governor (as of 1.3.0.11)
- SLQB (as of 1.3.1)
- Ezekeel's backlight dimmer sysfs interface (As of 1.4.0)
- Ezekeel's Deep Idle modifications (As of 1.4.1)
Click to expand...
Click to collapse
Kernel builds are currently tested against a stock rom and CM7, while they may work unchanged in other roms, your mileage may vary.
All source code is available on my github (see signature).
Be safe, -ALWAYS- make a backup before flashing!
Click to expand...
Click to collapse
*Standard Disclaimer: All packaged builds are provided with no guarantees as to their safety. By flashing, you assume any and all potential risks that running a custom kernel might entail.*
*A note to overclockers: If your phone is unstable when running an overclock speed, your particular phone probably can't handle that overclock and you should choose a lower clock.*
All kernel builds mirrored HERE.
*It is generally a good idea to wipe Cache and Dalvik-Cache when flashing a new kernel build to avoid certain problems usually related to Dalvik-Cache*
Downloads:
Experimental Version: 1.4.1 (These are testing builds that are more likely to have issues)
2.3.4+ based roms (Nexus-S AND Sprint Nexus-S 4G Phones):
CFS BUILDS:
Netarchy Nexus - 1.4.1-cfs (For stock 2.3.4 or higher roms)
Netarchy Nexus - 1.4.1-cfs-universal (Universal for non-stock 2.3.4 or higher roms)
BFS BUILDS:
Netarchy Nexus - 1.4.1-bfs (For stock 2.3.4 or higher roms)
Netarchy Nexus - 1.4.1-bfs-universal (Universal for non-stock 2.3.4 or higher roms)
"Stable" Version: 1.3.7
2.3.4+ based roms (Nexus-S AND Sprint Nexus-S 4G Phones):
CFS BUILDS:
Netarchy Nexus - 1.3.7-cfs-2.3.4 (For stock 2.3.4 roms)
Netarchy Nexus - 1.3.7-cfs-2.3.4-universal (Universal for non-stock 2.3.4 roms)
BFS BUILDS:
Netarchy Nexus - 1.3.7-bfs-2.3.4 (For stock 2.3.4 roms)
Netarchy Nexus - 1.3.7-bfs-2.3.4-universal (Universal for non-stock 2.3.4 roms)
Code:
Changelog:
Revision 1.4.1:
- Updated Ezekeel's Touchkey Dimmer to version 3.0 bugfix 4
- Integrated Ezekeel's Deep Idle mod, current to bugfix 5
- 45,333 rabid naked bunnies were harmed during the making of this kernel
Revision 1.4.0:
- Revert a patch that caused random reboots in certain usage situations
- Added Ezekeel's backlight dimmer sysfs interface (See instructions in second post on how to use)
Revision 1.3.9:
- Return to Deadline as default IO scheduler, using BFQ v2 could cause bugged encounters such as a never ending boot
- Applied kernel tweaks from the recent 2.3.5 OTA (mostly relevant for sprint users)
Revision 1.3.8:
- BFQ updated to BFQv2-r1
- Some build options that may have contributed to random reboots have been modified
Revision 1.3.7:
- Voodoo Sound driver updated to v10
- Testing out tiny rcu
- Touchscreen tweaks are no longer applied by default on boot. Users can still custom tweak touchscreen settings if desired
by editing /system/etc/init.d/98touchscreen and rebooting as before.
Revision 1.3.6:
- Wifi driver changes, rolled back some code that was causing problems
- Added Cyaniris' touchscreen tweaks back in the form of a user customizable sysfs interface (courtesy of work by Cyaniris).
Users can set custom values by editing /system/etc/init.d/98touchscreen , followed by a reboot for the changes to take effect.
Currently the default values are set, users that find the defaults not optimal might want to try some suggested settings by Cyaniris
of 35 for touchthr, and 20 for noisethr.
- Corrected a bug that would have caused reboots and/or other assorted badness when having the phone sleep at a frequency other than 800mhz
(Confession: I was an idiot and forgot to move over this fix from my 2.3.3 kernel trees when making the new kernel trees for 2.3.4, woops!)
Revision 1.3.5:
- Wifi driver updates, bugfixes
- JHash3 Added
- Cpu cache clearing fixes
- New compiler toolchain for builds, using gcc 4.5.2
- Interactive governor adjustments
- IO scheduler set to Deadline, seems to have a nice balance in performance
Revision 1.3.4:
- Remove touchscreen adjustments for now, they were causing problems on some phones.
Touchscreen tweaks will be revisited for a future build
- Add auto group process scheduler for CFS builds
Revision 1.3.3:
- Touchscreen adjustments that may improve touch response
- Update Voodoo Sound driver to version 9
Revision 1.3.2:
- Update BFS builds to BFS404
- Add Simple IO Scheduler and set as default
Revision 1.3.1:
- Smartass screen-off speed adjusted to address unresponsive programs during screen-off
- Smartass adjustments to improve responsiveness
- SLQB slab allocator added to help optimize memory allocation performance
- Some build configuration changes that may improve overall feel
- Ondemand governor up threshold adjusted to improve battery usage while still maintaining responsiveness
Revision 1.3.0.12:
- Adjustments to smartass to improve performance (there is probably still room for improvement)
- Default I/O Scheduler set to CFQ (previously BFQ), this may prove to be more stable in certain situations
- Some adjustments made to the CFS scheduler that may result in a better overall feel to CFS builds
Revision 1.3.0.11:
- Added Smartass Governor
(Not enabled by default, use setcpu or CM's cpu performance
settings to change if you want to try it out)
- Raised voltage cap to 1600mV for crazy people that
want to turn their phone into a reactor ;D
- Set config options in 2.3.4 kernel builds that should enable
NS4G compatibility for our newly arriving sprint friends.
Welcome to club nexus ;D
Revision 1.3.0.10:
- Update kernel base to 2.6.35.13
- Excessive stuttering in apps such as Gun Bros should be resolved
or significantly improved; some problems with memory handling
were introduced in 2.6.35.12 and are resolved in .13
Revision 1.3.0.9:
- The cause of super-lag has been found (Big thanks to twitch153 for helping me test)
- Introducing Universal builds! These universal builds are designed to be flashed on any
non-stock rom of the series marked (ie; Universal 2.3.3)
- Misc other tweaks to the kernel config that may result in an even smoother overall
experience
Revision 1.3.0.8a:
- Fix issue preventing USB debugging (and adb), and sdcard space from working
Revision 1.3.0.8:
- Updated to support the 2.3.4 rom update
- Lots of updates from upstream, including components needed to support
the forthcoming nexus s 4g (yes that means that I will be supporting the ns4g)
- Back to the 2.6.35.12 kernel base, the sdcard tweak has been scaled back
as it appears to have been causing excess lag
- BLN work for i9023 models from akent included (not tested), i9023 users may
find they can now use BLN
Revision 1.3.0.7:
- Revert back to 2.6.35.11 base until I can track down the cause of ridiculous lag in the .12 base
(Not that .11 was a bad performer by any means ;D)
- BFS builds updated to BFS401
- BFS users should find that they have regained their bootanimation
Revision 1.3.0.6:
- Voodoo driver updated to v8
- Custom voltage sysfs interface has changed,
the method used in 1.3.0.4 and 1.3.0.5 is not compatible.
See the guide in the 2nd post for details on the new method.
Revision 1.3.0.5:
- Raised max voltage cap by 50 mV for people who want to try raising the voltage a little bit on 1.4ghz
- More tweaks to try and address instances of "super-lag"
Revision 1.3.0.4:
- Corrected a bug that could cause a slightly higher voltage to be used at certain speeds (resulting in slightly faster battery drain)
- Added a sysfs interface for manipulating voltage levels at various speeds, see 2nd post for details
(read: this allows the possibility of custom under/over volting in realtime)
- Used a different build configuration that may address the occasional "super-lag" that appeared in 1.3.0.3
Revision 1.3.0.3:
- Update kernel base from 2.6.35.11 to 2.6.35.12
- Updated BFS version from BFS 363 to BFS 400 (BFS builds only)
- Raised default read-ahead value from 128 to 2048 (read: sd speed tweak built-in, scripts not necessary)
Revision 1.3.0.2:
- Updated Voodoo Sound driver to version 7
- Fixed a bug that made the sysfs file "scaling_available_freqs" not exist
Programs that must read this file for discovering/controlling available cpu speeds can now do so.
(This also means that CM7 users can set their cpu speeds from the cyanogenmod performance
settings instead of having to use SetCPU)
Revision 1.3.0.1:
- Add initial BLN support (Currently only functional on SAMOLED models [i9020])
Download the BLN control app from the market to use BLN functionality
Revision 1.3.0.0:
- More adjustments to the default colours to try and de-smurf the
previous adjusted defaults while still avoiding "Yellow tint shock"
- Voodoo sound updates (see github commit if you want more details)
- Fixed a bug that caused boot times to take significantly longer than necessary
Revision 1.2.9:
- Voodoo Sound v5 driver update
- Adjust default colours to avoid the initial "Yellow tint shock"
Revision 1.2.8:
- Voodoo Color gamma fix
Revision 1.2.7:
- Voodoo Color driver updates/fixes
Revision 1.2.6:
- Bring panel code up to date with official kernel
- Update Voodoo Color driver to v2
- Release initial cm7 2.3.3 compatible builds
Revision 1.2.5:
- Add 2.3.3 compatible builds
- Incorporate many updates from the newer 2.3.3 kernel sources,
including wifi driver updates, touchscreen updates, drivers for
future SLCD nexus-s variants, and more
(far too many bugfixes and updates to list, review the commit list on my github if you want details)
- Ext4 tweak should be working again in stock builds
Revision 1.2.4:
- Add NFS modules
- Make TUN built-in rather than modular (this may address issues some have had loading the driver)
- Add Voodoo Color
Revision 1.2.3:
- Update kernel base to 2.6.35.11
- Removed the ~56fps cap
- Conservative governor tweaked to perform better for users that choose to use it
- Greater rom compatiblity, particularly with roms that use specialized init scripts
Revision 1.2.2:
- 1.3ghz and 1.4ghz added to the frequency table for overclockers
- Default cpu speed on boot is 1000mhz, use a tool such as SetCPU to overclock
(No doubt I'll get some flack for this, but it's a very bad idea to boot into the max possible overclock when not all phones can tolerate it, so I consider it a necessary evil)
- Interactive Governor added, use a tool such as SetCPU to change to it if you want to try it out (Probably needs a bit of tuning to avoid annihilating battery, we shall see)
- CFS and BFS variants are now available
- Infused with the power of 1000 rabid naked bunnies
Revision 1.2.1:
- Ext4 hack should be working properly now
Revision 1.2:
- Fixed a condition where limiting max speed to 1000 would result in
potential underclocking to 800 (Thanks DebauchedSloth)
- Set hi-res timer to 1000hz
- Gave a little more power to the cpu at 1.2ghz, this may help those
having trouble running at 1.2 be more stable
- Integrated ext4 hack into the ramdisk builds
(ext4 hack is not technically a kernel issue but worth pointing out)
Revision 1.1:
- 1.2ghz overclock *really* works now -Thanks for the help Morfic-
- Cpu policy fix to avoid crashes with SetCPU and screen off profiles
(Courtesy of work by coolbho3000)
Revision 1.0:
- Initial release
- Add BFS scheduler
- Add 1.2ghz overclock
- Add BFQ
- Add Voodoo Sound driver
- Add CIFS support
- Add TUN support
- Update kernel base to 2.6.35.10
Custom Under/Over volting 101:
Code:
**As of 1.3.0.6 the method of custom voltage control has changed, read carefully!**
It is now possible for users to define custom levels of under/over
volting via a new interface in sysfs.
The interface file in sysfs can be found at
/sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
By default, the custom values are all zeroed out, so a
` cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table `
will show:
1400mhz: 1450 mV
1300mhz: 1400 mV
1200mhz: 1350 mV
1000mhz: 1250 mV
800mhz: 1200 mV
400mhz: 1050 mV
200mhz: 950 mV
100mhz: 950 mV
Modification of voltages is possible by echoing a string of 8 values
to the sysfs interface via the console, where the order of values
goes left to right from highest frequency affected to lowest.
To adjust the mV for a particular higher or lower than the default,
echo values divisible by 5 like in the following example from an adb shell (this is JUST an example, not guaranteed working values ;D):
` echo "1500 1400 1325 1275 1200 1050 900 850" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table `
Which has the following effect when examining UV_mV_table:
1400mhz: 1500 mV
1300mhz: 1400 mV
1200mhz: 1325 mV
1000mhz: 1275 mV
800mhz: 1200 mV
400mhz: 1050 mV
200mhz: 900 mV
100mhz: 850 mV
Rom developers, you can conceivably create custom scripts to
apply various under/over volt settings
For reference, these are the default voltages:
Default Frequency Voltage Table:
1400mhz: 1450 mV
1300mhz: 1400 mV
1200mhz: 1350 mV
1000mhz: 1250 mV
800mhz: 1200 mV
400mhz: 1050 mV
200mhz: 950 mV
100mhz: 950 mV
Additionally, there is currently a safety cap of 1600mV for max voltage,
setting a value higher than 1600mV will currently not have an effect greater than 1600mV.
(Read: You can set a value higher than 1600, but it will get dropped to 1600 behind the scenes)
This can be altered for future builds if I get feedback asking for it.
Backlight Dimmer:
Ezekeel said:
Based on the latest BLN version 9, I made some modifications to implement a backlight dimmer which does not need an external program (like cron) to trigger an off-switch.
To activate the dimmer, just echo the dim interval in ms (this is milliseconds; 1000ms = 1s) into /sys/class/misc/backlightnotification/in-kernel-dimmer. If you pass a value of 0, the dimmer will be deactivated.
Click to expand...
Click to collapse
FAQ:
Code:
Q: I'm getting a "Device or Kernel version not supported" error in Voodoo Control Plus!
A:The error is referring to the generic modules that voodoo control plus comes with to support
kernels that don't already have voodoo built-in (such as a completely stock kernel).
You can safely ignore this error, as voodoo is already built into the kernel.
Q: I'm getting SOD's (Sleep of Death) when undervolting!
A: You are probably undervolting too far
Q: OMG I'm getting a black screen (no boot animation) when booting a 2.3.3-based rom!
A: This tends to happen mostly on BFS builds, though it *can* occur on cfs builds (and even on the
stock kernel). The exact cause of this glitch is not known at this time, however, it is purely cosmetic.
You will notice that the bottom buttons are lit, and if you were to run adb logcat, you will see that the
phone is active. The phone is actually booting, just be patient.
Q: What are BFS and CFS?
A: They are task schedulers (they determine what processes get cpu time, how much, etc).
CFS (Completely Fair Scheduler) is the default scheduler in the official mainline kernel. It's a tried, tested, stable scheduler.
BFS (Brain **** Scheduler) is a third party scheduler written by Con Kolivas that must be patched into the kernel, and replaces the CFS scheduler. It tends to be faster in certain tasks, and is usually pretty stable, but sometimes there can be performance quirks.
Downloading and Testing! THx
Is using setCPU advised?
EDIT: Removed to avoid confusion as the info previously contained in this post is now outdated and invalid.
Someone give a shout out if this works with cm! Haven't got time to test it myself today. And thanks for your work!
Sent from my Nexus S using XDA App
I will put this in my ROM
Thanks
Just a heads up
Doesn't work with CyanogenMod 7 nightly
netarchy said:
SetCPU is not necessary.
You're free to use it of course, just remember that the NS idles at 800mhz, so if you use a screen off profile, take that into account.
Click to expand...
Click to collapse
Done. Works great with MoDaCo r10
demo23019 said:
Thanks
Just a heads up
Doesn't work with CyanogenMod 7 nightly
Click to expand...
Click to collapse
Thanks for heads up, thats sad. But thanks to the OP for the kernel its so nice to see.
Sent from my Nexus S using Tapatalk
Welcome.
Coolbho3k has a fix up. rewriting policies to enter sleep at 800 and restoring after.
Don't have link handy. You find it on his twitter.
Sent from my Nexus S
morfic said:
Welcome.
Coolbho3k has a fix up. rewriting policies to enter sleep at 800 and restoring after.
Don't have link handy. You find it on his twitter.
Sent from my Nexus S
Click to expand...
Click to collapse
Thanks for the tip
AAAAAAAAAAAAAAAAALOOOOVEEEEIIIIT !!!!!
1.4HGZ PLEEEASE
To make it cm7 compatible he can split_bootimg the cm7 kernel.
I'm looking into making one kernel working on both Bionix and cm7.
Currently it's 3 builds, Bionix, cm7 and stock for me. If I can unify it, I'll let you know.
Sent from my Nexus S
Please for CM7 KANG
dingdonghei said:
Someone give a shout out if this works with cm! Haven't got time to test it myself today. And thanks for your work!
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
nope, no boot with cm7. but it very successfully made my screen go black. woot!
Man this sounds good...tempted to flash my rom from nightly to try this thanks Dev for giving us more options.
morfic said:
To make it cm7 compatible he can split_bootimg the cm7 kernel.
I'm looking into making one kernel working on both Bionix and cm7.
Currently it's 3 builds, Bionix, cm7 and stock for me. If I can unify it, I'll let you know.
Sent from my Nexus S
Click to expand...
Click to collapse
THANK YOU MR MORFIC !!!!!!!!!!!!!!!
1.4Ghz it's possble ? sorry
morfic said:
To make it cm7 compatible he can split_bootimg the cm7 kernel.
I'm looking into making one kernel working on both Bionix and cm7.
Currently it's 3 builds, Bionix, cm7 and stock for me. If I can unify it, I'll let you know.
Sent from my Nexus S
Click to expand...
Click to collapse
Koush's anykernel can serve that purpose. It splits out the ramdisk from the current boot on the phone and combines it with the zImage of the new kernel (meaning no having to manually repack ramdisks to make various rom-compatible builds), then flashes the new boot image.
Once I have it playing nice with the NS I'll be able to post universal builds. One of the many things on my todo list ;D
Nice. Loved your work on my evo and stoked to try it here. More kernel devs means more choice and hopefully a richer collaborative spirit
Sent from my CM7 Nexus S!
kenvan19 said:
Nice. Loved your work on my evo and stoked to try it here. More kernel devs means more choice and hopefully a richer collaborative spirit
Sent from my CM7 Nexus S!
Click to expand...
Click to collapse
100% ! 100%
fps kernel by dr4go
This kernel is based on the newly released LG v20Q sources, but also includes every (still) needed fix from imperticus' NeoBlaze kernel. It should work on both Froyo and Gingerbread stock and MoDaCo based ROMs. It won't work with CyanogenMod based ROMs.
Prerequisites:
For the SWAP Enabler you need at least 384MB of free disk space on your /data/ partition. And because the swap enabler just triggers the creation of a swapfile it would be best if the data partition wouldn't be too full when executing it (fragmentation will decrease the swap performance by a whole lot!)
Features:
- EXT2/3/4 built in
- NTFS R/W built in
- OC/UV support, overclocking up to 1552MHz [based on cpasjuste] - I recommend SetCPU (http://forum.xda-developers.com/showthread.php?t=505419)
- SDRAM, VDE and GPU overclock [morfic]
- Voodoo Sound [supercurio]
- VR I/O scheduler
- BFQ I/O scheduler (default)
- SLQB memory allocator
- CIFS, TUN
- SWAP support (including swap notify patch for people who want to play around with compcache)
Credits:
- cpasjuste
- beene
- rmcc
- pastime1971
- morfic
- supercurio
- hell_97
- msk
- faux123
- imperticus
Greetings:
- carburano
- juri256
- ryan
INSTALLATION
1. Remove "boot settings" from Pimp My Cpu to reset to default values
2. Reboot into CWM (v5.0.2.7-r2 recommended)
3. Install zip file from SDCARD
4. Reboot
Kernel sources: Github
Personal note: Although I've already been built a lot of kernels (for the HTC Desire HD and also the LG Optimus 2X) I've never released them to public. And I mainly decided to do it, because I'm really really unsatisfied by the performance of this device. Imho it could and should perform a lot better. Join me if you would like to be part of this adventure.
And to conclude with imperticus words: Please also don't forget the 'Thanks button'.
CHANGELOG
2012-02-08
**Kernel v0.4:
- Based on LG's v20Q codebase
- Total removal of RAM hack (may be preliminary, hadn't the chance to look into a few issues, yet...)
- 1st try to fix 50hrs+ issue and a bluetooth incompatibility
2012-01-12
**Kernel v0.3a:
- Reverted the linux kernel patching series (apparently we are stuck on v2.6.32.9)
- Reduced RAM hack to 32MB
- Changed frequency table again (1015MHz replaced with 1040MHz)
- _safe installer added (@ Lo_RaT_PeNaT: that's the version for you to try)
2012-01-10
**Kernel v0.3:
- Improved battery usage
- Fixed a small Synaptic problem
- Patched to 2.6.32.53
- Changed default scheduler to BFQ
- Added some arm 2.6.35+ cpu features (=for snappier phone handling)
- Tweaked .config
- Faster startup time
- Improved EXT4 write performance
- Changed wifi driver
- Lots of sysctl tweaks
- Changed default max frequency to 1216MHz (previously 1408MHz)
- Changed frequency table (added a new frequency 1552MHz, removed 1100MHz)
- Tweaked voltages
- Integrated 64MB Hack
History:
Code:
[u]2012-01-09[/u]
**Kernel v0.2a_repack:
- Merged both installers (of v0.1 and v0.2) and created new one (it no longer overwrites the build.prop file)
[u]2011-12-31[/u]
**Kernel v0.2a:
- Reverted battery voltage scaling fix for Froyo sources
**Kernel v0.2:
- Added SWAP support
- Improved EXT2 and EXT3 performance
- Added NTFS R/W support
- Drastically improved disk and memory read and write speeds when heavy I/O is involved
- Added kernel version to status and removed localversion from it
- Integrated swap notify patch (if anybody wants to use compcache)
- New installer (and dalvik cache is now also automatically wiped)
- Changed default min frequency to 216MHz (previously 389MHz)
- Changed default max frequency to 1408MHz (previously 1015MHz)
- Changed default governor
**SWAP Enabler v0.1:
- First public release
**SWAP Disbler v0.1:
- First public release
[u]2011-12-28[/u]
**Kernel v0.1:
- First public release
FAQ
1. Does fps stand for frames per second?
No, it doesn't. And I will never ever release this information to anyone here. Sorry folks.
2. What is the difference between the normal and the safe version?
Only the installer. If you're stuck when booting, please try the _safe version. Otherwise it is the same kernel.
3. ...more to follow...
It's a great news to have a new kernel to try!
Edit:
ROM:Gueste2x_v2.1(base on v20e&v20m)
1.After 3 times test, quadrant score is about 2800 at 1Ghz.(HP SR1 is about 3300)
2.Andrev OC can work. I really like Myrt's apps to set UV&OC.
installed kernel on stock gingerbread rom.
got a quadrant score of 5700+ at OC 1.2 ghz (VR I/O scheduler)
changed I/O scheduler to BFQ and my score jumped to 6000+
dr4go,
Will you add swap support to your kernel? Because this is really great feature for our low memory device )
Fast. Smooth. Thanks!
Sent from my LG-P990 using XDA App
How come these kernels doesn't work with both CM7 and stock (like MCR) based ROMs? Isn't it possible to fix it? Modles? Kernel version? Too much patches provided by LG?
Remember HTC Hero development back in the days; almost all kernels worked independent on ROM. It was an exception (more or less) if the kernel didn't work with a specific ROM.
Looks like a great kernel, but won't flash a stock based ROM over CM.
What about battery life?
Sent from my LG-P990 using Tapatalk
ryaneu said:
installed kernel on stock gingerbread rom.
got a quadrant score of 5700+ at OC 1.2 ghz (VR I/O scheduler)
changed I/O scheduler to BFQ and my score jumped to 6000+
Click to expand...
Click to collapse
Could you please tell me how to change I/O scheduler?
ryaneu said:
installed kernel on stock gingerbread rom.
got a quadrant score of 5700+ at OC 1.2 ghz (VR I/O scheduler)
changed I/O scheduler to BFQ and my score jumped to 6000+
Click to expand...
Click to collapse
Thanks, that is exactly the information I need to improve the kernel. During HTC Desire HD days, there was no better scheduler than the VR I/O scheduler.
Could you also share your results you get with the Anticipatory-, NoOp- and Deadline-I/O scheduler? That way I could select the best one of those.
Thank you in advance.
dr4go
feav said:
dr4go,
Will you add swap support to your kernel? Because this is really great feature for our low memory device )
Click to expand...
Click to collapse
Noted. Imo you are right, that it would be a great feature for the LG Optimus P990.
Still a lot on my todo list... I already wanted to release it a few days back (as you may have noted I made the last commit on December 12th - since then I'm using it on my device.
Lastly... regarding the todo list: it's done when it's done - and as always: No information released to public before a new kernel it's out.
Stay tuned folks.
sibbor said:
How come these kernels doesn't work with both CM7 and stock (like MCR) based ROMs? Isn't it possible to fix it? Modles? Kernel version? Too much patches provided by LG?
Remember HTC Hero development back in the days; almost all kernels worked independent on ROM. It was an exception (more or less) if the kernel didn't work with a specific ROM.
Looks like a great kernel, but won't flash a stock based ROM over CM.
Click to expand...
Click to collapse
Don't get me wrong: I never had CM installed on any of my previous Android devices. My kernel may work on CM, but honestly... I have no clue.
Yes I've also wanted to try CM once, but as you know... you don't have time for everything.
If you are willing to test it, just flash my kernel (but leave also any other working CM kernel on your SDCARD just in case it doesn't boot anymore) and if you do so... please report back... also what works or what doesn't work...
Thanks in advance,
dr4go
I dealt want to try this kernel buy I do not want to f**k up my phone because it is very good with v20o and rock stable.
is it possible to post a stock kernel so I can return without a flash?
thanks
KillerbeeNL said:
I dealt want to try this kernel buy I do not want to f**k up my phone because it is very good with v20o and rock stable.
is it possible to post a stock kernel so I can return without a flash?
thanks
Click to expand...
Click to collapse
You can find your current kernel inside your zip file of your current ROM. And I doubt that it's the stock kernel you've currently have...
dr4go said:
You can find your current kernel inside your zip file of your current ROM. And I doubt that it's the stock kernel you've currently have...
Click to expand...
Click to collapse
its the rebuild stock v20o from hell_97 with same changelog v20o (?)
EDIT its hypnos v2.0 sp1 v20o version
KillerbeeNL said:
its the rebuild stock v20o from hell_97 with same changelog v20o (?)
Click to expand...
Click to collapse
This is your current kernel you have.
To restore it, there are two possibilities:
1) Copy it to your sdcard and flash it inside a root terminal using the commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p5
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p5
2) Copy the boot.img file inside your nvflash folder, and execute:
Code:
nvflash --bl fastboot.bin --download 10 boot.img
dr4go said:
This is your current kernel you have.
To restore it, there are two possibilities:
1) Copy it to your sdcard and flash it inside a root terminal using the commands:
Code:
dd if=/dev/zero of=/dev/mmcblk0p5
dd if=/sdcard/boot.img of=/dev/mmcblk0p5
2) Copy the boot.img file inside your nvflash folder, and execute:
Code:
nvflash --bl fastboot.bin --download 10 boot.img
Click to expand...
Click to collapse
tnx ..i made a nandbackup with CWM from my current rom and now a have flashed your kernel so if anything goes wrong I can go back
I will test this kernel for a couple of days for stability and battery use.
what's with the "windowsmgr.max_events_per_sec 120 " ??
LG 2X lcd screen has a refreshrate of 72hz so anything higher than 72 fps (120) could cause tearing in animations (?)
thanks for your effort and time
KillerbeeNL said:
tnx ..i made a nandbackup with CWM from my current rom and now a have flashed your kernel so if anything goes wrong I can go back
I will test this kernel for a couple of days for stability and battery use.
what's with the "windowsmgr.max_events_per_sec 120 " ??
LG 2X lcd screen has a refreshrate of 72hz so anything higher than 72 fps (120) could cause tearing in animations (?)
thanks for your effort and time
Click to expand...
Click to collapse
Max_events_per_sec sets OS(software opengl related params) related frames. While actual hw fps is setted in tegra frame buffer kernel driver. Increasing refresh rate at HW level(at kernel level) gives fake higher 2d (as benchmarking software read hw refresh rate to judge 2D),Infact worsen performance and in a long run it damages LCD Controllers and can be dangerous Actual supported refresh rate is 60hz for mobile QVGA and HVGA and you may find 60-62 with other company except LG.
Sent from my LG-P990 using Tapatalk
spica1234 said:
Max_events_per_sec sets OS(software opengl related params) related frames. While actual hw fps is setted in tegra frame buffer kernel driver. Increasing refresh rate at HW level(at kernel level) gives fake higher 2d (as benchmarking software read hw refresh rate to judge 2D),Infact worsen performance and in a long run it damages LCD Controllers and can be dangerous Actual supported refresh rate is 60hz for mobile QVGA and HVGA and you may find 60-62 with other company except LG.
Sent from my LG-P990 using Tapatalk
Click to expand...
Click to collapse
So, which value is recommended??? Leave it at 60??? Or 72 in our case????
Cheers!
el_charlie said:
So, which value is recommended??? Leave it at 60??? Or 72 in our case????
Cheers!
Click to expand...
Click to collapse
windows.mgr_max_events_per_sec <---that value is not at all harmfull you can keep any if you want 150-200
:good: First of all :good: Thank you for your patronage!!! :laugh::victory:
Before you do anything: This is purely at your own risk and I will not be responsible for anything that happens to your tablet. I flashed it on mine at my own risk.
Compatibility Information: There are 2 different versions. 1 for stock and 1 for Cyanogenmod. Even though the kernels are intended for the 3G tablet it will work just fine on a WiFi only tablet (like mine). This makes the build process less messy.
**Sources Fully documented v1.9 beginner friendly sources now available including the build script. If more explanations are required, please say so. However, remember that the explanations are not intended to be a blind step by step instructions of going from samsung source to A1.
TWRP V2.6.0.0: Please read: do not worry about any kind of "E:A: Render Error". This is a side effect of removing some image files to save place on the recovery image so it will fit on the 5MB. The error simply means it failed to show (render) and image file that it is looking for. This is not harmful at all. If you can't flash the recovery please try the dd method.
V2.6.0.0 3G Download
V2.6.0.0 Wifi Download
V2.5.0.0 3G Download
V2.5.0.0 Wifi Download
TWRP V2.6.3.0: There are no more E:A Render errors. All graphics that were removed are there. Also, the recovery will install supersu if no root is detected. That feature has also been restored. The kernel has been stripped of anything not recovery related to shrink it down. It also has selinux support which allows the "set_metadata" zip installation to work. The download is in the attachments below.
Changelog:
Changelog:
Voodoo sound <-- new to version 1.0
USB charging enabled as well as charging from other chargers *** fixed V1.5.4 thanks to pershoot
Overclock to 1.2GHz <-- new to version 1.2
NTFS modules enabled, ondemand default frequency scaler, noop default disk io scheduler <-- new to version 1.2.1
GPU overclock from 333MHz to 400MHz. <-- new to version 1.3
Overclock to 1.4GHz <--new to version 1.4
Support for Current Widget <-- new to version 1.5
CIFS enabled in kernel config, 1.4GHz attempted stability fix (thanks to jaswinky) <--new to version 1.5.2
Wifi driver compiled as module <--new to V1.5.3
More voltage anomalies fixed, updated battery driver to pershoot's 3.1 <-- new to V1.5.4 and V1.5.5XE
Fixed charging boot bug <--new to V1.5.6SE
(In case you were wondering 1.5.7 had an issue in it.)
Disabled frequency lock, added 1GHz default max (you can change it to 1.2GHz or 1.4GHz after boot), 216MHz default min CazeW's suggestion <--new to 1.5.8SE+XE
Enabled pershoot build/vfp optimization commit, added 150MHz minimum frequency <-- new to 1.5.9SE+XE
Boot script support (put yours as /data/local/a1init.sh) <-- new to V2.0
Smarter ram disk that only initializes 3G on 3G tablets<-- new to V2.1
1.5GHz && 1.6GHz OC available, cifs utf8 kernel module available <-- new to V2.2
Support for CM9 <-- new to V2.2CM
Enabled xbox controller module as xpad.ko <--new to V2.2.1
NTFS moved to kernel module instead of built in, CIFS moved to kernel module instead of built in, enabled option.ko and usb_wwan.ko for connection of 3G dongle, all nls charsets/codepages built as modules <--new to V2.2.2
V1.6.3 is pretty much V2.2.2 but without my custom ram disk. I've also tried a boot script method proposed by Toldo but haven't had time to test it yet. Please flash the CM9 stock kernel or Samsung stock kernel before trying V1.6.3.
Applied git patch to disable mmc_cap_erase <-- new to V1.6.4
Voltage control, cifs built in again <-- new to V1.7
Galaxy Tab 8.9 specific fix <--new to V1.7.1
Cyanogenmod charging mode fix <--new to V1.7.2
Galaxy Tab 8.9 specific feature <--new to V1.7.3
CM10 compatibility fix, enabled Samsung's powersaving governor <--new to V1.7.4
followed pershoot's "-defconfig: jb: unset TEGRA_CONVSERVATIVE_GOV_ON_EARLYSUPSEND" change to fix odd 450MHz capping issue <--new to V1.7.4b
Copied in pershoot's keyboard dock driver <--new to V1.7.5
801MB RAM enabled <-- new to V1.8
Rebased on pershoot's November 17 source <--new to V1.8.1
Back to samsung base, follow pershoot's suggestion of Nexus7 mtp drivers to fix mtp, enabled zRam <--new to V1.8.2
Reduced RAM to 785MB to prevent intense 3D games issue, enabled KSM (check in settings --> performance --> memory management)
(CM Version only) works on CM10.1 <--new to V1.8.4
Incorporated touchscreen death fix. Thank the user who reported it. <-- new to V1.8.5
Used part of pershoot's kernel config to get data usage working in CM <--new to V1.8.6
Added CM's version of the ROW (read over write) disk IO scheduler for GT-I9300<-- new to V1.8.7
Added XDA's grzwolf's solution to the hsic wakeclock problem <--new to V1.8.8
Added frandom kernel module <-- new to V1.9
Credits:
Supercurio: voodoo sound
Pershoot: voodoo port, usb charging, flashable zip, OC template, current widget setup
XDA forum's CazeW: used your replace suggestions to patch up wm8994_voodoo.c and wm8994_voodoo.h so it will compile properly, and finding the missing link for 1.4GHz OC, and disabling frequency locks
Task650: providing a nice, clean deodexed rom for me to try this on
XDA forum's RaymanFx: OC instructions
Me: GPU OC
XDA forum's jaswinky for valuable hints and checking my work over.
Xoom ICS kernel: for getting an approximate idea of voltages
(If I missed any credits, please forgive me as this is my first attempt at any kind of development)
XDA forum's motley for voltage control
XDA forum's Unknownzd for mmc_cap_erase patch
XDA's grzwolf for the hsic wakelock fix
Great to see someone else kernel developing, could be the start of something here... Lol, I wanna give this a try but I think It'll stop 3G working if I flash the 7510 kernel.
Sent from my GT-N7000 using Tapatalk 2
RavenY2K3 said:
Great to see someone else kernel developing, could be the start of something here... Lol, I wanna give this a try but I think It'll stop 3G working if I flash the 7510 kernel.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Care to try the 3G version I just uploaded? I don't own the 3G version but I followed the same idea for compiling the 3G kernel.
Welcome, nice of you to come to the party
Is there really no one that can test and leave test reports? If i would have been on sammy rom i`d been all over this.
Good luck dev
Flashed, wifi,3g and voodoo working,
well done.... Will test more for you and report back
Sent from my GT-P7500 using Tapatalk 2
kashortiexda said:
Flashed, wifi,3g and voodoo working,
well done.... Will test more for you and report back
Sent from my GT-P7500 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for your bravery!
Working on my 7500 even feels a little quicker too
Dang, you move quick, I've installed it but, how did you get the voodoo app to recognise the device as supported?
Scratch that, it was me being an idiot
Sent from my GT-N7000 using Tapatalk 2
Works fine on my P7500.( Voodoo, 3G and Wifi) Good work, Thnx!
3g + 1.1
all working great, including usb charging, 3g, wifi, and voodoo whilst device ON....finally !
Awesome. After flashing kernel, my useless wall chargers work. It is very smooth too. Great job.
Sent from my GT-P7510 using xda premium
Finally, the modified kernel!
Voodoo works perfectly.
It can even overclock the CPU to make and perfect kernel.
Maybe 1.6GHz.: D
XTeK2 said:
Finally, the modified kernel!
Voodoo works perfectly.
It can even overclock the CPU to make and perfect kernel.
Maybe 1.6GHz.: D
Click to expand...
Click to collapse
Overclocking abilities is quite a tall order for my current "skills". After looking at the instructions on how you would do it, the process looks much much more involving than just a manual patch job. Weird thing is that after an initial read through of the instructions it looks like a 1.2Ghz overclock code is in the kernel source but I'm not sure why it's not turned on.
kusgan said:
Awesome. After flashing kernel, my useless wall chargers work. It is very smooth too. Great job.
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
I was quite surprised to discover that the charger that comes in the box of the galaxy tab 10.1 actually sends some kind of "green light" to the tablet to begin charging. If the tablet gets the box charger it actually records "samsung charge !!!r" before activating the charging. If any other charger is connected the tablet records "invalid charger !!!" and disables charging in the next line of code. I just changed it so that it will record "other charger" in stead of invalid and enable charging after recording. (yes, the original code had those exclamation marks after charger).
is it ok with task ics rom ?
zerong said:
is it ok with task ics rom ?
Click to expand...
Click to collapse
You mean the task650 one? Of course it is! That's the only stock ics rom I've ever flashed on my tablet. I credited task650 in my first post for providing a clean deodexed rom to test on.
AAccount said:
You mean the task650 one? Of course it is! That's the only stock ics rom I've ever flashed on my tablet. I credited task650 in my first post for providing a clean deodexed rom to test on.
Click to expand...
Click to collapse
Yes task650 ! all is ok with your kernel ? i dont know if i have to wait a pershoot kernel for stock ics rom in order to enable voodoo sound and overcloking !
zerong said:
Yes task650 ! all is ok with your kernel ? i dont know if i have to wait a pershoot kernel for stock ics rom in order to enable voodoo sound and overcloking !
Click to expand...
Click to collapse
Yes, everything seems to be ok with the task650 rom. There is no overclocking available currently but voodoo is working.
Can i return to stock kernel if all isnt good? So where can i find a ics stock kernel ?
zerong said:
Can i return to stock kernel if all isnt good? So where can i find a ics stock kernel ?
Click to expand...
Click to collapse
From the nandroid backup you make before flashing anything.
I don't think a package has been made yet for ICS boot.img.
This kernel is no longer being updated. Please refer to kowalski kernel thread for CM10 ROMs.
Presenting CM10 kernel built from source with ramhack and OC/UV support by wkpark
Only for the new (unlocked ICS) bootloader!
This is RC's kernel, with patches by wkpark for ramhack and OC/UV. Supports OC upto 1.5 GHz.
Thanks to them for all their work. Also, thanks to pengus77 for bringing CM10 to the new bootloader
Built using my guide over here
Uses spica's HP supersonic toolchain
Works with CM10/MIUIv4 ROM on new bootloader only
Download links:
New and recommended powersaver version!
Includes pengus77's wifi drain fix (All credit to him for that)
Non-OC, to increase battery life and stability
RAM hack values 24 MB, 32 MB, 48 MB for increased smoothness
New experimental governors are absent in this ROM, which is meant to be a stable version for daily usage. The new governors have not been properly tested yet and are unlikely to be used by most of the users. They may be included in later builds after more testing. If you want to use them, flash the experimental kernel on the previous page.
This is the version recommended for daily usage. Try the 48 MB one first, and if camera gives problems, then try a lower RH value.
Download link for stable, powersaver version
Link to latest experimental version
Download link for older experimental versions
This is the link to my folder with all kernels for the new bootloader so far, in case you want to try some other version. Ramhack values are mentioned in the file names, and if it supports OC (not every phone will like OC) it is also mentioned in the file name.
Thanks to RC and wkpark, this would not be possible without them.
Warning:
I am not responsible if anything goes wrong with your phone.
If your phone does not like OC/UV, or freezes when overclocked, reduce the max frequency or dont use the OC version of the kernel.
If apps like camera give problem, try to use a version with reduced ramhack value.
To be flashed over the ROM without wiping data. Wipe only cache and dalvik cache
If you are having problems with the new kernel and wish to revert back to the stock kernel, flash your ROM again
Credits:
arcee and the rest of the CM team. Its their work it is based on
Donate to RC
wkpark for cracking the bootloader, new his patches, without which, there would be no ramhack or OC/UV
Donate to wkpark
pengus77 for bringing CM10 to the new bootloader and wifi battery drain fix.
This wouldn't be possible without him
spica1234 for his wonderful HP Supersonic toolchain
benee for his anykernel updater for star, and for all his work
Other devs for all their work (PM me if I forgot someone!)
Source: https://github.com/rugglez
Changelog:
29/12/12:
New version built with spica's supersonic HP toolchain
Integrated pengus77's latest (v3) wifi drain fix + bsod fix
27/12/12:
Experimental version released with new CPU governors (smartass v2 and hotplug), and simple I/O scheduler (default is still cfq), max frequency=1.2 GHz
Power saver version released without OC or new governors, and with pengus77's wifi battery drain fix
26/12/12:
Initial release
Max clock frequency is 1.5 GHz
Trying the 32mb oc kernel, seems ok so far, will report back any oddities,
I'm on penguss cm10.
i tested..............
Great news. Just two little questions:
- does this work with cm10.1 as well?
- are the Wifi drain patches from pengus77 included?
Regards,
Orgler
Thank u guy's! i will try new_CM10_kernel_1225_32M_OC.zip and report back!
angel_boulevard said:
i tested..............
Click to expand...
Click to collapse
And....?
orgler said:
Great news. Just two little questions:
- does this work with cm10.1 as well?
- are the Wifi drain patches from pengus77 included?
Click to expand...
Click to collapse
You could try it with cm10.1 but im not sure if it would work. Take a backup first. Wifi drain patches will be included with his permission and when he feels it is the right time (after the testing phase and all)
thanks for the hard work i think u can put like a changelog in thread and the features of kernel listed just avoid people asking same thinks all the time
included wireless.ko is the one patched by pengus? thank you in advance
edit: just checked, it's not the patched one
First impressions are good! Not much room for UV as 1ghz is already at 1000mV which is quite low already I think? But that is not important, just an observation.
Thanks Rugglez. Been waiting a while for an OC kernel on CM10 and no call bug either. This is the future for our phone I think.
I ´m testing the 48M_OC-Kernel on CM10.
I set max OC to 1,2GHz, but Antutu CPU Master shows Peaks at 1,5GHz! The Kernel is always scaling in its full available Range.
I tested it with different Settings and Gouvenours, nothing helps.
zerocoolriddler said:
I ´m testing the 48M_OC-Kernel on CM10.
I set max OC to 1,2GHz, but Antutu CPU Master shows Peaks at 1,5GHz! The Kernel is always scaling in its full available Range.
I tested it with different Settings and Gouvenours, nothing helps.
Click to expand...
Click to collapse
I just checked with "CPU spy" and yes it is hitting 1.5Ghz even though I have it set lower than that.
Noted. Will release 1.2 GHz and 1.4 GHz versions separately from next time
With pengus77 permission now, i'll integrate his wifi drain fix too.
Probably tomorrow
anjo88 said:
thanks for the hard work i think u can put like a changelog in thread and the features of kernel listed just avoid people asking same thinks all the time
Click to expand...
Click to collapse
Thanks for the idea, will add it.
rugglez said:
Noted. Will release 1.2 GHz and 1.4 GHz versions separately from next time
With pengus77 permission now, i'll integrate his wifi drain fix too.
Probably tomorrow
Thanks for the idea, will add it.
Click to expand...
Click to collapse
So we waiting to test
Can you put in the next update some more CPU governers and I/O scheduler?
zerocoolriddler said:
I ´m testing the 48M_OC-Kernel on CM10.
I set max OC to 1,2GHz, but Antutu CPU Master shows Peaks at 1,5GHz! The Kernel is always scaling in its full available Range.
I tested it with different Settings and Gouvenours, nothing helps.
Click to expand...
Click to collapse
Same here oc set to 1.2 but it's scaling up to 1.5 seems stable anyway.
Took one pic and gallery FCed and phone soft rebooted.
With OC 32mb kernel camera and video recording is working.
Sent from my LG-P990 using xda premium
lgnd said:
Same here oc set to 1.2 but it's scaling up to 1.5 seems stable anyway.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
I do a OC with default cm10 function and on antutu say 1200!
Sorry for being off topic. I really salute new generation of developers for optimus2x who never let us feel our main devs/modders have left. You guys are doing a fabulous job. Thanks to you all.
Gps does not working.
Tested with igo and maps.
Sent from my LG-P990 using Tapatalk 2
rugglez,
Please add pulse boost and hotplug governor. Thanks.