TrollSlayer version 3 Kernel
Ok folks, got a kernel for our A701 stock JB 4.1.1 and Evil Alex Purgatory
This is NOT for CM/AOKP/PA/ etc builds.
Keep in mind, I am not a kernel developer, and this is my first attempt. So it's pretty basic right now. I've been running it for a couple weeks, and it seems to be pretty stable.
First of all Credits and Thanks @civato - For being a wealth of info and a good Mate @sgt. meow - Govs & Schedulers and all his help @scrosler - For Help in compiling @faux123 - Dynamic Fsync & UV @verboth - Original Speedo Fake
The Kernel
Based on Acer JB 4.1.1 source
Compiled with Google toolchain
Features
CPU OC to 1500Mhz (on by default)
GPU OC to 520Mhz (on by default)
CPU UV tables
Dynamic fsync control (on by default)
Governors
lulzactive
lagfree
smartass2
pegasusq
Schedulers
row
sio
Gaming fix by faux123
RNDIS (not tested)
Cifs support
NTFS support currently via Stickmount app.
Dynamic fsync via Trickster app. I advise Trickster for settings.
Known issues:
OC apps not correctly reporting 1500Mhz on "ramp-up", but benchmarks report normal OC.
UV: I advise dropping voltage by 50mv at first, then by 25mv until you find the best voltage for your CPU.
Install: Flash through CWM. No need to do wipes, the install will do it.
Download Version 3
Alternate Download
Source:
Github https://github.com/moscowdesire/701trollslayer
Tarball http://d-h.st/EvQ
Enjoy
MD
Changelog
22/11/2013- Version 3 initial release
Notes
Dynamic Fsync
This is a goodie by faux123, so all credits go to him for creating this unique feature !
Many kernels just disable synchronous writes to file to speed up system. While this works neatly, it is also dangerous as processes believe that file writes are actually sync'ed to disk (or mmc media in our case) while this is not yet true !
The gain is a noticably smoother user experience, but the risk of doing so is to have a corrupted filesystem if the device crashes, user pulls battery, battery fully depleats ... so that the device is turned off unexpectedly.
To allow for the benefit, but to minimize the risk, faux123 created dynamic fsync, which while the screen is on, will defer file sync temporarily, but when screen gets turned off, a flush is called to synchronize all outstanding writes keeping your data safe.
Now it's up to you to either use this unique feature, at default it is enabled = Better performance
If you turn it off = writes will be done synchronously, which is safer but also slower..
Click to expand...
Click to collapse
Things to do for next version
Fix NTFS issue - probably fuse/ or Acer may have left debug code
OC companion core
Fine tune Governors as per cores ramping
Display sensitivity?
Good to see a (new) kernel for A701. But does this also work on A700 as well?
And a lil off topic: can anyone suggest me a good app to manage cpu/gpu?
Installed and.. awesome! :good:
Sweet. Someone try it on the 700! I won't get the chance on mine until tomorrow!
EndOfDays-Wildfire said:
Good to see a (new) kernel for A701. But does this also work on A700 as well?
And a lil off topic: can anyone suggest me a good app to manage cpu/gpu?
Click to expand...
Click to collapse
Trickster Mod seems to work well for me. If you're not going to turn off fsync, then you can use SetCpu. Trickster is a strange interface, and sometimes I forget to save my settings.
As with working on the A700, it might. Don't have a 700 so really can't tell you.
MD
Flashed it just now and works really well. Feels snappier :good:
Thanks
ExtremeRyno said:
Sweet. Someone try it on the 700! I won't get the chance on mine until tomorrow!
Click to expand...
Click to collapse
Considering Purgatory runs fine on the 700, I would say it "might" run on stock 700. But I see you are running Iconian. Vorbeth isn't around anymore, for a long time, but looking as his git, I saw he was using some CM code, which tells me Iconian may be a "hybrid" rom. If you get boot-loop, probably just flash his kernel package.
Actually never got around to changing my signature. Been running your E.A.P for most of a month now. I'll try the kernel over the weekend.
ExtremeRyno said:
Actually never got around to changing my signature. Been running your E.A.P for most of a month now. I'll try the kernel over the weekend.
Click to expand...
Click to collapse
Will look at the defconfigs and see if I can turn off the annoying "no sim card" function as it seems a few people use EAP on the 700. Would mean a new kernel build though.
Moscow Desire said:
Will look at the defconfigs and see if I can turn off the annoying "no sim card" function as it seems a few people use EAP on the 700. Would mean a new kernel build though.
Click to expand...
Click to collapse
That would be awesome. Thank you. If you do this don't forget to change device text in settings screen from A701 to A700.
Sent from my A700 using Tapatalk
Dc0de said:
That would be awesome. Thank you. If you do this don't forget to change device text in settings screen from A701 to A700.
Sent from my A700 using Tapatalk
Click to expand...
Click to collapse
You can do that in the /system/build.prop
MD
Is 1.6Ghz unstable?
minahasa said:
Is 1.6Ghz unstable?
Click to expand...
Click to collapse
1.6 is not yet incorporated into the dvfs tables
So glad you got this running. Hard work pays off.
sgt. meow said:
So glad you got this running. Hard work pays off.
Click to expand...
Click to collapse
Thanks Mate! You helped!
But got an issue that has happened to every Acer kernel source since the A500 days. NTFS breaks every time a kernel compiles using Acer source. Options for NTFS file system set to yes, or module in defconfig. Doesn't matter. When compiled, NTFS drives won't mount. Only option is Stick Mount. Stock kernels from Acer are fine.
On the Sammy forums, there was some info about the same issue (similar). Sammy's dev team reply was they left several DEBUG options on in defconfig. You ever heard of that? I've noticed a couple of the same are still set in the picasso_mf_defconfig.
If you can flash the stock kernel and grab the config.gz from /proc/ (I know you've probably tried this) try comparing both configs(the one in the stock kernel with the one you use).
sgt. meow said:
If you can flash the stock kernel and grab the config.gz from /proc/ (I know you've probably tried this) try comparing both configs(the one in the stock kernel with the one you use).
Click to expand...
Click to collapse
Hey, you're talking to MD! I can flash "anything"! :laugh:
Good idea and thanks! This will allow to see what configuration Acer uses when "they" compile.(actually forgot about proc/config.gz) must be getting old........
Thanks, I'll definitely try this on my a700. Will report back over a couple of days.
First I've to wait for my third charger
Hi,
I test the kernel for several days on my A700. In everyday life, there is no problem.
But when I play a video with the BSPlayer via HDMI to the TV, there is strong interference. It formed in intervals disorders.
The image is displayed in many thin horizontal stripes and it comes to short interruptions, the tone shifted more and more.
To continue to use the tablet helps, just restart. It seems to be due to the overclocking of the GPU.
With the stock kernel from your Rom is everything OK again.
I hope you understand what I mean and it helps in the development.
best regards
JoSch
Related
This is based off the latest Samsung kernel source (DI18) with some of my tweaks. Overclock to 1.2Ghz @ 1.25V is maximum. That is 50mV LESS than the voltage given in a stock kernel for 1Ghz!
This kernel is UNBELIEVABLY fast! Average Linpack scores of 9.5+ mflops & Quadrant scores of ~950-1050.
Battery life is great on this beast. Yesterday I ran it all day starting around 8AM, and I didn't hit low battery until 10PM. Thats the furthest I've ever gone, and almost double stock.
Just flash the zip in recovery. I have had no issues with this kernel, nor have any of my testers. This kernel is already included in AOSP Magic & Tha Boss ROM v.2 or above (it was actually made special for Tha Boss at the request of it's maker @KyleCole90). If you're running one of those ROMs you don't need to flash this, unless I release a new version here.
Use SetCPU to set the clock. You'll have to re-do the autodetect (press Menu, Choose Device, Autodetect) for it to decide the new speeds, and you may have to do it a few times. Also, if you flash a different kernel, or update then you'll have to re-detect as well.
Props to @Decad3nce for the BFQ patch from his Hero kernel, @Supercurio for his Voodoo Color mod for the i9000 I just ported it to Epic, Skeeterslint for helping me solve a problem with my ramdisk, @KingKlick92 for a baseline of safe values for voltages from his Vibrant kernel, @Herver for the conservative tweaks, and to Unhelpful on the Captivate forum for his helpful (*rimshot*) source for his Captivate overclock kernel.
If you have any questions or problems (shouldn't be any ) then Twitter me or email me. Also, I don't ask for donations, but if you're feeling generous and you like my work please check out my apps on the Market or send me a donation via the Paypal Donate link in my signature.
-------------------------------------------------------------------------------
Root Issues On Some ROMs:
There are some root issues on some ROMs due to the fact that they still use the old JoeyKrim root. It was never intended to be a permanent root method. Once we got kernel root it became moot. I recommend you ask your ROM dev to fix this, instead of complaining to me
Here's how to fix it if your ROM dev doesn't (just run this from a shell/command prompt, you must have ADB set up):
Code:
adb shell
remountrw
rm /system/bin/playlogo
rm /system/bin/jk-su
mv /system/bin/playlogo-orig /system/bin/playlogo
-------------------------------------------------------------------------------
Changelog:
MixUp-20101110-1036 -- Released 11/10/2010 10:37PM CST:
Added Smartass governor. Still beta. Not default, but available. Similar to interactive, but more responsive & better battery supposedly. Thanks to a dev in the Hero forums whose name I can't remember.
CIFS support
VooDoo Sound support. Still beta.
1.3Ghz & 1.6Ghz OC!
Light & CPU tweaks from Devin
Several more small tweaks I can't remember
This version is beta! I have NOT tested this one at all! I'm running FroYo atm, and I can't test this kernel since it isn't .32. Let me know of any (probably a few) bugs.
MixUp-20101024-847 -- Released 10/24/2010 8:47PM CST:
Switched back to conservative scheduler by default. Interactive is still there, but not default. It'll get set to default when someone fixes interactive.
Patched up to 2.6.29.6 (thanks @Nullghost)
Various scheduler tweaks, backported from newer versions
New BusyBox version
Back camera tweaks, sharpness & saturation upped a notch. I think its better, but if you disagree then take them down a notch in camera settings.
Front cam tweaks. Samsung -- People != blobbish vampires. Sharpness & color upped. No more pale blobs of Play-Doh.
RNDIS! Finally! DevinXTreme got this one goin.
Speaking of Devin, this is now a collab between him & I, with some (credited) kanging from @Nullghost
Optical sensor tweaks. I know, I know, they keep coming. It's good, I promise. I think I FINALLY fixed it.
IMPORTANT! Calibrate your battery after flashing this kernel, else it will decrease! To calibrate, charge your phone all the way (or insert a full battery), wipe battery stats in Clockwork, let it drain to ZERO, plug it in and charge to FULL! Do NOT put in a full battery after the discharge. Your battery should really improve after this.
MixUp-20101017-855 -- Released 10/17/2010 10:05PM CST:
New CPU tables again. Alleviate radio sleep issues. Anything left is just DI18's fault
Actually capped at 1Ghz at boot now, just change with the OC program of your choice
No more no-voodoo version. Voodoo is brightness issue free now, and its too much hassle to maintain two kernels. It may return eventually if I get around to integrating it to my config
Interactive CPU governor added & set as default. Ondemand still available as are the rest.
Fixed lots of config errors, depriving you of EXT4 & BFQ
More optimization for Cortex-A8
MixUp-20101005-809 -- Released 10/5/2010 8:09PM CST:
New CPU Tables (MOAR BATTERYZ!!11!)
More conservative tweaks from Herver (BATTERYZ!!!)
Updated to DI18 sources
New ramdisk
Limited to 1Ghz until changed in setcpu now, better battery by default & more stable for some users. Just up it in SetCPU if you want OCing
Tweaked minimum brightness levels
Screen doesn't fall to minimum brightness automatically until 1% battery now. Used to be 5%. You're welcome
I left up the old DG27 kernel for people who haven't yet upgraded to DI18, just in case the DI18 one causes issues for them
MixUp-20100926-323 -- Released 9/26/2010 3:55PM CST:
Switched to BFQ scheduler. See here for details.
Tweaks to the default Conservative governor. Scales up sooner to avoid hangups and scales down sooner to save battery
Added the Voodoo Color option (thanks @Supercurio for creating it, I just ported it to Epic). There are some issues with it as described at the link. If you don't like it, use the one without it instead of complaining, kthx
Fixed root issues finally, if you experience them you still have the JoeyKrim exploit installed. Bad user.
Undervolted 50 more mV across the board, battery life on this beast is amazing
Added Superuser Permissions app (thanks for the help, Skeeterslint)
adbd now runs as root by default. That means "adb shell" drops you straight to # instead of $
EXT3/EXT4 FS support included in kernel. Do with it what you will.
Changed to a different floating point emulation method that *may* yield better performance
NEON support in the kernel
MixUp-20100921-655 -- Released 9/21/2010 6:55PM CST:
Added Clockwork & ROM Manager support.
Judging from the reports I've heard and things I've seen, I'ma call this one Stoopid Fast. Just cuz it sounds cool
MixUp-20100920-630 -- Released 9/20/2010 6:30PM CST:
adbd now runs as root. This allows adb push to /system. It also enables adb remount to remount /system to RW or RO, but there is something missing from the ROMs that don't allow adb remount yet. I'm working on it.
Small tweaks to voltage table (I think) so possible better battery life on this one, but don't hold me to that. I'll be fine tuning them later on some more.
-------------------------------------------------------------------------------
Source:
My source is now on GitHub.
Stock DI18 Samsung kernel branch here. This is for beginning kernel devs. It's totally stock. Feel free to fork this or download the tree to start your own kernel base.
MixUp VooDoo is here. This has all my changes applied and I will push all my changes to it.
I did not have time to upload my source for the non VooDoo kernel today, I have the local repo done, but I only have access to a high speed connection when I go into town, and I didn't have time to upload this one while I had access. Really though, if you want the source for a non-Voodoo kernel its identical to this, just change the "drivers/video/samsung/s3cfb_tl2796.c" and "drivers/video/samsung/s3cfb_mdnie.c" files with the ones from the stock repo. Everything else is identical.
For devs wondering how I made ADBD run as root, I'm sure you already know how to do this, but if not do the following. Go to your ramdisk, open up default.prop, and then:
Change ro.secure=1 to ro.secure=0
Change ro.debuggable=0 to ro.debuggable=1
Change persist.service.adb.enable=0 to persist.service.adb.enable=1
Then recompile. That's it.
-------------------------------------------------------------------------------
And just to protect me:
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE!
Overclock kernels carry an inherent risk. You're pushing your hardware further than it's meant to go. Everything should be safe, and I've tested it myself and I trust it on my phone. But that doesn't mean it's perfect.
If *you* screw up and blame me, I will point at you and laugh. Deal with it.
i think i'll wait a bit to see if this is safe to flash
If I flash this kernel will I get those black screens like I did with Heros rom?
Sent from my SPH-D700 using Tapatalk
plmiller0905 said:
If I flash this kernel will I get those black screens like I did with Heros rom?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I don't notice them, but if you got them on his ROM you may well see them here too since its the same kernel. I recommend you set it on OnDemand scheduler with SetCPU instead of Conservative or whatever the default is
Geniusdog254 said:
I don't notice them, but if you got them on his ROM you may well see them here too since its the same kernel. I recommend you set it on OnDemand scheduler with SetCPU instead of Conservative or whatever the default is
Click to expand...
Click to collapse
Ok sounds good...what about having to hurry up and put the phone to sleep on the intial startup to stop the bootloops, do I have to do the same for this kernel as well?
Sent from my SPH-D700 using Tapatalk
plmiller0905 said:
Ok sounds good...what about having to hurry up and put the phone to sleep on the intial startup to stop the bootloops, do I have to do the same for this kernel as well?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Probably. I've gotten away without doing it, but the last couple boots I've had to. I'll build my own kernel later today and see if that fixes it. Just gotta download the Samsung source and set up a build environment for this instead of my Evo
Geniusdog254 said:
Probably. I've gotten away without doing it, but the last couple boots I've had to. I'll build my own kernel later today and see if that fixes it. Just gotta download the Samsung source and set up a build environment for this instead of my Evo
Click to expand...
Click to collapse
Ok I'll wait to flash this then cause trying to hurry up and put the phone into sleep mode at startup is hell. I'll be looking forward to your kernel and thanks for your hard work.
Sent from my SPH-D700 using Tapatalk
This kernel boot loops your phone. Even with a battery pull. I suggest flashing back to the stock kernel with Odin3.
casual864 said:
This kernel boot loops your phone. Even with a battery pull. I suggest flashing back to the stock kernel with Odin3.
Click to expand...
Click to collapse
are you putting it to sleep as soon as it boots??
Good so far thanx for posting it
BopChie said:
are you putting it to sleep as soon as it boots??
Click to expand...
Click to collapse
Even if I do that, whenever I put the phone to sleep it won't turn back on. Forcing me to do a battery pull.
casual864 said:
Even if I do that, whenever I put the phone to sleep it won't turn back on. Forcing me to do a battery pull.
Click to expand...
Click to collapse
Hmm did you put SetCPU at Set on Boot? I've seen that cause issues before. I know that it's working fine for me, although I occasionally have to do the instant-sleep trick on boot, but not always.
I know that it works for me, and it's reported working in the og. Grimey Goods thread as long as you do the instant-sleep. YMMV
so i dont set setcpu on boot or i do?
evoguyfhp said:
so i dont set setcpu on boot or i do?
Click to expand...
Click to collapse
You can give it a shot. I have it set on boot and it works for me but it's caused problems in the past if you set weird freqs. YMMV
Just posted a new version. Yes, I actually compiled this one
Let me know how it works. I'm going to bed. It's late here. I'll check feedback in the morning and respond to them tomorrow after class.
Enjoy
Geniusdog254 said:
Just posted a new version. Yes, I actually compiled this one
Let me know how it works. I'm going to bed. It's late here. I'll check feedback in the morning and respond to them tomorrow after class.
Enjoy
Click to expand...
Click to collapse
changelog?
[email protected] said:
changelog?
Click to expand...
Click to collapse
See OP. No more issues on boot (don't worry about locking and unlocking as soon as it boots anymore) and no wake issues. To make sure you have no wake issues, use the "ondemand" governor. That's the only one I've tested with. Can't guarantee that on conservative or powersave or any of the others. You can change them in SetCPU
Got It.. D'Oh..
PlankLongBeard said:
Only thing I ask for is a update.zip for returning to stock DI07 Kernal. After that all is well.. (BTW.. Thats for the Just In Case) Makes it Easier!
Click to expand...
Click to collapse
clockwork backup?
BopChie said:
clockwork backup?
Click to expand...
Click to collapse
Yeah, will be doing so, I forgot..
I've finally managed to get the 6210 kernel to compile AND work with the standalone kernel modules that samsung didn't bother to provide source for (ar6000 and j4fs.) It seems that the source on opensource.samsung.com uses different config flags than the source they used to compile for the shipping tablet.
The question is: Now that I can recompile it, what do I do with it? Well, I'll think about that and come up with some interesting answers. Probably a few efficiency tweaks, modifying the init.rc to allow for init.d parsing, and.. well, I don't know what else.
(I can find the source for the ar6000 adapter and j4fs, but I was extremely determined to get things working with the existing modules. I'm stubborn.)
Take care
Gary
Good luck gary!
Can you get overclocking enabled?
Sent from my GT-P6210 using xda premium
excellent job gary. bravo!
Excellent work. I might try my hand at this kernel development stuff. I did a lot of work with pascal a number of years back. Some c on the side. I might be able to add features that others have pioneered? We'll see... time is the enemy I believe. Sorry about the ramblings.
Sent from my GT-P6210 using xda premium
I've slimmed down the kernel a bit and also added support for init.d scripts (of course with no so-called ROM devs to take advantage of that, it's useless.)
I'm actually more interested in undervolting support than overclocking, but will add both around the same time. I should be able to post the kernel for the 6210 (only) sometime before the end of this year (local time.)
Take care
Gary
posted in the development section
garyd9 said:
I've slimmed down the kernel a bit and also added support for init.d scripts (of course with no so-called ROM devs to take advantage of that, it's useless.)
I'm actually more interested in undervolting support than overclocking, but will add both around the same time. I should be able to post the kernel for the 6210 (only) sometime before the end of this year (local time.)
Take care
Gary
Click to expand...
Click to collapse
Hey, users can throw stuff in init.d themselves!
(although most are too lazy to do so...)
i would like my ext partition on my sdcard to mount itself if you can do that gary! thanks and good luck!
I tried the kernel on mine and I don't like it. It's kinda choppy now going from page to page. How can I revert back to the stock kernel?
deezomaxima said:
I tried the kernel on mine and I don't like it. It's kinda choppy now going from page to page. How can I revert back to the stock kernel?
Click to expand...
Click to collapse
Please find the thread(s) in the dev subforum referring to ODIN and/or stock firmware.
Thanks Gary. Not sure if it's just my Tab but just being honest about what I was seeing.
deezomaxima said:
Thanks Gary. Not sure if it's just my Tab but just being honest about what I was seeing.
Click to expand...
Click to collapse
No problem.
Could you add tun module to support OpenVPN? The default kernel doesn't have that module so that OpenVPN doesn't work. Thanks!
maxofmin said:
Could you add tun module to support OpenVPN? The default kernel doesn't have that module so that OpenVPN doesn't work. Thanks!
Click to expand...
Click to collapse
I'm not familiar with that, but I'd be happy to investigate it. I'll add it to my 'todo' (but no promises on a timeline.)
maxofmin said:
Could you add tun module to support OpenVPN? The default kernel doesn't have that module so that OpenVPN doesn't work. Thanks!
Click to expand...
Click to collapse
Actually... It appears that 'tun' is already compiled into the kernel (directly - not as a module.) You should be able to use it without loading "tun.ko".
Can you please check this out?
Gary
Gary,
Correction on my assessment of your kernel. It's fine.
I'm back to stock and it's still doing what it was doing at moments and I've come to 2 conclusions:
1. The email widget I'm using on one page with a few icons
2. The Facebook widget I'm using on another page.
Pages with just icons seem to run fine.
Now I saw in your first post that you said you weren't into benchmarking for speed but have you benchmarked for battery life over the stock settings?
deezomaxima said:
Now I saw in your first post that you said you weren't into benchmarking for speed but have you benchmarked for battery life over the stock settings?
Click to expand...
Click to collapse
Only very non-scientific ones. (It's extremely difficult to ensure that exact same number of messages are pushed to my phone in a given period of time, that various forms of wifi interference are causing the same increases in power, etc.) That being said, I'm getting slightly better time on my battery with wifi set to "always on" compared to what I got on the stock kernel with wifi set to "never turn off when plugged in." (tablet was left in range of an AP in both cases.) I drop perhaps 5% in a 16 hour period with little to no screen time.
However, I'm also undervolting a bit with the custom kernel (values used are posted in another thread in this subforum), and have no active widgets beyond a single WX one that polls once/hr. I also changed the governor on my own to conservative at default settings (which saves a bit of battery as well.) Default for the kernel is ondemand which gives slightly better "snappiness."
Take care
Gary
Does it make a huge difference? Of course not. The undervolting is probably the only thing making much of a difference at all.
BTW, some of the tradeoffs between ondemand and conservative can be reduced by making some tweaks to the conservative governor:
https://github.com/Entropy512/linux_kernel_sgh-i777/commit/3b92eb76e72bbaa88aa8d87d306d1b61c9485912
Should be easy to port to .36
Main thing there if you don't want to change defaults is the stuff that reduces the minimum polling interval - the MIN_SAMPLING_RATE_RATIO lines - everything else is just tuning more aggressive (performance-tuned) defaults.
Thanks for the reply Gary.
So, I'm back on your kernel and installed SetCPU. I'm still messing with the settings to see what I get as far as battery life. I've had my Tab off charge since 7am this morning and it's now 1320 and Juice plotter is showing I have 67 hours of run time (95%) as opposed to seeing numbers in the 40s before hand. My device now wakes up out of sleep as it should instead of going into a non-responsive state sending me to reboot the whole device.
Everything is looking good now.
Please post your Infusion-Z and Zen kernel-related questions here...
Reserved
for future use
Tips, Tweaks, etc...
performance and battery tweak #1 - best antutu score - 4072
in testing the 2nd update of the infusion z kernel i came up with a configuration that consistently performed well on benchmarks (and in real phone use too!). I figured i'd share it here for others to try. (standard disclaimer from kernel thread still applies - you bork it, you bought it - not me). Feel free to post your experiences - any improvements i can confirm will be posted here..
flash coreA-16 kernel
in cwm, enable voodoo lagfix and system conversion
in phone cpu manager (i recommend voltage control) set the following:
- max to 1600 (minimum to 100)
- i/o scheduler - cfq
- governor - ondemand
- voltage - enable 1600 setting
- voltage - set undervolt to -50 across the board
- apply settings, then touch the menu key to save boot configuration
Click to expand...
Click to collapse
install adrenaline shot 14
- run only scripts 00, 01, 03, 04, 05, and 08 (others can be moved from /system/etc/init.d to your sdcard in case you want to try later).
run antutu benchmark...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
.•..•••..••.••••.•••.•••..•......••••..•.••.••••.•••.•.•..•..•••.•••..•..••..•.•..•......••..•...••.••••.••.•..•.••.•••..••..•••..•......••.•..•.•••.•....•......••.••••.••.•••...•......•••.....•••.•.•.•••..•..•••.....••.••••.•••..••.••..•.•..•.•••...•......•..•....••.••••.•••.•••..•......••.•.•..•••.•.•.•••.••..••..•.•.••.•••..••.•..•.••.••...••..•.•..•.•••...•.........••.•....•.•.
Any plans for ICS kernel
Aeonit said:
Any plans for ICS kernel
Click to expand...
Click to collapse
As soon as Samsung releases source for one I'm all over it
I wouldn't hold your breath though...
I know you know this , but for other readers: CM9 / AOKP threads have "ICS on Infuse" options in development. The Infusion-Z kernel is GB, intended for Samsung "stock" based ROMs.
entropy dd charging tweaks!! can't wait!!
Just wondering... its helpful for me and probably not anyone else lol but is there av out functionality?
There is AV out via the MHL to HDMI adapter that plugs into the usb connector. If your target device does not support HDMI there are converters available that should get you what you need.
If you are looking for something else, please reply with more specifics.
Zen Arcade said:
There is AV out via the MHL to HDMI adapter that plugs into the usb connector. If your target device does not support HDMI there are converters available that should get you what you need.
If you are looking for something else, please reply with more specifics.
Click to expand...
Click to collapse
I will look into that thanks... anyway like i mean through the headphone jack, like the original galaxy s phones did. I would provide you a link, but am currently up extremely late doing homework. I think our devices are capable of doing it, its just the addition was never added to the kernel.
Hi Zen
You can also throw us "Zen ROM" fully tweaked with your kernel.
What kernel to use with AEON ROM?
Forgive me for asking, but before I flash, I'd like to know what kernel users would recommend flashing for use with AEON ROM? And for my own edification, why do you recommend it? I'm still trying to get my hands around the difference between a ROM and a kernel.
Thanks,
atk
These kernels can be used on any Gingerbread based Roms for infuse.
please visit this link for further clarifications specially designed for new users. http://forum.xda-developers.com/showthread.php?p=22913686
Aeonit said:
These kernels can be used on any Gingerbread based Roms for infuse.
please visit this link for further clarifications specially designed for new users. http://forum.xda-developers.com/showthread.php?p=22913686
Click to expand...
Click to collapse
Fair enough. Thanks.
atk said:
Forgive me for asking, but before I flash, I'd like to know what kernel users would recommend flashing for use with AEON ROM? And for my own edification, why do you recommend it? I'm still trying to get my hands around the difference between a ROM and a kernel.
Thanks,
atk
Click to expand...
Click to collapse
There are kernels based on source code released by Samsung, intended to be run with ROMs based on Samsung source. There are also kernels based on the Android Open Source Project (AOSP) that will work with ROMs developed from AOSP sources. You cannot run an AOSP kernel with a Samsung-based ROM and visa versa.
In general, kernels are what manage the phone hardware and provide a common interface to the ROM and applications running on the phone.
If you are running Aeon you have two kernel groups to choose from: Entropy's daily driver - better on battery and includes fast charging hacks, or Infusion - geared more toward faster performance with overclocking. With updates in the past two months both provide most of the features available in the stock kernels along with being rooted to support custom ROMs.
You can click on the "ISET" link in my signature to get to the "super everything thread" with links to all the options available fo the Infuse.
Or, if you want to keep it simple, just flash Aeon and use the kernel that comes with the ROM.
Aeonit said:
Hi Zen
You can also throw us "Zen ROM" fully tweaked with your kernel.
Click to expand...
Click to collapse
It's #2 on the list
Zen Arcade said:
flash coreA-16 kernel
in cwm, enable voodoo lagfix and system conversion
in phone cpu manager (i recommend voltage control) set the following:
- max to 1600 (minimum to 100)
- i/o scheduler - cfq
- governor - ondemand
- voltage - enable 1600 setting
- voltage - set undervolt to -50 across the board
- apply settings, then touch the menu key to save boot configuration
install adrenaline shot 14
- run only scripts 00, 01, 03, 04, 05, and 08 (others can be moved from /system/etc/init.d to your sdcard in case you want to try later).
run antutu benchmark...
Click to expand...
Click to collapse
I have better values using noop and conservative. But my current high antutu score is 3911.
With cfq and ondemand - 3751
Still- 3911 is pretty great!
EDIT: But 4060 is even better! Still noop and conservative with -50mv down the line.
I use aeon and your newest kernel a oc to 1600 uv -50 all the way down,
when ever I play words with friends after I make a play and the ad pops up I click okay then it usually freezes up and get a black screen and I have to hit back a few times to get out and eventually get a fc screen then it works again.
Same thing if I go open a text message while playing for example and try and go back to words with friends it freezes up again..
What could be causing this?
It doesn't really do it with entropys dd just this one, it also does the same if I don't oc and leave it at 1200
Any ideas? Thanks
Sent from my SAMSUNG-SGH-I997 using XDA
csaint422 said:
I use aeon and your newest kernel a oc to 1600 uv -50 all the way down,
when ever I play words with friends after I make a play and the ad pops up I click okay then it usually freezes up and get a black screen and I have to hit back a few times to get out and eventually get a fc screen then it works again.
Same thing if I go open a text message while playing for example and try and go back to words with friends it freezes up again..
What could be causing this?
It doesn't really do it with entropys dd just this one, it also does the same if I don't oc and leave it at 1200
Any ideas? Thanks
Sent from my SAMSUNG-SGH-I997 using XDA
Click to expand...
Click to collapse
1. dont undervolt.
2. your phone may not be able to hand the oc to 1.6 ..try Zen-B 1.4
My phone has worked fine oc to 1600 before, and if I don't uv my battery life well suck..
Maybe I'll give b a shot..
Just seems multi tasking bogs down some could be a combination of tweaks conflicting, I'll try b or not oc with less uv and play around till something works
Sent from my SAMSUNG-SGH-I997 using XDA
csaint422 said:
My phone has worked fine oc to 1600 before, and if I don't uv my battery life well suck..Maybe I'll give b a shot..
Just seems multi tasking bogs down some could be a combination of tweaks conflicting, I'll try b or not oc with less uv and play around till something works
Sent from my SAMSUNG-SGH-I997 using XDA
Click to expand...
Click to collapse
I have never been a fan of oc...I have so many that love to oc their phones, pc...so on...imho oc degrades your hardware, sure you rocking it while it lasts on 1.6 + oc, and sure the phone can handle it, when it can. but just like any type of hardware i.e. computers, phones and so on, your gonna bring the hardware down. And will wear out....imo.
Not saying you should or shouldn't, just a thought, I can't afford to degrade my phone or computer, so I just run it at speeds that it was designed for, but even flashing custom rom is not safe either...so I understand the need for speed, but if your gonna fly....ensure you have parachute just in case you crash and burn... Ok enough of my old man talk...
Whenever I use the built-in Processor manager in CM9 (our CM9) and whenever I change the maximum MHz or the governor everything is fine. However when I'm using some apps such as browser it will soft boot in some times, not rarely but occasionally.
Is this normal? If it is then is SetCPU for Root Users worth buying to use for our phone (it looks very neat and has profiles too!)? If it is not then how will I manage my problem?
Would you point me to the "Processor manager" you are talking about? I didn't know CM9 had one!
Which build of CM9? Have you installed any other kernels or tweaks?
It is not normal in my experience with Team Acid / Hefe Kernel to have unexpected reboots.
What are you trying to manage with the app and when? That may impact the choice.
I use System Tuner (Pro) and find it does what I need. Then again, I don't change settings once I've got a kernel dialed in.
Posted from my SGS4G, thanks to Team Acid development
jeffsf said:
Would you point me to the "Processor manager" you are talking about? I didn't know CM9 had one!
Which build of CM9? Have you installed any other kernels or tweaks?
It is not normal in my experience with Team Acid / Hefe Kernel to have unexpected reboots.
What are you trying to manage with the app and when? That may impact the choice.
I use System Tuner (Pro) and find it does what I need. Then again, I don't change settings once I've got a kernel dialed in.
Posted from my SGS4G, thanks to Team Acid development
Click to expand...
Click to collapse
In "Settings" under "Performance", then go to "Processor". Once there you will see some settings pertaining to the processor.
Build R8, no tweaks or custom kernels.
So will SetCpu for root users app work for our phone?
th3controller said:
So will SetCpu for root users app work for our phone?
Click to expand...
Click to collapse
It did for GB. Haven't tried it on ICS. Jeff mentioned System Tuner above and I couldn't agree with him more. It's the only app I use for setting OC/UV as well as I/O schedulers. Try the free version first. It does everything though. SO if you like it kick down for the paid version.
I have used setCPU since I bought it way back when. It works. Jeff's the man though I might have to switch just because lol.
TwitchyEye said:
Jeff's the man though I might have to switch just because lol.
Click to expand...
Click to collapse
What am I chopped liver? llol jk. Jeff is indeed a great resource to have around.
TwitchyEye said:
Jeff's the man
Click to expand...
Click to collapse
Cedric's the man -- the author of System Tuner Pro. His support has been beyond expectations. I'm very picky about what I pay cash for. His pride in his products and quick, intelligent responses has more than earned the relatively small price that he asks for his "Pro" versions. Past that, he doesn't overly "cripple" his ad-supported versions.
I've never tried SetCPU, but I know many people have had great success with it.
Many of the "tweaks" are governor-specific. Most "reasonable" programs work through the exposed "sysfs" entries that allow one to read/set parameters of the kernel. In this case, the governor, governor parameters, and the voltage table.
I actually experience the same problem with the soft reboots after switching to CM9
So the answer is yes, set cpu will work for our ice cream sandwich phone?
Cause I will buy it now.
Seems to be working fine... For now, when I first tried to set clock settings at:
Min: 200 MHz
Max: 1200 MHz
Governor: SmartAssV2
I/O Scheduler: Deadline (Jeff what scheduler do you suggest? Or is Deadline fine?)
After these settings were put in effect, I went back to the home screen, the screen froze with a weird effect. I had to do a battery pull, rebooted phone and tried to reapply settings again. It worked and I'm going to report back if weird stuff happens.
th3controller said:
Jeff what scheduler do you suggest? Or is Deadline fine?
Click to expand...
Click to collapse
I've stayed out of the scheduler fray as much as I can. From what I have read, there is a very significant difference between them when you have spinning disks. I've also read that the ones that work well for spinning disks aren't so good for flash media. I've heard that there is a new one in the works for mainline Linux (FIOPS), but it is far from production quality. Not clear how any of them interact with Samsung's umm, well, "unique" approach to managing flash -- we're neither an SSD nor a raw card for internal memory. I switch between deadline and noop with the phase of the moon, and haven't personally noticed an astounding difference between them. I couldn't tell you what I have set right now.
Modified kernels overclocked.
I am not responsible if this bricks your device(no reason that it should but just in case).
***Update 7/12***
kernel allow usage of ext4 or f2fs on same partition.
this will not format to f2fs.
to use f2fs go here: http://forum.xda-developers.com/showpost.php?p=53427756&postcount=1&nocache=1&z=32066198618380
Bootimg_ext4orf2fs_CM11_Overclock_20140712.zip - 3.85 MB
MD5:ead39d8e659b3bc63518b0508a0e6ddb
Features
Hashcode's latest updates
http://review.cyanogenmod.org/#/c/65480/
GPU Overclock to 512 MHz up 33% from stock, CPU Overclock 42% up to 1.7 GHz
Linaro dropped for now
source https://github.com/Maromi-/kernel_omap_bowser-common
Linaro
Makefile
ifdef CONFIG_CC_OPTIMIZE_MORE
KBUILD_CFLAGS += -O2 -fmodulo-sched -fmodulo-sched-allow-regmoves -fno-tree-vectorize
endif
KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
-fno-strict-aliasing -fno-common \
-Werror-implicit-function-declaration \
-Wno-format-security \
-fno-delete-null-pointer-checks \
-march=armv7-a -mtune=cortex-a9 -mfpu=neon \
-ffast-math -fsingle-precision-constant \
-fgcse-lm -fgcse-sm -fsched-spec-load -fforce-addr
tate_android_deconfig
-CONFIG_CC_OPTIMIZE_size=y
+# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
+CONFIG_CC_OPTIMIZE_MORE=y
Old Stuff
https://www.dropbox.com/s/rniaco65frepkye/CM11_Overclock_20140418a.zip
MD5:13df3ec88983ad54498ec065486f0d33
Smartreflex Override
]https://www.dropbox.com/s/9j0v4htkyznewis/CM11_Override_20140331.zip
md5:d9986618035115fbd6a5df3b5903b8f0
THANKS TO:
Hashcode for his kernel
Galaxy Nexus XDA Forum Devs
Maromi said:
Modified kernels undervolted and overclocked they each also boot at max speed. Tested on PA and CM10.1.
1.4 GHz(try me first)
https://www.dropbox.com/s/va7u6t0dlomgc5r/UV_Modified_Kernel_KFHD7_1.4GHz.zip
MD5:e7810e7272b98fca97c02a0b519ad6d7
1.5 GHz(did you try 1.4?)
https://www.dropbox.com/s/1kd5qpi9o7w2pwl/UV_Modified_Kernel_KFHD7_1.5GHz.zip
MD5:060c9aaad58016580e39a4f066dfb0f1
1.3 or 1.6 GHz(boots at 1.6 GHz)
THANKS TO:
Hashcode for his kernel
Click to expand...
Click to collapse
The people who experienced a freeze at the boot animation of Hashcode's CM10.1 build will also experience a freeze here (I tested both myself), no matter which .zip file you choose. If you wish to proceed, please make sure you have Hashcode's 1.2GHz kernel on the sdcard, so that you can just flash that over and not have a paperweight on your hands. A backup would also come in handy.
Maromi said:
Modified kernels undervolted and overclocked they each also boot at max speed. Tested on PA and CM10.1.
1.4 GHz(try me first)
https://www.dropbox.com/s/va7u6t0dlomgc5r/UV_Modified_Kernel_KFHD7_1.4GHz.zip
MD5:e7810e7272b98fca97c02a0b519ad6d7
1.5 GHz(did you try 1.4?)
https://www.dropbox.com/s/1kd5qpi9o7w2pwl/UV_Modified_Kernel_KFHD7_1.5GHz.zip
MD5:060c9aaad58016580e39a4f066dfb0f1
1.3 or 1.6 GHz(boots at 1.6 GHz)
THANKS TO:
Hashcode for his kernel
Click to expand...
Click to collapse
see if meta.inf is well placed
---------- Post added at 06:46 PM ---------- Previous post was at 06:44 PM ----------
Maromi said:
Modified kernels undervolted and overclocked they each also boot at max speed. Tested on PA and CM10.1.
1.4 GHz(try me first)
https://www.dropbox.com/s/va7u6t0dlomgc5r/UV_Modified_Kernel_KFHD7_1.4GHz.zip
MD5:e7810e7272b98fca97c02a0b519ad6d7
1.5 GHz(did you try 1.4?)
https://www.dropbox.com/s/1kd5qpi9o7w2pwl/UV_Modified_Kernel_KFHD7_1.5GHz.zip
MD5:060c9aaad58016580e39a4f066dfb0f1
1.3 or 1.6 GHz(boots at 1.6 GHz)
THANKS TO:
Hashcode for his kernel
Click to expand...
Click to collapse
add governors and io scheluders and gpu overclock (or adding a new value, so we will have 3 frequencies, no the default 2) please
seokhun said:
The people who experienced a freeze at the boot animation of Hashcode's CM10.1 build will also experience a freeze here (I tested both myself), no matter which .zip file you choose. If you wish to proceed, please make sure you have Hashcode's 1.2GHz kernel on the sdcard, so that you can just flash that over and not have a paperweight on your hands. A backup would also come in handy.
Click to expand...
Click to collapse
are you wiping anything before or after flashing?
also of note is that im just sharing what i did to my device.
Maromi said:
Modified kernels undervolted and overclocked they each also boot at max speed. Tested on PA and CM10.1.
1.4 GHz(try me first)
https://www.dropbox.com/s/va7u6t0dlomgc5r/UV_Modified_Kernel_KFHD7_1.4GHz.zip
MD5:e7810e7272b98fca97c02a0b519ad6d7
1.5 GHz(did you try 1.4?)
https://www.dropbox.com/s/1kd5qpi9o7w2pwl/UV_Modified_Kernel_KFHD7_1.5GHz.zip
MD5:060c9aaad58016580e39a4f066dfb0f1
1.3 or 1.6 GHz(boots at 1.6 GHz)
THANKS TO:
Hashcode for his kernel
Click to expand...
Click to collapse
Now that you guys are making new kernels does this mean we are getting any closer to enabling USB host mode? maybe also enabling the GPS that's on the motherboard?
http://www.ifixit.com/Teardown/Kindle+Fire+HD+Teardown/10457/2
This Aldo shows FM transmitter/received included. Just curious if its possible
Sent from my Amazon Kindle Fire HD using XDA Premium HD app
Shawnsch said:
http://www.ifixit.com/Teardown/Kindle+Fire+HD+Teardown/10457/2
This Aldo shows FM transmitter/received included. Just curious if its possible
Sent from my Amazon Kindle Fire HD using XDA Premium HD app
Click to expand...
Click to collapse
I was gonna say FM radio but then i remembered it has no antenna!
unless it works the same way as some mobile phones where the headset 3.5mm jack acts as a receiver, But idk!
GPS would be awesome though
Sent from my Amazon Kindle Fire HD using XDA Premium HD app
AmrBanawan said:
unless it works the same way as some mobile phones where the headset 3.5mm jack acts as a receiver, But idk!
Click to expand...
Click to collapse
Some? dont you mean all? XD
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
Thanks Maromi, this is working flawlessly for me and my benchmark is up to 9195!
Sent from Hell... in HD!
AmrBanawan said:
I was gonna say FM radio but then i remembered it has no antenna!
unless it works the same way as some mobile phones where the headset 3.5mm jack acts as a receiver, But idk!
Click to expand...
Click to collapse
the Tune In app is pretty amazing
could you add frandom, is faster, 10-50 times faster than urandom
https://github.com/Ryuinferno/frandom-android crossbreder has a script to use it, no the module, the module has to be made
4. Remove /dev/random as it's blocking . Link it to non-blocking /dev/urandom. Since /dev/random is blocking and designed to protect us from Quantum alien cryptographers with mathematical certainty and urandom is non blocking pseudo-random device that most apps and OSs are using anyway and with Haveged running, is as secure anyway as it's very difficult to empty the entropy pool faster than Havege can replenish it. Pre ICS devices have a lot to gain with this but ICS+ devices show visible gains too.
5. Frandom support - CrossBreeder now supports linking both your random devices to the extremely fast alternative - Frandom ( http://billauer.co.il/frandom.html ). This module is orders of magnitude (10-50 times) faster than the standard character devices ( Check this out - http://forum.xda-developers.com/showpost.php?p=37409586&postcount=134 ). The erandom character device also installed by Frandom doesn't use up system entropy at all on top of being fast. You will need to ask your ROM developer to develop the kernel module for you and then place it in /system/lib/modules. CrossBreeder will then try and load it and if successful, make all the necessary adjustments so that both /dev/random and /dev/urandom are pointing to /dev/frandom and /dev/erandom respectively. The speed benefits are to be seen to be believed. But since each ROM requires a unique kernel module, this option is left optional ( but auto detect ).
feature 5 is inportant, but the other is useful too to make our kindle very fast, or better, we couldnt see any difference but, there will be a gigant difference in system. i dont know, so many people say it is exellent
seokhun said:
The people who experienced a freeze at the boot animation of Hashcode's CM10.1 build will also experience a freeze here (I tested both myself), no matter which .zip file you choose. If you wish to proceed, please make sure you have Hashcode's 1.2GHz kernel on the sdcard, so that you can just flash that over and not have a paperweight on your hands. A backup would also come in handy.
Click to expand...
Click to collapse
I don't believe this is correct. Although my tablet was freezing with hashcode's original 1.5ghz kernel, both of these 1.4 and 1.5ghz builds are completely stable for me. It's worth trying even if you had problems with the other, however it may not work for all devices.
-Ken
will this work with the 4/22a build?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
codepoet82 said:
I don't believe this is correct. Although my tablet was freezing with hashcode's original 1.5ghz kernel, both of these 1.4 and 1.5ghz builds are completely stable for me. It's worth trying even if you had problems with the other, however it may not work for all devices.
-Ken
Click to expand...
Click to collapse
Hashcode said there were problems with hardware, and that not all 4460s are the same, so whether you think it's correct or not is irrelevant. The tablets behave differently in many circumstances from one another.
seokhun said:
Hashcode said there were problems with hardware, and that not all 4460s are the same, so whether you think it's correct or not is irrelevant. The tablets behave differently in many circumstances from one another.
Click to expand...
Click to collapse
All hardware is not created equal, same reason some people may get more overclock out of a cpu then the next person with an identical setup.
I'm one of those regularly experiencing a freeze with CM10.1 (20130508 build).
I flashed the latest Hashcode build (20130511), which obviously works for me, because clock is back at 1.2GHz.
Then I flashed your kernel UV_Modified_Kernel_KFHD7_1.4GHz.zip, wiped cache & dalvik and I booted up with no problem!
But are you sure the boot is at maximum frequency?
I'm asking because, as soon as I select 1.400 MHz as max frequency in the Performance section, my KFHD7 instantly freezes.
EDIT: just had again a video acceleration during playback with MX Player (S/W decoder).
seokhun said:
Hashcode said there were problems with hardware, and that not all 4460s are the same, so whether you think it's correct or not is irrelevant. The tablets behave differently in many circumstances from one another.
Click to expand...
Click to collapse
Here, let me restate my original comment in the manner it was intended to be read.
"Seokhun is wrong, even if your tablet didn't work with hashcode's first 1.5Ghz kernel you should try these. Don't let his narrow minded view of how he thinks the world works prevent you from trying this yourself."
Now, why don't you take your bad attitude and put it in a box with a little pink bow on top, and go give it to mommy. She can tell you how you're a beautiful and unique snowflake, and the adults around here can get back to doing the actual work.
-Ken
degiovab said:
I'm one of those regularly experiencing a freeze with CM10.1 (20130508 build).
I flashed the latest Hashcode build (20130511), which obviously works for me, because clock is back at 1.2GHz.
Then I flashed your kernel UV_Modified_Kernel_KFHD7_1.4GHz.zip, wiped cache & dalvik and I booted up with no problem!
But are you sure the boot is at maximum frequency?
I'm asking because, as soon as I select 1.400 MHz as max frequency in the Performance section, my KFHD7 instantly freezes.
EDIT: just had again a video acceleration during playback with MX Player (S/W decoder).
Click to expand...
Click to collapse
It doesn't boot up at 1400, it boots at 1200 and you have to set it to 1400 if you want it there.
codepoet82 said:
Here, let me restate my original comment in the manner it was intended to be read.
"Seokhun is wrong, even if your tablet didn't work with hashcode's first 1.5Ghz kernel you should try these. Don't let his narrow minded view of how he thinks the world works prevent you from trying this yourself."
Now, why don't you take your bad attitude and put it in a box with a little pink bow on top, and go give it to mommy. She can tell you how you're a beautiful and unique snowflake, and the adults around here can get back to doing the actual work.
-Ken
Click to expand...
Click to collapse
I stated in the original reply that I tried all the .zips that Maromi provided along with Hashcode's, you donut. If you're going to be a douchebag about it, might as well go to do something else if you don't have a more civilized comeback. By your logic, we should ignore Hashcode's advice, because Maromi's kernels and Hashcode's kernel are actually quite similar.
The problem, according to Hashcode, lies with the devices, not the kernels themselves, you donut! How dare you make a statement regarding my mother, you insolent fool. If you've got any sense of decency, at least do it tomorrow, and not on Mother's Day!