I see a couple kernels with overclocking and other small unnecessary tweaks, but none that seem to address the fundamental flaw of aggressive background app killing. Is this just an area no one has previously had to look into, so the solution is not known or are people such as mdj unaware of the issue because they don't own the phone? Not critical of the developer's hard work...just curious why this seems to be overlooked?
el_smurfo said:
I see a couple kernels with overclocking and other small unnecessary tweaks, but none that seem to address the fundamental flaw of aggressive background app killing. Is this just an area no one has previously had to look into, so the solution is not known or are people such as mdj unaware of the issue because they don't own the phone? Not critical of the developer's hard work...just curious why this seems to be overlooked?
Click to expand...
Click to collapse
Well in my Fusion kernel I enabled init.d scripts support, which was never there before. So now you can use the V6 Supercharger and to fix OOM groupings for better multitasking.
klin1344 said:
Well in my Fusion kernel I enabled init.d scripts support, which was never there before. So now you can use the V6 Supercharger and to fix OOM groupings for better multitasking.
Click to expand...
Click to collapse
Is that any better than just adjusting the settings with minfree manager? I've tried that and it doesn't seem to work well.
el_smurfo said:
Is that any better than just adjusting the settings with minfree manager? I've tried that and it doesn't seem to work well.
Click to expand...
Click to collapse
Not sure what minfree manager is..but just give it a try and see how you think. Personally I've had good experiences with the V6.
klin1344 said:
Well in my Fusion kernel I enabled init.d scripts support, which was never there before. So now you can use the V6 Supercharger and to fix OOM groupings for better multitasking.
Click to expand...
Click to collapse
i see you're running the axiom s custom rom and fusion kernel.. i was wondering if your kernel could also work with axiom s s-less version? thanks
EDIT: i just read in your thread that it's compatible with all One S devices
Init.d scripts and a custom kernel greatly helps but the only true multitasking I've seen is in CM9
WCCobra said:
Init.d scripts and a custom kernel greatly helps but the only true multitasking I've seen is in CM9
Click to expand...
Click to collapse
This is probably just because Sense isn't using so much memory, so there's more to keep programs in residence.
forget the developer options, scripts, the oom values, etc. they don't help. the phone has plenty of memory for any applications. the issue isn't the memory available, but how the phone manages saved states and KERNEL is responsible for that. i hope somebody will make a working kernel for us one day.
Related
High speed ROM - Stock Gingerbread 2.16
Features:
--------
- Based on leaked Gingerbread ROM 2.16.0.0 with Kernel 2.6.35.10
- Rooted with su and superuser
- Unsecured boot.img
- Busybox included
- init.d support. Scripts moved to /data/init.d for easy addition/deletion/modification
- RAM & Speed Optimizations
- Clean & Fast, no visual changes
- Zipalign system applications for better RAM usage
- Automatically zipalign new applications on boot for better RAM usage
- Custom boot animation support (Replace bootanimation.zip in /data/local/)
- Nano text editor with sysro + sysrw support
- Bash shell support
- Highly tweaked kernel for performance
- Excellent battery life
- All apks updated to the latest version
- Low memory tweak (no need for task managers)
- Removed Stock completely
- Removed default maps and included Brut Maps Mod for international navigation.
Known Bugs:
------------
- You tell me
Download Link:
-------------
- http://www.multiupload.com/EJVXBO8J7B
Thanks to:
----------
- Mike1986 for guidance
- Dsixda for amazing kitchen
- Capychimp for guidance
and for all those who I forgot to mention
What about those kernel tweaks?
I thought its not entirely possible without kernel sources.
Whats the difference in speed compared to Lee's or Mike's release?
Try4Ce said:
What about those kernel tweaks?
I thought its not entirely possible without kernel sources.
Whats the difference in speed compared to Lee's or Mike's release?
Click to expand...
Click to collapse
You can tweak existing kernel parameters via sysctl which I have done.
So far I have find my rom more stable and smooth.
I will be requiring your feedback too in this regard.
Good to see another ROM to help the development
theintelligent said:
You can tweak existing kernel parameters via sysctl which I have done.
So far I have find my rom more stable and smooth.
I will be requiring your feedback too in this regard.
Click to expand...
Click to collapse
Didnt Mike and Lee do the same then?
Anyways, will give it a shot Always good to have more devs (and therefore different tweak setups) on board !
andywright1982 said:
Good to see another ROM to help the development
Click to expand...
Click to collapse
I agree with u on that ... the more devs there is the more fun for us "mortals"
Try4Ce said:
Didnt Mike and Lee do the same then?
Anyways, will give it a shot Always good to have more devs (and therefore different tweak setups) on board !
Click to expand...
Click to collapse
Yes, I'm using sysctl as well But maybe theintelligent used different parameters
theintelligent said:
You can tweak existing kernel parameters via sysctl which I have done.
So far I have find my rom more stable and smooth.
I will be requiring your feedback too in this regard.
Click to expand...
Click to collapse
Well there are few more things that I have done.
Firstly I have changed the IO scheduler to NOOP.
Secondly I have set different task manager settings when the screen is on and off. i.e when the screen is off the settings are aggressive, while the screen is on they are average. This gives your device a smoother feeling (The script is based on FlooHimself screen state scaling tweak).
Thirdly I have played with priorities of some processes (This script was used by NeoPhyTe in the Desire forum). It does gives your device some edge.
Anyways as soon as the uploading is complete, you can play with the ROM and report back.
theintelligent said:
Firstly I have changed the IO scheduler to NOOP.
Click to expand...
Click to collapse
well, i haven't tested it on this release but noop should give you slightly worse overall results than deadline. i didn't checked but i assume deadline is default on this kernel.
Exchange sync!
Is the exchange sync still a problem with this?
rijohann said:
Is the exchange sync still a problem with this?
Click to expand...
Click to collapse
Well I haven't found any problem. Can you please be specific what problems have you faced?
a user said:
well, i haven't tested it on this release but noop should give you slightly worse overall results than deadline. i didn't checked but i assume deadline is default on this kernel.
Click to expand...
Click to collapse
Tested noop my self, deadline gives better results
Task managers are useless anyway, the low memory killer default settings are spot on, further adjustments may cause instabilities.
Welcome to DHD dev theintelligent
Sent from me LeeDrOiD loaded Desire HD using the Android XDA Premium app
There you go experience talking..........Lee and Mike they both have mastery in DHD.
will sure give it try, after all this what i joined xda for to have fun with all different flavors and customizations.
Thanks for your efforts will report the findings asap.
LeeDroid said:
Tested noop my self, deadline gives better results
Task managers are useless anyway, the low memory killer default settings are spot on, further adjustments may cause instabilities.
Welcome to DHD dev theintelligent
Sent from me LeeDrOiD loaded Desire HD using the Android XDA Premium app
Click to expand...
Click to collapse
Well it's easy to change, but I will require more feedback like this.
Hotmail Exchange Sync
Hi,
can you tell me, if Hotmail Exchange Sync is working
on this ROM? With others Stock Sense 2.16 ROMs
were issues by Hotmail Inbox (Exchange Sync)
For example:
http://forum.xda-developers.com/showthread.php?p=11974324&highlight=hotmail#post11974324
thanks in advance.
jarilla.
theintelligent said:
Well it's easy to change, but I will require more feedback like this.
Click to expand...
Click to collapse
Got a tight community here matey, sure we will all work well together
Sent from me LeeDrOiD loaded Desire HD using the Android XDA Premium app
LeeDroid said:
Got a tight community here matey, sure we will all work well together
Sent from me LeeDrOiD loaded Desire HD using the Android XDA Premium app
Click to expand...
Click to collapse
This is great for the community.
theintelligent said:
You can tweak existing kernel parameters via sysctl which I have done.
So far I have find my rom more stable and smooth.
I will be requiring your feedback too in this regard.
Click to expand...
Click to collapse
Nice release, but who is campychimp? Hehe
Sent from my Desire HD using XDA Premium App
capychimp said:
Nice release, but who is campychimp? Hehe
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
Apoligies I was mentioning you. Updated in the main post.
As i can see,all cookers have given up for a few days updates for this ginger's leak.I think that this one leak is not so good as we thought ...I have tested all 2.3 sense roms here and i decided to come back to 2.2...A lot of issuεs which are important for each day use...
Hope u have found the answre's for the problems but i believe that we must wait for another leak...
Btw welcome and wish u to enjoy our company...
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.
I believe most of us here have been flashing various roms. Some roms give us more satisfaction than the rest.
However, it is difficult to have the best features of every rom. Is there anyone who knows where the core tweaks of the rom are located? Share your experiences and knowledge in this thread!
Anyone?
10chars
Some are in build.prop while some are scripts (system/etc/init.d) and are executed at boot. If you download a ROM from a recognized and well reputed dev, its best not to pile tweaks on tweaks. Not only will they conflict but the tweaks of that specific ROM were put there for optimum performance of that specific ROM. Some tweaks are global anyway. If you want stuff like setting GPU I/O fraction to 50 you could use the script from hypersensation (init.d) but then again those scripts are easy enough to write. What kind of tweaks are you referring to??
Thanks for the reply. I am looking at more to the gaming tweaks. Like 3d performance etc.
Pjay12 said:
Some are in build.prop while some are scripts (system/etc/init.d) and are executed at boot. If you download a ROM from a recognized and well reputed dev, its best not to pile tweaks on tweaks. Not only will they conflict but the tweaks of that specific ROM were put there for optimum performance of that specific ROM. Some tweaks are global anyway. If you want stuff like setting GPU I/O fraction to 50 you could use the script from hypersensation (init.d) but then again those scripts are easy enough to write. What kind of tweaks are you referring to??
Click to expand...
Click to collapse
remus82 said:
Thanks for the reply. I am looking at more to the gaming tweaks. Like 3d performance etc.
Click to expand...
Click to collapse
Gaming performance relies strongly on the kernel. Faux is probably the best in this field but of course with heavy use drains your battery. The best roms I've encountered for gaming are reverted AOSP and lee Droid sense 3.0 version and lee kernel. I doubt there are many tweaks in the ROM itself for gaming purposes. A ROM running bricked would not play as smooth as faux but would have better battery. The roms I mentioned are just what I use btw
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.
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