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.
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..
This kernel is based on Thalamus's Oxygen Kernel but with AVS and he's given me permission to post it here for testing.
I implemented AVS from scratch (based on the Code Aurora kernel) and it seems to work well for me.
AVS uses some hardware to emulate the longest gate delays through the CPU datapath. If the delay is longer than expected, the CPU voltage can be decreased, if shorter then it can be increased. This means that the CPU is always running near the minimum voltage it requires and because power consumption rises with the square of voltage this is a good thing.
Here are the results of some initial tests (full load, no idle):
Clock Speed, Without AVS, With AVS
1113600,234mA,223mA
998400,207mA,190mA
768000,158mA,138mA
499200,111mA,93mA
384000,90mA,79mA
245000,70mA,64mA
So there are power savings of about 8-15%
All patches are initially pushed here:
https://github.com/dzo/kernel/tree/2.6.35-bravo-exp
and should end up here:
https://github.com/thalamus/kernel/tree/2.6.35-bravo-exp
You can see the current status of AVS by doing:
Code:
cat /sys/module/avs/parameters/status
Doing:
Code:
echo 1 > /sys/module/avs/parameters/debug
will put lots of debugging info in the kernel log.
To disable AVS do:
Code:
echo 0 > /sys/module/avs/parameters/enabled
The minimum voltage is set to 900mV but you can change this using e.g.:
Code:
echo 850 > /sys/module/avs/parameters/vdd_min
Putting too low a value in here will crash your phone because AVS seems to have trouble with low frequencies.
I also added some extra frequency steps, 76.8MHz and 192MHz.
Don't expect huge power savings, the CPU is only one of the things using power on our devices.
I think AVS is a nice idea and I'd like to know how stable it is on other people's phones.
To install, flash the attached update zip from recovery.
Please don't use this kernel unless you are fairly well informed about what you are doing.
15/4/12: Updated kernel with higher vdd_min
Going to give this a test now, I'll report back later.
How did you produce those mA readings btw?
have you tried using other kernels like Eviolets one? does it really save much more battery than EVs?
is it 100% stable??
with the kernel using some hardware to calculate the voltages needed wouldnt it take some more power to get the calculations done?
cez10 said:
have you tried using other kernels like Eviolets one? does it really save much more battery than EVs?
Click to expand...
Click to collapse
Why don't you try it and find out instead of asking questions.
is it 100% stable??
Click to expand...
Click to collapse
I think the words '[Kernel]Experimental' in the thread title are a clue.
with the kernel using some hardware to calculate the voltages needed wouldnt it take some more power to get the calculations done?
Click to expand...
Click to collapse
The overhead of the calculations is negligible.
So this is only for gingerbread AOSP ROMs or works on Sense as well?
lvnatic said:
So this is only for gingerbread AOSP ROMs or works on Sense as well?
Click to expand...
Click to collapse
Oh my...people just want to be spoonfed on XDA these days.
This kernel is based on Thalamus's Oxygen Kernel
Click to expand...
Click to collapse
As Oxygen is an AOSP ROM it's fairly clear that it's not going to be a sense kernel isn't it?
Thanks for sharing this.
What are the available governors? I can't find this information on github.
Will switching between governors (depending on phone state) cause any issues with the voltage change, that aren't advised?
_thalamus said:
Oh my...people just want to be spoonfed on XDA these days.
As Oxygen is an AOSP ROM it's fairly clear that it's not going to be a sense kernel isn't it?
Click to expand...
Click to collapse
He never mentioned it is specifically for AOSP or Sense ROMs. I was wondering if this is just a separate script, not kernel dependent. But if I give it a 2nd read then yes, it seems indeed it is an entire kernel, my bad, no need for a spoon...or w/e it means.
lvnatic said:
He never mentioned it is specifically for AOSP or Sense ROMs. I was wondering if this is just a separate script, not kernel dependent. But if I give it a 2nd read then yes, it seems indeed it is an entire kernel, my bad, no need for a spoon...or w/e it means.
Click to expand...
Click to collapse
Don't listen to Thalamus. He has no time for people less "knowledgeable" than him. There was a time where I thought a kernel was a kernel.
I thought I had escaped his unhelpful comments when I left Oxygen thanks to his attitude (if you don't like his attitude, then tough is the general gist of it). If he was a shop owner he would go bankrupt, quickly, as he has no people skills whatsoever.
If he wasn't a dev, he would be labeled a troll, yet he is allowed to get away with being nasty to people. When will XDA introduce a -thanks button?
I think the saying goes, if you don't have anything nice to say, then don't say anything at all.
Thanks, this one looks like a good project
As to stability: i've been using this kernel for a couple hours without issues, with very small draining btw; anyway a few minutes ago the phone became unresponsive: i was just typing a message with whatsapp, clocked 192x806, and a freeze occurred. A soft reset did the trick.
Keep up the good job
Edit: i'm on beta 2 fyi...
chronicfathead said:
Don't listen to Thalamus. He has no time for people less "knowledgeable" than him. There was a time where I thought a kernel was a kernel.
I thought I had escaped his unhelpful comments when I left Oxygen thanks to his attitude (if you don't like his attitude, then tough is the general gist of it). If he was a shop owner he would go bankrupt, quickly, as he has no people skills whatsoever.
If he wasn't a dev, he would be labeled a troll, yet he is allowed to get away with being nasty to people. When will XDA introduce a -thanks button?
I think the saying goes, if you don't have anything nice to say, then don't say anything at all.
Click to expand...
Click to collapse
Hahahahahaha.
That cheered me up, I'm having a crap day.
Happy to be of assistance.
Edit: You prove how little you know about me by saying that I have no time for people less knowledgeable than me. That is totally untrue. I spend a lot of time helping people who are less knowledgeable than me. What I have no time for is laziness, people who won't help themselves or idiots. There is a big difference.
_thalamus said:
Hahahahahaha.
That cheered me up, I'm having a crap day.
Happy to be of assistance.
Edit: You prove how little you know about me by saying that I have no time for people less knowledgeable than me. That is totally untrue. I spend a lot of time helping people who are less knowledgeable than me. What I have no time for is laziness, people who won't help themselves or idiots. There is a big difference.
Click to expand...
Click to collapse
I only base my observation on posts of yours that I have read. Rather than shooting people down, advise them so they can improve their knowledge.
sent by touching my Desire
In Airplane mode i had 2mA battery usage all night without AVS and 5mA usage with AVS. This is via Battery monitor widget.
Xinot said:
In Airplane mode i had 2mA battery usage all night without AVS and 5mA usage with AVS. This is via Battery monitor widget.
Click to expand...
Click to collapse
AVS has nothing to do with power consumption while the device is asleep. When the phone sleeps, the CPU is power collapsed, i.e. is completely powered down. AVS only changes the voltage while the CPU is awake.
The Kernel work great on Miui 1.4.8 since 2 days! No reboot or freeze... and in idle with JiuceDefender, 652Mhz max ondemand over 3h the device lost only 2% accu
Thanks for your work
Sent from my HTC Desire using XDA App
I've just updated the kernel in the first post to increase the minimum voltage and remove some possibly unstable frequencies.
Should be more stable now.
dzo said:
AVS has nothing to do with power consumption while the device is asleep. When the phone sleeps, the CPU is power collapsed, i.e. is completely powered down. AVS only changes the voltage while the CPU is awake.
Click to expand...
Click to collapse
OukkiDoukki! So i have something else going on here...
Thanks running sweet keep up the great work using on GV 2.0
Sent from my HTC Desire using XDA Premium App
cez10 said:
have you tried using other kernels like Eviolets one? does it really save much more battery than EVs?
is it 100% stable??
Click to expand...
Click to collapse
Just a quick post to say that I've been testing this kernel for 2/3 days (actually the version that Thalamus has in his experimental github) and find the battery usage to be the same. But the AVS code seems much cleaner than the implementation I have.
As for stability, I haven't had a single crash yet. And overall speed seems better than on my kernel.
Quadrant also confirms this.
Regards,
EViollet said:
Just a quick post to say that I've been testing this kernel for 2/3 days (actually the version that Thalamus has in his experimental github) and find the battery usage to be the same. But the AVS code seems much cleaner than the implementation I have.
As for stability, I haven't had a single crash yet. And overall speed seems better than on my kernel.
Quadrant also confirms this.
Regards,
Click to expand...
Click to collapse
Do you think you will be compiling ManU 1.5 from this source then?
WildKernel
As some of you may know, I've been working on a custom kernel for ICS/JB and its about done (for a first release).
Also I was previously planning on a beta testing for a selected few, but I released I won't have enough time to be hosting testing sessions, so how about this. The kernel is know free to use for the public, but all I ask is that your report and compare. I'd like to see if there's improvement or loss between the A6 kernel and this (battery, performance, etc.). Also please report anything good and bad so that I know what to keep and what not to keep for a final release. This also helps me push out fixes faster when presented with lots of information.
Current kernel features include: (If feature begins with a * then check below for more information)
Universal kernel compatible with all AOSP (NOT SENSE) ICS & JB roms
rebased to CAF (custom) Linux 3.0.39 kernel
Optimized Built in Low-memory killer w/ Fugeswap (as seen in the v6 Supercharger)
Optimized ram usage/handling (Swap & Zram)
Increased Wi-fi connectivity range
*Low & High power Wi-fi scaling steps
*Badass Governor
Lazy Governor
Imported Snapdragon optimizations used by the Sensation (Thanks Romanbb)
Lagfree Governor
Fast charging for unknowns and when plugged in to computers
HIGHLY Tweaked for the perfect battery life and performance
Bluetooth code from CAF
V(R), simple, deadline, noop, and CFQ I/O schedulers
*Ondemand & Intelli(gent)demand Governor
Stable Undervolting of the CPU
increased SDcard readahead speed
Tweaked Flashlight
Added more clock steps to the GPU for compatibility with low power browsing and GPU OC @ 320 mhz
Please wipe cache and dalvik cache
I dont suggest using SetCPU as it may cause bugs such as reboots, use CM or AOKP's built in cpu speed feature
Download Universal flasher for ICS and JBhttp://www.mediafire.com/download.php?q9bhv68k8dvai13
(Flashable for S-ON coming tomorrow when I have time)
You may find my source hosted @ Github
More information:
Badass Governor: This governor has built in profiling (like used in SetCPU but not as battery & Ram consuming). This is also the default and highly recommended governor. This governor features a 3 phase system CPU profiling system. This will change your CPU speed based on usage. This saves a lot of power as your speed doesn't just keep at one clock no matter how much your using you phone. A similiar profiling system is also used for the GPU and such.
Ondemand and Intellidemand Governor: Intellidemand is based off the Ondemand governor but features a 2 phase CPU profiling system with some added tweaks. Ondemand also now has early suspend support for low power browsing to save battery.
Wi-fi Low and High power scaling steps: This is a feature that will determine whether to use High or low power voltages on the Wi-fi chip to save battery. eg: Wi-fi will be turned to low power when idle or screen off. Wifi will be turned to high power when actively in use or in progress of a download. Take note that high power wi-fi voltage isn't necessarily "High" power but more of just "Stock HTC" power.
View all public kernel releases
Changelog:
Code:
[B]Sep 3 - ver003[/B]
1. Bluetooth updates upstream
2. Downgrade to linux Kernel v3.0.39 with custom libs to *really* fix lag
3. Badass back to default governor as the most stable
4. More LMK tweaks
[B]Sep 2 - ver002[/B]
1. Implemented USB forced fast charge v3.1
2. Downgrade to linux Kernel v3.0.40 to fix lag
3. Ondemand tweaks, early suspend updates, and is now default governor because of balance of stababilty, battery, and speed.
4. LMK tweaks
5. Updates to bluetooth from CAF (more battery saving and stable)
6. Updates to scheds from faux
7. mpdec ready but disabled until stabalized
8. A lot of improvements since ver001
Thanks:
TeamDS
Strapped365
faux123
Tamcore
cretin45
showp1984
RomanBB
and any others I may have missed
reserved for James (He'll be supplying statistics such as battery reports, cpu logs, benchmarks etc.)
Post statistics and they will be copied here
Nice
Hastily spouted for your befuddlement
Awesome. Hope this fixes the battery drain problem from the A6 kernel.
Sweet. Will test tonight.
Il test this but not until Saturday morning will I have solid feedback
I'm going to have to use both Ankers plus my stock battery for tomorrow as I have school, then a football game, then a roadtrip so I will definitely take shots and post back with great contrasts I'm sure
Thanks XMC
::Respect::
---------- Post added at 10:02 PM ---------- Previous post was at 09:31 PM ----------
CRUD! I got to my PC, downloaded it and read its not in Boot.img format! IM S-ON D:
Sorry wild, can't get it booting. Been trying forever. I'll redownload again when I get home.
P.s: it boots, but it goes right into a reboot after I hit homescreen. I don't think I can use alogcat to pull one, so I'll have to wait till I get back to my computer. Perhaps a dmesg a well.
You also plan on making something for sense ROMs?
If not would you mind if I grab your patches and implement it to a more enhanced virtuous kernel?
Riyal said:
You also plan on making something for sense ROMs?
If not would you mind if I grab your patches and implement it to a more enhanced virtuous kernel?
Click to expand...
Click to collapse
Hey maybe even if xmc your planning on doing a sense one... Maybe if no offense allow Riyal access to those things as you might learn from his enhancements to a sense kernal and such... Also additional development for DS
:what:
::Respect::
well im on my computer. the error (though im no expert) seems to be here
if you need the full logcat let me know and i'll try grab it again. that's the error going on right when the homescreen gets laggy on boot, right before it reboots.
i don't know if this is important to you, but this is what i get in logcat right before reboot
I'm sure i followed directions. I hope I'm not doing something wrong.
Edit: yep. Definitely not an expert. So it stopped rebooting after I unchecked "set on boot" under performance. Will be reporting back.
CoNsPiRiSiZe said:
Il test this but not until Saturday morning will I have solid feedback
I'm going to have to use both Ankers plus my stock battery for tomorrow as I have school, then a football game, then a roadtrip so I will definitely take shots and post back with great contrasts I'm sure
Thanks XMC
::Respect::
---------- Post added at 10:02 PM ---------- Previous post was at 09:31 PM ----------
CRUD! I got to my PC, downloaded it and read its not in Boot.img format! IM S-ON D:
Click to expand...
Click to collapse
I flashable for S-ONs will come soon sorry
Riyal said:
You also plan on making something for sense ROMs?
If not would you mind if I grab your patches and implement it to a more enhanced virtuous kernel?
Click to expand...
Click to collapse
to be honest I hate sense and I doubt I'll be developing anytthing for it anytime soon.
Riyal, i'm open source so feel free to do whatever you wish. If you need help with me pointing out specific commits lemme know
ekoee said:
well im on my computer. the error (though im no expert) seems to be here
if you need the full logcat let me know and i'll try grab it again. that's the error going on right when the homescreen gets laggy on boot, right before it reboots.
i don't know if this is important to you, but this is what i get in logcat right before reboot
I'm sure i followed directions. I hope I'm not doing something wrong.
Edit: yep. Definitely not an expert. So it stopped rebooting after I unchecked "set on boot" under performance. Will be reporting back.
Click to expand...
Click to collapse
are you using setcpu?
No, I'm running cm 9.1.0. Under settings > performance > cpu settings or whatever it is, if you have set on boot checked, the phone runs funny. I unchecked it in a desperate attempt to figure out what's going on, and it's been pretty stable ever since.
xmc wildchild22 said:
reserved for James
Click to expand...
Click to collapse
LMAO! :laugh: You GO James!!! :good:
CoNsPiRiSiZe said:
CRUD! I got to my PC, downloaded it and read its not in Boot.img format! IM S-ON D:
Click to expand...
Click to collapse
Can't we just extract the zImage from the universal kernel flasher, rename it boot.img, and flash? I thought they were analogous...
Edit: I tried it. Didn't work. "Boot Magic check failed". Guess I was thinking of Samsung devices. Bummer, I really wanted to try this.
Ok after a 10 minute self lesson on kernel kitchen I managed to compile a boot.img. Booted right up but I had nofrills with an "apply on boot" setting which screwed me over. Severe lag. I managed to access that app in slow motion and deselect the apply on boot nonsense. Now we are in business
Don't forget to uncheck all governor apply on boot settings before flashing! Also, on first boot go to a view CPU frequency place on your phone so you can wait until the phone settles before rebooting/doing stuff. Takes a little longer than you would expect.
So far the performance seems good, I'll report back on battery life later.
Edit: 3 consecutive reboots during 3 consecutive calls. Switching back to 3.0.30 (A5) for now. Since I didn't flash this officially I'd take this experience with a grain of salt but it is similar to what ekoee is reporting so IDK.
Hi xmc! Not that I question the knowledge of the senior htc community developers here but this battery issue I am facing with ROMs like virtuous is already nagging me out.
Now compiled yours and shocked that it also has the battery bug.(The not going to 100% bug)
So I decided to really look up the battery driver carefully awhile ago and noticed something strange in it. I noticed this days ago and thought this was ok but thought I would stand up and ask today.
In
arch/arm/mach-msm/htc_battery_8x60.c
htc_batt_get_battery_info
Could you tell me why calculation of battery is like this?
htc_batt_update->batt_current = htc_batt_info.rep.batt_current - htc_batt_info.rep.batt_discharg_current;
Click to expand...
Click to collapse
instead of this?
htc_batt_update->batt_current = htc_batt_info.rep.batt_current;
Click to expand...
Click to collapse
Seems like the batt_discharg_current is making my battery report less than the real value so I'd like to know why is the calculation like that?
I'm sorry for asking but I think you're the only developer on doubleshot who is approachable enough for me to ask to.
Riyal said:
Hi xmc! Not that I question the knowledge of the senior htc community developers here but this battery issue I am facing with ROMs like virtuous is already nagging me out.
Now compiled yours and shocked that it also has the battery bug.(The not going to 100% bug)
So I decided to really look up the battery driver carefully awhile ago and noticed something strange in it. I noticed this days ago and thought this was ok but thought I would stand up and ask today.
In
arch/arm/mach-msm/htc_battery_8x60.c
htc_batt_get_battery_info
Could you tell me why calculation of battery is like this?
instead of this?
Seems like the batt_discharg_current is making my battery report less than the real value so I'd like to know why is the calculation like that?
I'm sorry for asking but I think you're the only developer on doubleshot who is approachable enough for me to ask to.
Click to expand...
Click to collapse
I'll take a look once I get home. Lol and just to be clear, i'm not the only dev for the DS. We got Blue6IX, jeffakajeff, strapped365, tbalden, Riyal , kornyone, and nbetcher. (Dont kick my a$$ if I skipped your name )
Flashed this with a fresh install of your JB ROM. Phone is really laggy when waking from screen off for a few seconds but then its ok. I'll look more in to this but thats what I'm seeing so far.
Flashing over CM 9.1 now, will test it out and report back with results. Really hope this takes care of the battery drain issue in 9.1.
xmc wildchild22 said:
I'll take a look once I get home. Lol and just to be clear, i'm not the only dev for the DS. We got Blue6IX, jeffakajeff, strapped365, tbalden, Riyal , kornyone, and nbetcher. (Dont kick my a$$ if I skipped your name )
Click to expand...
Click to collapse
Lol! If I were a dev here I wouldn't have asked you this woot now I'm an ass kicker :highfive:
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
Just wondering in everybody else's experience which kernel they find to be the best as far as battery life and performance goes. I've only seen 3 kernels for 4.4.2 being leankernel dkp (I believe that's the name of it) and ktweaker. Also what settings you found to be the best for you (governors, undervolting settings, overclocking settings, Etc.) I do a lot of facebooking but that's about it. So I guess let the discussion begin? I'm running the latest update of cm11.
Kernel are fone depended. Wat works for some ppl might not work for othets. Try them all out let them run couple days then u can decide which is better for you.
BMS and KT747 also have 4.4 versions
Best is subjective. Here's my subjective approach, so caveat emptor, take what I say as personal belief and not a professional benchmark testing...
For AOSP-based roms, here's what my experience is:
Lean: Easiest and simplest of the kernels. Has limited governors, but the tweaked InteractiveX is pretty effective at doing what you need. It also has a crapton of S3 specific tweaks to improve battery life. You can overclock to 1.72 (I believe...) Downside? The min frequencies are 384k, which means other kernels can go into a deeper sleep. The TCP algorythms are limited too, so choose 'reno'.
DKP: I love this kernel, but several people report it doesn't work for them. This kernel has a ton of governors, with 'freelunch' and 'asswax' being the best. There are also a lot of TCP algorythms (choose 'yeah' for best performance). You can overclock to something ridiculous like 2.1... but I keep it at 1.62; there's also deep sleep frequencies down to 54k (yes... 54000), but I tend to stay at108k. The downside? Some people can't get this kernel to work on their device and it doesn't have some of the battery saving tweaks Lean does.
KT: This is kind of the 'go to' for many people, because it has a standalone app that flashes in the process and the dev is pretty active with the S3 version here. Many of the same features of the previous two, but different governors and nothing that's a device-specific tweak; the kernel is developed for multiple devices.
BMS: This, to me, is a similar kernel to KT and was my go-to for 4.3 roms. I haven't used it in a while, so I can't speak to if it offers more governors and customization.
My take and choice?
Lean and DKP offer the best battery and performance than the rest; they seem to give the same performance, so really you can use either and be happy. I find KT and BMS to be sluggish (even with tweaking) on 4.4 roms AND they don't seem to put the device into the sleep I want it to for battery savings.
BUT... If you're flashing Gummy, give the stock kernel a try! It's the only AOSP-based rom that doesn't use the Cyanogenmod kernel and you can actually get some good performance out of it. I flash DKP over Gummy, but I also flash Lean some times.
beepea206 said:
Best is subjective. Here's my subjective approach, so caveat emptor, take what I say as personal belief and not a professional benchmark testing...
For AOSP-based roms, here's what my experience is:
Lean: Easiest and simplest of the kernels. Has limited governors, but the tweaked InteractiveX is pretty effective at doing what you need. It also has a crapton of S3 specific tweaks to improve battery life. You can overclock to 1.72 (I believe...) Downside? The min frequencies are 384k, which means other kernels can go into a deeper sleep. The TCP algorythms are limited too, so choose 'reno'.
DKP: I love this kernel, but several people report it doesn't work for them. This kernel has a ton of governors, with 'freelunch' and 'asswax' being the best. There are also a lot of TCP algorythms (choose 'yeah' for best performance). You can overclock to something ridiculous like 2.1... but I keep it at 1.62; there's also deep sleep frequencies down to 54k (yes... 54000), but I tend to stay at108k. The downside? Some people can't get this kernel to work on their device and it doesn't have some of the battery saving tweaks Lean does.
KT: This is kind of the 'go to' for many people, because it has a standalone app that flashes in the process and the dev is pretty active with the S3 version here. Many of the same features of the previous two, but different governors and nothing that's a device-specific tweak; the kernel is developed for multiple devices.
BMS: This, to me, is a similar kernel to KT and was my go-to for 4.3 roms. I haven't used it in a while, so I can't speak to if it offers more governors and customization.
My take and choice?
Lean and DKP offer the best battery and performance than the rest; they seem to give the same performance, so really you can use either and be happy. I find KT and BMS to be sluggish (even with tweaking) on 4.4 roms AND they don't seem to put the device into the sleep I want it to for battery savings.
BUT... If you're flashing Gummy, give the stock kernel a try! It's the only AOSP-based rom that doesn't use the Cyanogenmod kernel and you can actually get some good performance out of it. I flash DKP over Gummy, but I also flash Lean some times.
Click to expand...
Click to collapse
By far the most in depth reply I've ever gotten on anything on any forums. I'll definitely give dkp a try with your suggestions, and I'll give that Rom a try as well when I get home on Sunday thank very much the reply
Backup, flash and find out.
Sent from my SCH-I535 using xda app-developers app
Travisholt92 said:
By far the most in depth reply I've ever gotten on anything on any forums. I'll definitely give dkp a try with your suggestions, and I'll give that Rom a try as well when I get home on Sunday thank very much the reply
Click to expand...
Click to collapse
Anytime, man. I'm ADD when it comes to roms and kernels, so I'm constantly changing them, but I really like the DKP/Gummy combo. FYI, if you're going to flash Gummy, get the 1/15 build... it's the one I'm on and is the most stable as of late.
I also recommend using the TricksterMOD app from the Play Store. It allows you to modify every feature the kernel will allow and can set on reboot.
Let me know if you want to know what my settings are in Trickster... I have it pretty dialed-in to solid performance and battery life.
Oh and as flyest said... nandroid, THEN flash. You should probably wipe dalvik and cache too. You don't have to, but I've had some bootloops before when I didn't.
beepea206 said:
Anytime, man. I'm ADD when it comes to roms and kernels, so I'm constantly changing them, but I really like the DKP/Gummy combo. FYI, if you're going to flash Gummy, get the 1/15 build... it's the one I'm on and is the most stable as of late.
I also recommend using the TricksterMOD app from the Play Store. It allows you to modify every feature the kernel will allow and can set on reboot.
Let me know if you want to know what my settings are in Trickster... I have it pretty dialed-in to solid performance and battery life.
Oh and as flyest said... nandroid, THEN flash. You should probably wipe dalvik and cache too. You don't have to, but I've had some bootloops before when I didn't.
Click to expand...
Click to collapse
I've only had issues like that when trying to flash anything my girlfriend's phone. However as far as trickster goes I can't afford the donation version at the moment.
What about I/o scheduler?
Travisholt92 said:
I've only had issues like that when trying to flash anything my girlfriend's phone. However as far as trickster goes I can't afford the donation version at the moment.
Click to expand...
Click to collapse
Don't even bother with the donation version... you can do everything you need with the free one.
As for I/O... you'll hear various claims that one is better than the other, but I stick with ROW. For the memory our device has 'Read Over Write' is the best scheduler you'll get with these kernels. FIOS is really the best, if you can find it, but ROW is what I stick with.
This may help clarify... or confuse you more lol http://timos.me/tm/wiki/ioscheduler
beepea206 said:
Don't even bother with the donation version... you can do everything you need with the free one.
As for I/O... you'll hear various claims that one is better than the other, but I stick with ROW. For the memory our device has 'Read Over Write' is the best scheduler you'll get with these kernels. FIOS is really the best, if you can find it, but ROW is what I stick with.
This may help clarify... or confuse you more lol http://timos.me/tm/wiki/ioscheduler
Click to expand...
Click to collapse
Alright what are those settings then lol
Travisholt92 said:
Alright what are those settings then lol
Click to expand...
Click to collapse
In my opinion, I found that leankernel is the best for battery saving/performance without tweaking...
buhohitr said:
In my opinion, I found that leankernel is the best for battery saving/performance without tweaking...
Click to expand...
Click to collapse
I like tweaking though
Travisholt92 said:
Alright what are those settings then lol
Click to expand...
Click to collapse
Here's only stuff I tweak.
SETTINGS:
TCP: 'yeah'
CPU FREQUENCY: min - 108000 / max - 1620000
GOVERNOR: freelunch
SPECIFIC:
Force Fast charge: YES.
Multicore Power Saving: 1
MPU Voltages: Press minus once for -25. Note that this may cause a 'wake lag' with the screen, so revert to 1150 @ the 1.512 frequency if you have issues.
I also tick the box for 'kernel settings' on reboot, so the app overrides other settings that are in effect @ boot.
beepea206 said:
Here's only stuff I tweak.
SETTINGS:
TCP: 'yeah'
CPU FREQUENCY: min - 108000 / max - 1620000
GOVERNOR: freelunch
SPECIFIC:
Force Fast charge: YES.
Multicore Power Saving: 1
MPU Voltages: Press minus once for -25. Note that this may cause a 'wake lag' with the screen, so revert to 1150 @ the 1.512 frequency if you have issues.
I also tick the box for 'kernel settings' on reboot, so the app overrides other settings that are in effect @ boot.
Click to expand...
Click to collapse
How do I change the tcp
In Trickster, TCP is at the very top of the 'Settings' window and should be a drop down menu.
beepea206 said:
In Trickster, TCP is at the very top of the 'Settings' window and should be a drop down menu.
Click to expand...
Click to collapse
Not there on the version I have
Travisholt92 said:
Not there on the version I have
Click to expand...
Click to collapse
In Trickster, under general, the first option on very top "TCP congestion control"...
buhohitr said:
In Trickster, under general, the first option on very top "TCP congestion control"...
Click to expand...
Click to collapse
Thank you very much
I've always used Lean Kernel for touchwiz and aosp roms. Very battery friendly and over clockable. I also like DKP for touchwiz. DKP has TricksterMod support and I believe Lean Kernel does as well. But if the rom has performance in the settings menu of the rom I use that instead.
Thanks to beepea206... I'm now getting 20+ hours of battery life off of one charge... I'm not changing a thing