MoDaCo
I'm sorry if this has already been asked.
Am I able to use the Stock KF over clocking kernel on the KF MoDaCo Rom?
I'm sorry if this has already been asked.
Am I able to use the Stock KF over clocking kernel on the KF MoDaCo Rom?
[KERNEL][3.0.31][OC, CIFS, TUN]intersectRaven's Kernel 07/31/2012 17:34
- Thread starter intersectRaven
- Start date
- Status
I have used Raven's Kernel zip named 2.6.35.14_Stock_20120223_1512 on MoDaCo and haven't experienced any adverse effects.I'm sorry if this has already been asked.
Am I able to use the Stock KF over clocking kernel on the KF MoDaCo Rom?
Yea. I would really want some more features can be ported to this kernel. Like smartass V2 and vr scheduler, also it would be better to have 1.4 ghz overclock or above. A gpu overclock is needed as well. As I encounter some lag on this kernel even with 1.2 ghz overclock.
Sent from my Kindle Fire using xda premium
Might not be the Kernel Shadowgun plays great on mine with the newest CM7 Kernel and Chainfire
Sent from my Kindle Fire using Tapatalk
Same here, they play fine for me on Cm7 running the latest kernel with and without Chainfire.
I reinstalled and every thing has been working fine. For some reason my Kindle was acting like the screen had been turned off and on again witch will pause the games. Figured this out after installing auto-killer as a potential fix and selecting the option for an alternate preset for when the screen is off. Then after noticed that I would get a pop up banner from auto-killer that it chánged my values as if the device was left idle even though it was actively being used. Set a screen of profile in SETCPU after that also confirmed this. I'm going to go ahead and blame TWRP as I would always find oñe odd bug just about every time I flashed anything and also would find things missing or not working after a backup. For the most part they had been minor bugs like speakers not working after unplugging headphones until turning audio off and on or incorrect temperature readings. I cant say for sure TWRP is at fault but can verify that my Roms flashes and restores have all been bug free since making the switch to CWM.
Game is wonderful by the way, been also playing dead zone and without chainfire and I must say the Kindle handles these games much better then I anticipated. Big ups on the Kernel as they don't play nearly as well without.
Game is wonderful by the way, been also playing dead zone and without chainfire and I must say the Kindle handles these games much better then I anticipated. Big ups on the Kernel as they don't play nearly as well without.
Question, is this Kernel still Supported? Haven't herd much lately Despite my above comment I forgot to edit this is hands down the best CM7 Kernel going. Think TWRP was at fault with the above issue. Otherwise until CM9 is ready for prime time its definitely the best thing going Kernel wise.
It's because I thought that 3.0 would be released in a few days. I've been compiling some kernels but haven't released it publicly.
I think its because the kernel is almost perfect, so intersectRaven doesnt need to do any more tweaks.
It's because I thought that 3.0 would be released in a few days. I've been compiling some kernels but haven't released it publicly.
i love ur kernel. Waiting for ur update
Sent from my LG-P500 using Tapatalk 2 Beta-5
It's because I thought that 3.0 would be released in a few days. I've been compiling some kernels but haven't released it publicly.
I hope there will be some update for stock 6.3 firmware. For example, a 1.4 ghz overclock1
I hope there will be some update for stock 6.3 firmware. For example, a 1.4 ghz overclock1
1.4 might be too much. Alot of peoples fires can't handle 1.3
Sent from my LG-VM670 using Tapatalk
I think it is just the voltage issues, galaxy nexus with OMAP 4460 can OC to 1.6 GHz
Sent from my HTC HD2 using xda premium
The 4460 stock frequency is 1.5ghz, the nexus is just underclocked...
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
38This is my personally compiled kernel for the Kindle Fire with a few optimizations.
Acknowledgments:
DooMLoRD - for helping greatly in my initial trials on how to create kernels for the Fire
g1011999 - for providing a working .config
paulobrien - insecure boot image
franciscofranco - for some of the ARM optimizations which I've missed since I stopped modding the N1
hashcode - the 3.0 kernel base
Features:
- compiled using Mjolnir
- CPU overclocking code from OMAPZOOM repositories
- ARM code optimizations
What doesn't work:
same bugs as Hashcode's
Download URL:
http://intersectraven.euroskank.com/kernels/
Latest Changes:
20120730_08XX:
- backported cleancache and zcache improvements from 3.4
20120709_1619:
- added further tweaks to interactive scheduler
- rebased experimental optimization to minimize chance of faulty merge
20120703_1041:
- rebased to hashcode's 3.0.31 kernel with support for the touchscreen filter
- added an experimental optimization which in theory should make the kernel a bit more responsive...at least in theory...
20120619_2251:
- numerous ARM optimizations (most from the 2.6 series)
- ported CM's changes to the interactive governor and low memory killer
- GPU driver is compiled into the kernel
20120601_1145:
- integrated latest BFQ release 4 for selection (not default) in SetCPU
20120513_1557:
- integrated shutdown fix from hashcode
20120512_2044:
- first 3.0 release with almost all my tweaks
20120216_1740:
- final fix for TUN without module (if it still doesn't work, going to module in next release)
- UTF8 support for file systems
- some optimizations
20120211_1219:
- minor update for fixing OpenVPN based VPNs
20120207_19XX:
- unification release (unified all my modifications with my Galaxy Nexus kernel and restarted from scratch)
- ARM optimizations
- OC without thermal control
- compiler optimizations
- CIFS and TUN enabled
- now based on 2.6.35.14
- now in zip version for easier flashing
***DEPRECATED***
Instructions (stock WiFi driver):
1.) Boot to fastboot
2.) Test first using fastboot boot command
Instructions (custom WiFi driver):
1.) Turn off WiFi.
2.) Use adb push command to push tiwlan_drv.ko to /sdcard/
3.) Using root explorer, rename tiwlan_drv.ko from /system/etc/wifi to tiwlan_drv.ko.bak.
4.) Usring root explorer, copy tiwlan_drv.ko from /sdcard/ to /system/etc/wifi. Make sure permissions are same with other files in directory together with owner and group being set to root.
5.) Reboot to fastboot and TEST FIRST using fastboot boot command
Detailed instructions are on the next post.
***DEPRECATED***
GitHub:
http://www.github.com/intersectRaven/kindle-kernel12Detailed Instructions:
Turn off your device's WiFi.
From your command prompt issue the ff. commands:
Code:adb shell su idme bootmode 4002 reboot
This will cause your kindle to reboot to fastboot mode. Issue the ff. commands:
Code:fastboot -i 0x1949 boot bootnew.img
This will cause the Kindle to boot TEMPORARILY to the new kernel which I assume you downloaded from me.
If it doesn't boot normally, you can turn off your Kindle by holding down the power button for at least 10 seconds then turn it on again.
This will boot your Kindle to fastboot mode again.
If the kernel didn't work:
Code:fastboot -i 0x1949 oem idme bootmode 4000 fastboot -i 0x1949 reboot
This will reboot your Kindle back to normal.
If the kernel worked, here's how to flash it permanently:
Code:fastboot -i 0x1949 flash boot bootnew.img fastboot -i 0x1949 oem idme bootmode 4000 fastboot -i 0x1949 reboot
This should boot up with the new kernel.
Once you've booted up properly, issue the ff. commands to replace your stock WiFi driver with the new one.
Code:adb push tiwlan_drv.ko /system/etc/wifi/ adb shell su cd /system/etc/wifi chmod 644 tiwlan_drv.ko
Ensure that the permissions, owner and group settings for the new WiFi driver are correct by issuing:
Code:ls -l
Turn on your WiFi.988Unification Release!
This marks a complete restart of my kernel modifications! Branch modifications have now been back/forward-ported to/from this and my Galaxy Nexus source tree! Also, this marks a return to the roots of why I began modifying kernels! Focus is on energy consumption, compiler optimizations and code changes for more efficient processing! Also, only OC which is endorsed by the manufacturer is going to be integrated into the kernel.
