Related
This is an undervolt test version of my new StupidFast Kernel v1.2.3. This is a TEST release (NO VOODOO). This kernel aims to be fast, compatible, stable, and have good battery life. It is based on my StupidFast v1.0.36.
Code:
Changes since 1.2.2:
Fix for the 0.5-1.0 second pause/lag opening apps/drawer
Scheduling Tweaks
I/O Tweaks
Changes since 1.1.23:
Stock 1ghz @ 1225mV
Changes since 1.1.14:
Tweaked minfree settings
tweaked io scheduler
more compiler flags for cortex/hummingbird cpu
tweaked wifi scan interval to help with battery life
Changes since 1.0.36:
removed custom boot animation to trim size.
using kernel jhash3 instead of jhash2.
optimized compiler flags for the hummingbird cpu.
changed some kernel scheduling timings.
BLN disabled by default (configurable with [url=http://forum.xda-developers.com/showthread.php?t=823922]this app[/url])
You will see that the custom boot animation was removed. It's okay. If you already have v1.0.36, 1.1.4 or 1.1.23 installed on your phone, the animation will stay. If you're new to my kernels with v1.2.3, your old boot animation will be there.
I'm not seeing any lag on the phone. Gallery opens pretty much instantly. Settings->Applications->Manage opens pretty much instantly. Launcher Pro+ pretty much instantly appears when the phone starts up.
Testers could NOT find any audio problems with this kernel using the media player in JT's Clean ROM. I've tested Youtube and Pandora and have had no audio issues. Also, we couldn't find any issues with USB mount/unmount, settings changes, etc.
As always, if you find a bug or what you think might be a bug, let me know. This is NOT the final stable release of the 1.2 kernel. Stay tuned to #samsung-fascinate on FreeNode or @geeknik on Twitter!
Download:
http://dl.dropbox.com/u/6088006/stupidfast-test-v1.2.3.zip
saps from #samsung-fascinate said that v1.0.36 was "far and away the fastest real world kernels I've ever seen, period"
If you like my kernel, show me some love. Donate today!
Thanks to saps, jt1134 my beta testers and the kind folks that donated cash to the cause! Keep fighting the good fight!
sweet. dowlloading now.
Downloading also.
I like your kernels, but I just noticed I am getting a super weird output in ADB when I try using that. I also have superdark ROM so it could be either one.
Ok, I just rebooted and checked again and all is running fine with 1.2.2 in recovery, but not in running android system, must mean its the rom.
Downloading now.. went with full full wipe with jts clean, and still getting popping, on asop player, double twist, pandora
Besides the battery life which is supposed to be increased, is there any other benefit to UV ???? Longer processor life, runs cooler, etc.
What are the drawbacks, if any ???? Does performance take a big hit, etc.
I'm asking more in general terms. Obviously I will observe first hand with this kernel, which I'm downloading now.
mexiken said:
Besides the battery life which is supposed to be increased I assume, is there any other benefit to UV ???? Longer processor life, runs cooler, etc.
What are the drawbacks, if any ???? Does performance take a big hit, etc.
I'm asking more in general terms. Obviously I will observe first hand with this kernel, which I'm downloading now.
Click to expand...
Click to collapse
In theory, as I know computer not cell phone, UV will allow it to run cooler, which does mean last longer (but is that really a problem?) and use less juice while still being as fast as before. If it runs stable you will not see a performance hit and it will better with the battery. It will just freeze your phone if its too low and requires more juice, really no harm can be done, overvolting is more dangerous as that burns up cpus, but you overvolt to make the higher frequency stable. Simple overclocking principals apply, you want the lowest voltage for your cpu frequency.
spyd3r05 said:
Downloading now.. went with full full wipe with jts clean, and still getting popping, on asop player, double twist, pandora
Click to expand...
Click to collapse
are you upping the CPU to 200mhz to run those? I am doing that and its just fine, although I never had a popping problem at 100mhz either. I just set the min to 200 because that cleans up a little bit of the lag too.
Possibly related, every once and a while my phone will just decide to press a soft key on its own, what is that? (that causes a slight skip in the music when I am playing it)
destroyerbmx said:
are you upping the CPU to 200mhz to run those? I am doing that and its just fine, although I never had a popping problem at 100mhz either. I just set the min to 200 because that cleans up a little bit of the lag too.
Possibly related, every once and a while my phone will just decide to press a soft key on its own, what is that? (that causes a slight skip in the music when I am playing it)
Click to expand...
Click to collapse
see if listening to it while hooked to power recreates the problem... i noticed for me atleast its only when plugged in...
I have it up to USB and its not skipping or popping right now, I am also using mixzing
v1.2.2 is the least fastest of all the geeknik kernels for me. There is 1 almost 2 second pause loading and exiting apps unless it was already in memory.
Still faster then everyone elses kernel. And so far battery life looks to be way better on this one but I haven't had it long enough to say for sure.
Nothing has changed on my audio popping issues so I am still using SetCPU at 200min still. I am short 6 hours of battery life like this by my best guestimate... which isn't a big concern for me- just reporting for those who need to make it thru a day without a charger nearby.
Never had any FC's with USB.
Touchwiz/JT's Super Clean ROM
And a thank you to geeknik for all your efforts! love how your pumping these out!
Kernal runs great! No unwanted sounds from the stock music player in jt's rom. USB works just fine. Thanks for your hard work!
are you using setcpu? if so that helped me fix it bumping min to 200... any one else having the problem might try that...
Interestingly enough, this kernel does seem a touch slower than the 1.2.23 regular voltage kernel. Hangs just the slightest bit when firing up and exiting dolphin browser and xda app. Still, appears to be MUCH better with battery life, as the previous geeknik kernels were ravaging my battery.
Definite progress but not quite perfect imho. Still thanks for all your work geeknik, you're killing it with these.
Also fyi, running custom blackhole, with sns and lp
Sent from my StupidFast Fascinate using XDA App
This kernel is running fairly smooth, like the other 2. I can deal with the extra 0.5 second delay when first opening an app, as long as BLN is optional and battery life is extended. Thank you very much for taking the time to come up with these kernels for us. Other kernel providers tend to make their products less accessible for us XDA users, but you take the stress out of the search. Thank you again.
Thank you very much for taking the time to come up with these kernels for us. Other kernel providers tend to make their products less accessible for us XDA users said:
This is because these development forums are filled with junk threads, nobody taking the time to read a Lil bit. Its getting worse and devs leave because of it. Not the devs fault at all. Just a point to make: )
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Can someone explain how to get bln. I saw a post about it but can't find it or I'm over looking it like an idiot
Sent from my SCH-I500 using XDA App
zachsx said:
Can someone explain how to get bln. I saw a post about it but can't find it or I'm over looking it like an idiot
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Re-read the first post of this thread, there's a link to how to enable/disable bln
The uv kernel is a winner of course. I test these kernels for geeknik before he throws them up for the masses. Not just running quadrant [although I do that too] but going thru the real phone stuff itself. The manage applications load, replacing new dock shortcuts, gallery, apps and stuff everything we actually want to see improve with.
I for one never had battery issues with previous stupidfast kernels but I know some did, same this music crackling. It seems to me most of you that do are either running blackhold or deodexed rom though and quite humbly I'd look their for your culprit moreso than the kernel. If there was a music skipping issue from the kernel itself it would manifest itself across the boards but it doesnt.
Anyway, battery life is going to be stellar trust me, under light-moderate use Im only using like 2% per hour here swyping 8-10 texts per hour here, very good indeed
Hey Saps- I see ya on all the forums and your contributions have really helped me out...
That being said I keep seeing an overlook of real world usage in these testings. Can you guys test beyond stock apps? I mean checking stock should be the first thing you do obviously but how many people use the stock music player or the stock browser, etc? I am betting most the people that have the knowledge enough to test these kernels and ROMs aren't using stock functionality and apps.
Please test this kernel with the PowerAMP or Music PlayerPro music apps before writing off the issue.
Use Dolphin to check the internet, etc. Use K-9 to check email, etc.. ya know- use the popular apps during testing also if you could?
Audio cracking, FC's with the USB settings, and I even heard mention of live wallpapers having issues. These reports coming from 3 reported different ROMs.
How are you missing this?
I myself have had great success with battery life on the Stupid Fast kernels. Better then stock kernel for sure. But I've been having to run my battery faster by using my workaround to avoid the music crackling.
JT's Super Clean ROM using TouchWiz
Just suggestions so we can all get on the same page and enjoy these badass mods.
P.S. What ROM are you using during testing of this kernel? I'll gladly switch to fix the issues
I know, tons of stuff released, some may be similar, but I've had people waiting for me to release these for some reason, so I am. Not sure what I do differently that makes people choose what I release over someone else, but here they are.
What I've done is started with the source jt1134 has provided as a base, and went from there. I haven't had time to change much else yet, but in due time, I'm hoping to have a lot of changes and updates. If you feel like supporting the development, consider signing up for Dropbox and help give me more space to store kernels.
0808
Merge pull request from Times_infinity to fix missed call problem
0804
New Kernel/Ramdisk based on ED05 sources
Updated root script to root phone on boot
Updated recovery to latest CWM
Fixed busybox issue (I think)
Voodoo Sound V10
Only one undervolt level - same as previous "100" kernel
0531
navenedrob's ext4 formatting options put into Voodoo conversion script - disable lagfix, then re-enable to take advantage of it
V(R) IO Scheduler
Fixed backup/restore/wipe errors for android_secure (I think) - thanks squash
0530
Fix mount USB Storage in recovery (Thanks times_infinity)
0529
Fix 0523
Root ROM on boot (if not already rooted)
Move files to initramfs so changes can travel between ROM Flashes
No more AOSP kernels, waiting for CM7
0523
Voodoo Sound V9
Use Linaro Toolchain to compile
Switch to bmlwrite to flash
0426
Fixed auto-brightness
0425
Voodoo Sound V8 (thanks supercurio)
Updates to initramfs to try and prevent bootloop when wiping data/cache
Update to CWM 3.x and make CWM 3.x compatible zips
0415
Simple IO Scheduler
Moved SD Card speed tweak to init.d script so users can change the value
-> Default value is 4096
Updated source to ED01 from Samsung
Built with 2010q1 toolchain, updated from 2009q3
0408
Updated initramfs from jt1134
Kernel config changes from jt1134
Voodoo sound patches from jt1134/supercurio
"Fixed" Smartass, still doesn't work properly though, set conservative back to the default
Increased voltage on 100 kernel at 1000MHz
CFS Tweaks to try and help performance some
TCP settings to help make 3G more consistent
Built AOSP kernels
0330
Smartass CPU Governor added and set as default <- not working yet
VFAT patch
Voodoo Sound mic/recording fixed and added back - thanks jt1134/supercurio
0329
Upstream EXT4 patches
Changed UV levels for greater compatibility
init.d support
SirGatez patch to force audio to headphones when they are plugged in (off by default)
-> run "headphones" from a shell prompt to enable
-> run "default" to restore normal functionality
0328
jt1134's source is the base, includes BLN, Voodoo Color, Voodoo Sound V7, Voodoo lagfix (if applicable), and anything else jt had in is source when i synced it.
Stock voltage, and undervolted kernels available
Updated CPU Scaling - keeps the processor running as slow as possible without overworking it
Updated compile flags - from Eclair, may not do anything noticeable
SirGatez's battery hack to allow for non-oem batteries
To Do:
Get 600MHz working
NOTES:
If you are experiencing problems, I need detailed info to be able to fix it or help you out. Failure to provide detailed info will mean I'm just going to ignore your problem as user error. Details would be something such as which kernel you are flashing (filename) and steps to reproduce the issue. Also, if you used any other kernels that had the same problem or didn't have the problem.
Legend
voodoo/novoodoo - voodoo has the lagfix, novoodoo doesn't (I hope this was obvious)
sv/50/100 - Undervolt level. sv = stock, 50 = 50mv off 400-1000mhz/75mv off 100-200mhz, 100mv off 400-1000mhz/125mv off 100-200mhz
Sweet thanks! I always had great luck with your kernels on Eclair. Flashing the 100 uv now.
Sent from my SCH-I500 using XDA App
Woohoo first in. Trying the 50 now.
*dammit, not first*
good day.
going to try the 100uv
I've tried probably 3-4 kernels in the past couple of days.. someone needs to make a thread up and discuss the differences.
am I correct in saying 100uv is - so far - the lowest UV kernel around?
thanks!
Woohoo 3rd. Thanks nutz
Dang. 4th.
Sent from my SCH-I500 using XDA App
Sweet
I was waiting for the imnuts kernals. Just flashed the 50, I can see the difference already! Just kidding but so far so good. Thanks!
Was I supposed to say fifth? I don't know the etiquette yet
khanable said:
am I correct in saying 100uv is - so far - the lowest UV kernel around?
Click to expand...
Click to collapse
You probably won't find a lower UV than my 100. It gets kinda useless after 100mv undervolt anyway.
ryanf said:
Woohoo 3rd. Thanks nutz
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
More like 4th
Anyone else had any luck? I can't get it to boot. I am now on my third battery pull.
Man I'm psyched to see this!!! Thank you imnuts!
Nice can't wait for aosp.
Sent from my SCH-I500 using XDA Premium App
Thanks for your work. Flashing now!
xceebeex said:
Anyone else had any luck? I can't get it to boot. I am now on my third battery pull.
Click to expand...
Click to collapse
Voodoo or novoodoo? I'm using the 100 voodoo right now and it's fine. If you're on novoodoo, you need to wait, as I mentioned in IRC shortly after posting the list as something is messed up in it that will likely cause the problem you're seeing.
imnuts said:
Voodoo or novoodoo? I'm using the 100 voodoo right now and it's fine. If you're on novoodoo, you need to wait, as I mentioned in IRC shortly after posting the list as something is messed up in it that will likely cause the problem you're seeing.
Click to expand...
Click to collapse
I am on voodoo and I am trying to use the 100 as well. It looks like it just booted, after the third battery pull. We will see how it goes.
Thanks again!
EDIT: It froze at the unlock screen, so I am trying a 4th battery pull.
https://dl-web.dropbox.com/get/Public/FamilyGuy-PeanutButterJellyTime.mp3?touch=6FiWCQ==&w=2e02a09b
Sent from my SCH-I500 using XDA App
This isn't oc'd, right?
Sent from my Froyo'd Fascinate via Tapatalk
xceebeex said:
I am on voodoo and I am trying to use the 100 as well. It looks like it just booted, after the third battery pull. We will see how it goes.
Thanks again!
EDIT: It froze at the unlock screen, so I am trying a 4th battery pull.
Click to expand...
Click to collapse
The 100 may be to much of an undervolt for your phone then, try the 50 or sv to see if you can reproduce the issue.
cpark_12 said:
This isn't oc'd, right?
Sent from my Froyo'd Fascinate via Tapatalk
Click to expand...
Click to collapse
Stock clock speeds. IMO, overclocking is useless on our phones for anything besides given you a bigger quadrant score, and it does little for actual usage.
It is definitely pretty screwed up for me. It keeps vibrating and there was no signal and nothing was working, but I was able to reboot to recovery so I am going to try flashing again and see what happens.
For those about to flash if you're using set cpu uncheck enable on boot before flashing, i've had the problem of freezing on boot before and this seemed to have solved the problem.
Dang it, I'm never gonna calibrate battery the way I'm flashing kernels the past few days...flashing now!
Sent from my SCH-I500 using XDA Premium App
I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Just try clearing app data rebooting and reinstalling the app. That problem has happened to me every once in a blue moon and that fixed it for me.
Sent from my SGH-I777 using Tapatalk 2
Thanks, I'll try reinstalling the kernel.
Which app are you referring to? because I had this problem no matter which app I used to change the governor (Extweaks, voltage control, setcpu).
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
bacon_n_icecream said:
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
Click to expand...
Click to collapse
It's the lulzkernel for some-reason :|
I have problem goto smartassv2 it's ok just steps heavy
Thanks for your suggestion. I just moved over to ondemand and its been ok for me. Too early to make any judgments but I'll try smartassv2 next.
Not that I'm glad to that you're having problems, but I'm glad I'm not the only one with this issue. Thanks for the response
Winklie said:
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Click to expand...
Click to collapse
DONT use kernel cleaning scripts. They cause more problems than good.
Sent from my AT&T I777 running AOKP build 3X
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
bacon_n_icecream said:
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
Click to expand...
Click to collapse
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
thanks, I generally do that any way along with the script cleaner
K Rich said:
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
CPU related as well...
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
kbulut said:
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
Click to expand...
Click to collapse
Lots of questions there. Phone overclocking is the same and at the same time different than PC overclocking. I too bought SetCPU and due to bugs and problems have completely abandoned it. Honestly with the exception of running an epeen benchmark there is little incentive to overclock. Find a newer Kernel (I use NEAK which has no overclocking ability) and install it, performance is stellar. You really have to ask yourself, is my phone slow enough that I need more CPU power to make it faster?
To see what time your CPU is spending at a given clock speed, download CPUSpyhttps://play.google.com/store/apps/details?id=com.bvalosek.cpuspy&feature=nav_result#?t=W251bGwsMSwyLDNd, you will be surprised to see your phone spend very little time at it's max clockspeed.
Due to the immaturity of the fab process for our CPU's (well SoC), what is a stable overclock for one person might not even load for another. These CPU's are not like an Intel Sandy Bridge, with 1Ghz of free overclocking, nearly guaranteed. You can certainly play with voltages to try and attain a higher overclock, but at the expense of CPU lifetime, as well as battery.
Additionally, it takes a new Kernel 3 or so full charge, discharge cycles on a phone to really 'settle in' and 'learn' a particular phones battery, while yours got hot, which to me indicates an endless loop of some kind running in the background.
My advice would be as follows: Choose a ROM you like, feel free to play with different Kernels, again, I use NEAK, which does not work for some folks, or crashes or whatever. Give it several days to 'settle in' and if your still not happy with performance or have stability problems, try a different governor/scheduler. You really need to establish a good, solid baseline of your phones performance and make small changes and give them long enough to establish any changes to your phones overall stability. Basically running cowboy through your phone and making changes will have a negative overall outcome. Make small, documented changes, test and see what overall effect this has to your phone's stability and battery life, and make another change.
bacon_n_icecream said:
I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Click to expand...
Click to collapse
Lulz has known problem in 3.2b2-1
Gokhan has fixed it in 3.2b2 - 2
Wait for ktoonsez to update it for us
Sent from my SGH-I777 using Tapatalk 2 Beta-6
Thank you so much for the information. Could I simply uninstall the setcpu and go back to normal? Simply reflash the rom and/or kernel? I really like shostock2 with the cherry picker kernel for now. I want to give them a week of try to make my mind. Before the setcpu I think.I was better off
Thanks for the help by the way. I appreciate it.
Thanks for the update about the new siyah kernel. Glad it wasn't just me with the issue. I was going to post this question in the siyah thread but am new to the site so didn't have permission so thanks for finding me all the way over here
Phalanx7621 said:
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I'm just going off what I've seen in the Siyah/NEAK threads. Most of the lock-ups/random reboots I've heard people having had used the cleaning script. Either that or its just coincidence.
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
bacon_n_icecream said:
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
Click to expand...
Click to collapse
Hmm, well I've just manually wiped cache and dalvik and have never had problems between roms/kernels.
Sent from my SGH-I777 using Tapatalk 2
I installed CM10.1 nightly on my fascinate a few days back and it has been working pretty good. I had to install a memory manager to kill tasks more often for me. Then I remembered an old app I purchased a couple years back. set cpu, I went ahead and installed that and overclocked 1200/400 and it made the phone come to life. things seem to run really smooth. Not an advertisement as much of helpful hint in case you were not aware.
Thanks for all your guys help this week setting me strait on getting my phone working.
Xceptiona1noob said:
I installed CM10.1 nightly on my fascinate a few days back and it has been working pretty good. I had to install a memory manager to kill tasks more often for me. Then I remembered an old app I purchased a couple years back. set cpu, I went ahead and installed that and overclocked 1200/400 and it made the phone come to life. things seem to run really smooth. Not an advertisement as much of helpful hint in case you were not aware.
Thanks for all your guys help this week setting me strait on getting my phone working.
Click to expand...
Click to collapse
Your not suppose to use a task killer it hurts the phone very badly if you enable KSM in performance menu and zram you will notice it works the best. And set CPU has problems with jb like it could boot loop your device its better to use the built in performance menu
Sent from my SCH-I500 using Tapatalk 2
Yes, the stock Performance menu options are your better choice for over-clocking and memory management.
If you don't see the Performance menu under system settings, you need to enable developer mode by selecting About Phone, then tapping on the android version info about a dozen times.
Regarding zram, I'll need to give it another try... Definitely go with ksm enabled.
Sent from my SCH-I500 using xda premium
The reason task-killers don't work well is because android changed the way it handles multi-tasking so that once you kill a process, it will bring it back anyway, so that if you keep trying to kill things you will actually waste more battery because it will constantly be coming back. Android is actually very good at managing memory and doesn't need your help to do it.
I only use KSM myself because I was getting lag after a while using zram, but maybe it was something I was doing wrong with the settings. My other settings as of now are Interactive governor (min 200 - max 1200) and noop scheduler.
Crawshayi said:
The reason task-killers don't work well is because android changed the way it handles multi-tasking so that once you kill a process, it will bring it back anyway, so that if you keep trying to kill things you will actually waste more battery because it will constantly be coming back. Android is actually very good at managing memory and doesn't need your help to do it.
I only use KSM myself because I was getting lag after a while using zram, but maybe it was something I was doing wrong with the settings. My other settings as of now are Interactive governor (min 200 - max 1200) and noop scheduler.
Click to expand...
Click to collapse
Noop is one of the worse schedulers not asking you to change but row an so is the best
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
Noop is one of the worse schedulers not asking you to change but row an so is the best
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
I usually use SIO but since I'm on the default kernel it's not an option. I tried ROW for a few days but it was making my music skip sometimes for some reason (especially while mutli-tasking while playing music), and noop doesn't seem to give me as many problems like that... so I'm not really sure. CFQ didn't seem to be that great either, so I'm hoping SIO will be added soon
Crawshayi said:
I usually use SIO but since I'm on the default kernel it's not an option. I tried ROW for a few days but it was making my music skip sometimes for some reason (especially while mutli-tasking while playing music), and noop doesn't seem to give me as many problems like that... so I'm not really sure. CFQ didn't seem to be that great either, so I'm hoping SIO will be added soon
Click to expand...
Click to collapse
Sio has always been great to me even the benchmarks give me crazy scores when using sio
Sent from my SCH-I500 using Tapatalk 2
zRam seems a zero-sum gain - or worse - on this phone
Crawshayi said:
The reason task-killers don't work well is because android changed the way it handles multi-tasking so that once you kill a process, it will bring it back anyway, so that if you keep trying to kill things you will actually waste more battery because it will constantly be coming back. Android is actually very good at managing memory and doesn't need your help to do it.
I only use KSM myself because I was getting lag after a while using zram, but maybe it was something I was doing wrong with the settings. My other settings as of now are Interactive governor (min 200 - max 1200) and noop scheduler.
Click to expand...
Click to collapse
I just gave zRam a spin and experienced noticeable lag with what I do as a result. I have "Allow purging of assets" and KSM checked.
For the I/O Scheduler, ROW seems better than the CFQ I had been running. Running the interactive CPU governor. 1200/100 CPU speeds.
Seems good.
bmeek said:
I just gave zRam a spin and experienced noticeable lag with what I do as a result. I have "Allow purging of assets" and KSM checked.
For the I/O Scheduler, ROW seems better than the CFQ I had been running. Running the interactive CPU governor. 1200/100 CPU speeds.
Seems good.
Click to expand...
Click to collapse
Ditto, except with purging checked I'm pretty sure I was getting lag from that too after a while, so on mine I only left KSM on. ROW also does seem the best, however lately it seems no matter what scheduler I choose I get music that skips every couple of minutes or so, but I think that's a rom issue and not so much a scheduler issue. I've always used 200 minimum so that my phone is snappier when waking up, but that's just a personal preference.
Crawshayi said:
Ditto, except with purging checked I'm pretty sure I was getting lag from that too after a while, so on mine I only left KSM on. ROW also does seem the best, however lately it seems no matter what scheduler I choose I get music that skips every couple of minutes or so, but I think that's a rom issue and not so much a scheduler issue. I've always used 200 minimum so that my phone is snappier when waking up, but that's just a personal preference.
Click to expand...
Click to collapse
I don't get music skipping hellybelly
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
I don't get music skipping hellybelly
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
I definitely do want to try hellybelly, but right now I just don't have the patience to set up all my apps again so maybe on my day off I'll git it a whirl. How's battery life on it?
Crawshayi said:
I definitely do want to try hellybelly, but right now I just don't have the patience to set up all my apps again so maybe on my day off I'll git it a whirl. How's battery life on it?
Click to expand...
Click to collapse
You might try a dirty flash to Helly after taking a backup (just wipe cache & Dalvik). It's based on cm10.1 so you should be all right...
Sent from my SCH-I500 using xda premium
Crawshayi said:
I definitely do want to try hellybelly, but right now I just don't have the patience to set up all my apps again so maybe on my day off I'll git it a whirl. How's battery life on it?
Click to expand...
Click to collapse
Battery life is crazy good and I wouldn't recomeend dirty because it includes a whole different kernel and such and a lot of little things changed from cm10.1
Sent from my SCH-I500 using Tapatalk 2
---------- Post added at 06:40 AM ---------- Previous post was at 06:39 AM ----------
bmeek said:
You might try a dirty flash to Helly after taking a backup (just wipe cache & Dalvik). It's based on cm10.1 so you should be all right...
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Its nothing like cm10.1 lol it has a whole different kernel and a while lot of other stuff lol
Sent from my SCH-I500 using Tapatalk 2
Thanks man, I've been looking into changing settings recently, might try it out.
dirty-flash between CM10 and HellyBean = no problem (apparently)
bbrad said:
Battery life is crazy good and I wouldn't recomeend dirty because it includes a whole different kernel and such and a lot of little things changed from cm10.1
Sent from my SCH-I500 using Tapatalk 2
---------- Post added at 06:40 AM ---------- Previous post was at 06:39 AM ----------
Its nothing like cm10.1 lol it has a whole different kernel and a while lot of other stuff lol
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
I simply said that Helly is based upon CM10.1, and it is. Anyway, I just did a dirty flash (cache+dalvik wipe only) from the 02/22 build of CM10.1 to the latest HellyBean and it works fine. Actually, with the 1400mHz overclocking it was working really smoothly - although the rate of battery drain was apparent...
My hesitation in sticking with hellybean is based on my lack of understanding on how/if all of JT1134's ongoing fascinate-specific kernel/framework efforts, that are going into the CM10 nightlies, are being merged into the hellybean kernel... I guess I should go over to DT's thread and ask . Perhaps he's got all that happening whenever he merges the CM10 source updates...
bmeek said:
I simply said that Helly is based upon CM10.1, and it is. Anyway, I just did a dirty flash (cache+dalvik wipe only) from the 02/22 build of CM10.1 to the latest HellyBean and it works fine. Actually, with the 1400mHz overclocking it was working really smoothly - although the rate of battery drain was apparent...
My hesitation in sticking with hellybean is based on my lack of understanding on how/if all of JT1134's ongoing fascinate-specific kernel/framework efforts, that are going into the CM10 nightlies, are being merged into the hellybean kernel... I guess I should go over to DT's thread and ask . Perhaps he's got all that happening whenever he merges the CM10 source updates...
Click to expand...
Click to collapse
All the merges go fine the merges to the cm kernel merges into the devil kernel
Sent from my SCH-I500 using Tapatalk 2
Well I decided to try Helly Bean and so far so good, on SmartassV2 and ROW - no skipping music and everything is really snappy. Battery life seems noticeably worse than pure CM 10.1 but nothing that still can't get me through the day. I wish the Devil settings were baked into the rom settings like they used to be, it's annoying to have to use 3rd party apps to control it. I really like the standalone AOKP performance settings apk but settings don't stick after reboot
Crawshayi said:
Well I decided to try Helly Bean and so far so good, on SmartassV2 and ROW - no skipping music and everything is really snappy. Battery life seems noticeably worse than pure CM 10.1 but nothing that still can't get me through the day. I wish the Devil settings were baked into the rom settings like they used to be, it's annoying to have to use 3rd party apps to control it. I really like the standalone AOKP performance settings apk but settings don't stick after reboot
Click to expand...
Click to collapse
They are baked in just tap build number 10 times it only has the stuff available in performance right now the only other feature that isn't in performance is touch wake
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
They are baked in just tap build number 10 times it only has the stuff available in performance right now the only other feature that isn't in performance is touch wake
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Oh thanks man, totally missed that one. Also, it's missing all of the RAM settings like XL and such but I never used that anyway so this will work just fine so thanks again
Crawshayi said:
Oh thanks man, totally missed that one. Also, it's missing all of the RAM settings like XL and such but I never used that anyway so this will work just fine so thanks again
Click to expand...
Click to collapse
Well I done even thinks that's available yet dt is still in the procces of adding features like that
Sent from my SCH-I500 using Tapatalk 2
Drop this file in your /system/etc folder, replacing the stock one. Cleaned up, and modified to work with a stock kernel or lean kernel.
Please open up the file, and read some of the notes I added, so you know what this does and how to change it if you so desire. It is very basic and straightforward.
Also, please remember one thing, if you want to go to the stock kernel, simply change any words in the scripts from "interactiveX" to "interactive".
Recommended lean kernel 3.16 with these scripts.
Designed to work with ALL Galaxy Note 3's running touch wiz 4.4.2 ROMs and running lean kernel or stock kernel. Other kernels are not guaranteed due to the voltages applied.
This will make a huge difference in performance and battery. Been using this (developed by me) for a long time now.
Summary:
*I/O optimization
*tuned interactive parameters
*fixed sysfs permissions for cpu's (root now has full control of sysfs tuneables)
*GPU sysfs identified for user to customize
*screen off frequency set to 1.2 GHz (can be changed by user)
*custom voltage set for bin 2 device. (Read instructions within file to adjust for others bins accordingly)
*custom mpdecision tuning and other relevant instruction regarding mpdecision binary
*general CPU tweaks for better performance, responsiveness and battery life (yes all 3 can be achieved, and are)
Again, open the file with a file explorer (or notepad+ in windows). Read it, understand it, adjust what you want, or leave it be. These settings are very much dialed in for the interactiveX governor of LK. It won't get much better. I'd say take a look at the voltage portion and mpdecision for now (found at the end).
Once more, drop file into the /system/etc directory... Replace the existing one, and reboot.
FILE DOWNLOAD
Updated today... many useful changes, and fixes (set up for stock kernel for now)
https://www.dropbox.com/s/tjlygujptls3lks/init.qcom.post_boot.sh?dl=0
Thanks man!
Thanks man best Antutu score.
Best. Disclaimer. Ever.
Sent from my SM-G900V using XDA Free mobile app
Hahahahahahah I love the disclaimer.
Thanks! Helps a lot
Sent from my SM-N900V using xda app-developers app
I've noticed my phone lags alot less now and some things I had going wrong (if I turned torch on more than 15 seconds it would freeze and Multiwindow didn't like to work) work now. I don't know why or how or even if it is supposed to do anything to those things and it's just a very odd coincidence. But I've noticed my battery life is horrible now. Running it with Alliance 2 and with my ZeroLemon I used to get 10-11 hours on screen time and that's down about half to 5 or 6 hours. I know you said you could tweak stuff but I have no idea about that. Any recommendations for me to change in the script? Thanks again if for anything my phone running smoothly again!
amebiasis said:
I've noticed my phone lags alot less now and some things I had going wrong (if I turned torch on more than 15 seconds it would freeze and Multiwindow didn't like to work) work now. I don't know why or how or even if it is supposed to do anything to those things and it's just a very odd coincidence. But I've noticed my battery life is horrible now. Running it with Alliance 2 and with my ZeroLemon I used to get 10-11 hours on screen time and that's down about half to 5 or 6 hours. I know you said you could tweak stuff but I have no idea about that. Any recommendations for me to change in the script? Thanks again if for anything my phone running smoothly again!
Click to expand...
Click to collapse
If you aren't using lean kernel, you need to change the governor in the script to NOT say "InteractiveX"... Stock, or all other kernels need "interactive"... Otherwise the governor will be stuck on performance.
That is likely your issue.
Most people don't know that the note 3 boots with the performance governor enabled. The /system/etc/init.qcom.post_boot.sh file executes after the boot complete flag and changes the governors, among other things.
Edit the file, change the governor call out to "interactive".
Should fix it.
Thank you sir!
Running amazing after changing things over to "interactive" in the script with the stock kernel. Much more fluid speed on Eclipse with the battery life a bit better. Thanks for sharing! :highfive:
Wow night and day difference by changing that script to just interactive. Been flying all day playing games and watching movies total SOT (with my ZeroLemon) is just over 5 and a half hours screen brightness at about 65% using Lux and Bluetooth and I'm only at 67% awesome job man and thank you for steering me in the right direction!
Is the 300 slot removed from this script?
Also to my understanding this is mainly for the dev edition and lean kernel correct. But most of us r on the retail. Is there anything else to change besides the interactive for better performance?
Sent from my SM-N900V using xda app-developers app
stalls said:
Is the 300 slot removed from this script?
Also to my understanding this is mainly for the dev edition and lean kernel correct. But most of us r on the retail. Is there anything else to change besides the interactive for better performance?
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
I can tell you for sure...this scripts works fine for plain jane stock kernel (because that is all you can use on retail Verizon N3) as long as you change the "interactiveX" to just plain "interactive"
Obviously you need root to swap out the script.
Sent from my Note 3 via Tapatalk
donc113 said:
I can tell you for sure...this scripts works fine for plain jane stock kernel (because that is all you can use on retail Verizon N3) as long as you change the "interactiveX" to just plain "interactive"
Obviously you need root to swap out the script.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Big difference in battery life when i changed interacticeX to interactive. Thanks for this OP. :thumbup:
Just want to provide my stats after using the script on eclipse rom 2.2./interactive. Screen on time was 6.5 hours with the phone. Before the script I would average about 4 hours. I want to thank the OP, this was a great tweak. Thumbs up.
Just giving you all a heads up.... I think there may have been a few errors in the stock init.qcom.post_boot file (they are human too, remember).
I am testing a few small changes to certain lines in the "factory" script to make sure. A brief explanation of it is that there are certain lines I removed from the one you all are using right now, and I did so because the file paths being called out did not exist!
However, I was going over this again tonight, getting ready for the official LP release and decided to review this odd discrepancy one more time. After doing some digging, I found that the file that some of those values were intended to be written to, were actually somewhere else!
Doh! - Sammy/QC. It is very possible that this location changed from a previous design or fs structure and somebody simply forgot to modify the script. Very interesting indeed.
Anyways, after I run this for a couple of days and do a little bit more investigating, I'll post the updated script for all of you.
Updated link and file. Please update if you were using this before, as there are many changes that were critical to stability and performance (errors made in this stock script)
Other devs, I recommend working this into your ROMs, given that fact.
red_can_soda said:
Updated link and file. Please update if you were using this before, as there are many changes that were critical to stability and performance (errors made in this stock script)
Other devs, I recommend working this into your ROMs, given that fact.
Click to expand...
Click to collapse
Question. So if this new file is set up for stock kernel for now, is it set to interactive or do we still need to change from interactiveX on retail?
Edit: was being lazy. Went ahead and went through script. Didn't see interactiveX anywhere.
red_can_soda said:
Updated link and file. Please update if you were using this before, as there are many changes that were critical to stability and performance (errors made in this stock script)
Other devs, I recommend working this into your ROMs, given that fact.
Click to expand...
Click to collapse
I'm not so sure the latest script is good or not....on my stock kernel Verizon N3 (NC4 firmware and kernel with NK1 radio) using the new script seems to have killed my battery life. I went from 33% to 20% in about 20 to 30 minutes.
I reset by restoring original script...rebooting...restoring your original script (interactiveX changed to interactive)...rebooting
I had to charge the phone so can't give a real check until I get back to 33% or so.
Sent from my Note 3 via Tapatalk
donc113 said:
I'm not so sure the latest script is good or not....on my stock kernel Verizon N3 (NC4 firmware and kernel with NK1 radio) using the new script seems to have killed my battery life. I went from 33% to 20% in about 20 to 30 minutes.
I reset by restoring original script...rebooting...restoring your original script (interactiveX changed to interactive)...rebooting
I had to charge the phone so can't give a real check until I get back to 33% or so.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Same here on battery drain. Not as smooth either running biggins rom "possible reason". I might try this on a stock Rom to see if that makes a difference. Hard to beat untouched biggins right now though.