yashsingh1/xdaforums huggingface dataset:
[Samsung Infuse 4G] Ltilt2:
Ondemand is unstable. Ur phone will not work properly.
[Samsung Infuse 4G] slider2828:
Please guys just read the thread.... MikeyMike01 posted his OC/UV settings for 1.8... I have settings that are close to his too and works fine...

No use reinventing the wheel.. Try his. If your phone doesn't wake up then you UV'ed your lowest settings too low... if you are running quadrant and it stalls, then either you OC'ed too high or your voltage on the highest settings is too high....

Just saying.... Ondemand has been unstable since last build.... wouldn't use it as Ltilt2 has said
[Samsung Infuse 4G] samsungcaptivates:
I had sleep death on 1.8 with no uv at all
[Samsung Infuse 4G] Ltilt2:
Guys, like slider said. Read and try using some of the devs settings. Bedwa makes sure his kernel are working properly on his device before realising it to the public. Thats why Im puzzled as why some of you have issues.

Edit..spareparts/ window speed/off

Animation speed/ off....my device works way better this way.. just incase anyone is using this kernel and spareparts.. good luck everyone
[Samsung Infuse 4G] slider2828:
Sometimes its overvolted to for a range, so some undervolting IS needed to cool the cpu down when its running... Did you try MikeyMike's Settings.... Try setting everything to -50....

I must add, overclocking is an art.... SERIOUSLY, it takes practice and a lot of testing to have a good result....

If everyone could do it and if every processor can do it, then samsung would have released it with those settings.....
[Samsung Infuse 4G] Ltilt2:
Try using Mikeymike's settings..
[Samsung Infuse 4G] ookba:
Same here, frequent, with Ondemand and Conservative.
[Samsung Infuse 4G] The Jack of Clubs:
if anybody wants voltage recommendations, ive tested these all day and they work.

ondemand is sadly not stable since before 1.5.3. now if you have on demand you will most likely get a sleep of death and disabling voltages with ondemand doesnt work.
[Samsung Infuse 4G] Dani897:
this is true. there are many things a cpu can have a sensitivity to. there are different schools of thought, and some cpus just don't overclock very well.

example, my captivate (same cpu part number btw) can not exceed 1.3 ghz. it just won't do it. there is a narrow 50mv range that it runs at that speed. any more or less volts and it dies. not only that but in the situation I use 1300mhz I need more volts in the lower settings than if I had the top clock at 1200, and I can go even lower at the low speeds it I keep it tto stock clocks or underclock.

if you have trouble and need to ask why, you might just need to acept that your cpu can't do what bedwas cpu can. or you can keep trying things.

some tricks I might use to get that last 100mhz are that I will set to performance governor to find the range of voltage for that speed that is stable. ill go 50mv over the minimum that works then ill turn the clock 100mhz below it on with the same voltage setting or no more than 50mv lower in actual voltage. from there I go in increments of 400mhz down but I always include 200 and 100mhz. once I have the clocks and voltage set on the high end ill turn the voltages foe the others down till I have instability or sleep death and go back up 50mv.

^this is what I do to get the best possible clock speeds because it accounts for instability caused by voltage changes and large changes in clock speeds.

for battery life I do my uv settings from the low speeds up, I may need to sacrifice max clock speed this way but it rarely means that I can't overclock at all, occasionally it just means less overclock. it depends on what your priorities are.
[Samsung Infuse 4G] Entropy512:
No, don't use other dev's settings.

As others have pointed out, every CPU is DIFFERENT.

UV settings that might work great for one person will be a complete nightmare for another.

As an example, someone posted settings where he had -150 mV undervolt from 100-400 - It works great for him but on my phone, this would be a guaranteed instant sleep of death. I get instant SoDs (e.g. I turn the screen off and I can't come back 100% of the time) at -100, occasional ones at -75, and solid stability at -50.

The original post links to a post from _13 which links to a great tutorial:

http://xdaforums.com/showpost.php?p=10936691&postcount=1102

Also this one is good:

http://xdaforums.com/showpost.php?p=15572072&postcount=772

Edit: My tree is a little behind at this point. I have a lot of merging to do, and even trying to remember what the hell I was doing before the weekend. I was out a good portion of the weekend, and now my time is split between two devices (Galaxy Tab 10.1 and the Infuse). The Tab probably won't be consuming very much more of my time for a while though.
[Samsung Infuse 4G] MikeyMike01:
I've read that noop is for flash memory, and the others aren't.

Sent from my Infuse 4G
[Samsung Infuse 4G] Suzook1:
update

ok last night at 12:30am the phone was at 70 percent after removing the init. With everything off (wifi, background etc) I left the phone alone until 9am this morning. It had 61 percent. thats a bit better.

BUT, then I used wifi for 1 minute and shut it off and 25 minutes later its down to 58 percent.

Sitting there is lost an average of 1 percent per hour. But when used for under two minutes it loses three percent. MADNESS.

This is the one thing that really bothers me using an andriod phone.

HELP
[Samsung Infuse 4G] jonnyboy_jbmatrix:
First, thanks bedwa. I can appreciate the amount of time and effort you have put into this kernel.

I've been testing this kernel and with conservative, the best I can achieve is 1.4, with no UV. But I get SOD and spontaneous reboots. With anything any higher, it immediately freezes and can not complete a boot cycle. It either freezes or reboots. If I use performance then I can use every freq including 1.8.

If I use ondemand, I can also use all freqs, but I get the SOD.

If performance works at 1.8 but conservative and ondemand SOD, freeze and reboot at 1.4, is the problem with the governor?

I'll stay with conservative and 1.2 and UV until ondemand is fixed.
[Samsung Infuse 4G] cpunchin:
Are you using SetCPU or Voltage Control?. With SetCPU I was having similar issues. With VC, nada... :cool:
[Samsung Infuse 4G] jonnyboy_jbmatrix:
Both, but not at the same time.

EDIT: I had both installed at the same time, but deleted the data for the one that I was not trying. After this post, I deleted SetCPU and conservative appears to be stable @1.8. thx
[Samsung Infuse 4G] Kif420:
Thanks bedwa!! super stable kernel at all speeds. Keep up the good work!!

Grapes
[Samsung Infuse 4G] Entropy512:
I/O schedulers perform two functions:

1) Reorder disk reads/writes to avoid thrashing magnetic disks. Doesn't apply to flash memory devices like ours

2) Keeps one app from hogging I/O resources by scheduling reads/writes to be "fair".

I/O schedule will have little effect on battery life. Which one is best depends on the read/write workload of the device. It seems like BFQ is fairly popular for Android devices, I do need to read in more detail. An I/O scheduler could improve how "responsive" the device feels during normal use.

The V/R scheduler that drowningchild added seems too spinning-media-oriented to me - lots of references in the description to head travel distance and direction.
[Samsung Infuse 4G] 13_:
See this Mini Guide for a quick tut on OC here.

As for Voltage Control:

The first tab (left) is where you will set your min / max speed. (example: slider 1 set at 100 , slider 2 at 1400). Also you will select the scheduler; noop, cfq etc and the governor; on demand, performance, etc, which controls the scaling speed between the states.(rec, cfq and on demand, just as OP states)

The middle tab is where you select the active states. ( example: green is active, lets say you want an OC of 1.3Ghz, you will have 100,200,400,800,1000,1200,1300 states green and all others red. You could also leave 1200 disabled etc etc. Part 2 of the middle tab is the UV... that's where the guide above comes in. While setting UV's it is best to do one state at a time, test and either keep or change. While testing UV and OC, it is common to get freezes, crashes and reboots, do not be alarmed, it only means you are removing to much voltage or there is to much, or you OC speed in not stable.

Recommend save settings by using the phone menu button then load settings to test. Once you have your UV and OC stable and efficent use the menu button and Save as Boot settings. this will set the settings no further adjustments required.

Good Luck, have fun... once you put in the work it makes up for it later ;)

Then you should be in a stock kernel thread.

Killing the battery? Overheating? Change settings every 3 days? These things are all untrue. Just saying.....
[Samsung Infuse 4G] wint0nic:
I am using on demand.
[Samsung Infuse 4G] Frooty:
What's the best way to test the UVing? Is there anyway to what state you're currently on? I'm not seeing it anywhere and I don't see how it's possible to test it properly besides just randomly doing stuff if you can't tell what state you're on.

Are you just supposed to deactivate all of the states except the one you're currently testing?
[Samsung Infuse 4G] 13_:
Yes. You would unselect all states EXCEPT the one you are testing UV and stability on and also set min / max speed (ex: 1Ghz min/1GhzMax). This would be for fine tuning. To verify what speed s you are running you can use CPU Spy from market.

Personally the only time I have individually tested all the states 600 or below is if I had sleep death issues, Otherwise 800 and up I would do in this fashion. The goal is to use as little V as possible and keep stable, thereby reducing power consumption and heat.

I usually start testing with lowers at this > 100, -100 >200, -75>400, -75>600 -75 or -50... and the rest I walk down one by one.

You can use the phone to test stability, play games, watch videos , run quadrant, run nenamark, run neocore, LOL.... everyone has a favorite way to torture test.
[Samsung Infuse 4G] Frooty:
Thanks. When changing your states//UV settings, once you hit apply it changes it instantly right? If that's correct, then is it normal to be able to undervolt all the way to the lowest setting at 1400 Mhz?

That's what I did, hit apply, and ran Stability Test for about 20 passes and then Neocore a few times and I didn't have any problems. Am I doing it wrong or is my just awesome and capable of undervolting as low as it can go?
[Samsung Infuse 4G] 13_:
You sure your running 1400? Min/Max on first tab. I would hit menu button > save profile >menu load profile. You may have the state selected but your allowed Min Max speeds are still set at lower speeds.

I dont think there is anyway you could UV 1400 that much and it still be running. 1250mv or below is probably insta-crash for most if not all.
[Samsung Infuse 4G] Frooty:
Yeah I did still have the min set to 100. However I just changed it to be min/max both at 1400 and then saved and loaded the profile. I tried running Quadrant but it FC'd when it started, so I moved it up one notch from the lowest setting and now everything seems to be fine still. I was able to run quadrant once without any problems, and then Neocore twice without any problems. I'm running Stability Test now and it's still going strong.

My phone is at 42C right now, but I'm guessing that's just because it's been at 1.4 Ghz for the past half an hour or so.
[Samsung Infuse 4G] indymx:
I just ran Quadrant again on the infused kernel then twice on this one..

Each time I killed all unneeded processes first, and ran with only Quadrant and the screenshot program in the background.

first shot is the infused kernel, second is Infusion stock with no changes in Voltage Control and the third is bumped to 1400, cfq & ondemand.

Also, just a note, I created an init.d folder in /etc with Root Explorer.. When I rebooted it was gone.

I think my better score this time was due to me killing apps..

Going to run another without killing them to see what I get now.
[Samsung Infuse 4G] bedwa:
Try making it in the system/etc folder. Should take care of it. ;)
[Samsung Infuse 4G] indymx:
Three more shots, 3 more conditions...

All of these were done without killing processes.

The first is at 1300 cfq/ondemand, second 1400 cfq/ondemand and 3rd with the infused kernel a minute or two after a reboot.

I think what this is telling me is that in real world conditions, there isn't much difference, and that Quadrant is a lousy benchmark program...

I'm going to run some similar tests tonight with a new benchmark program I just saw.. CF-Bench

I'll post results of that too.
[Samsung Infuse 4G] byuboy87:
thanks for quick response... followed ur directions, clockd at 1300 & everything seems in order. quadrants showing 2100 now.... thanks again

message from Sams inFuse running REFUSE from the great h8
[Samsung Infuse 4G] 13_:
No problem ;)
[Samsung Infuse 4G] brocabortzfield:
Does anyone else's phone seem slower?
[Samsung Infuse 4G] jgeezy24:
Did u get voltage control? Default speed is 1.0 so it prolly is.
[Samsung Infuse 4G] bedwa:
Just a note for all, this WILL be my first agenda to fix with my next version. It doesn't survive at 1.0 well. :(
[Samsung Infuse 4G] 13_:
That may be but let me say that the OC on this kernel is stellar. Very stable, especially considering it is the first one. I'm impressed with the amount of UV the infuse can take, and it seems that 1.5 and 1.6 wont even make it break a sweat when if they are implemented. I'm gonna guess 1.5 for the sweet spot on performance and battery. Nice work... pls 2 continue :D
[Samsung Infuse 4G] MikeyMike01:
Quadrant sucks.

Sent from my Infuse 4G
[Samsung Infuse 4G] super1395:
I'm sorry I'm a little new to this but. i know what OC is. but what is UV, and could you define it in laymen's terms please
[Samsung Infuse 4G] indymx:
Under volting
[Samsung Infuse 4G] byuboy87:
happy to help. from what i learned yesterday lol, uv allows u to conserve battery power by setting your processor speeds and voltage use lower. from what i am to understand, some are content with the power/performance undervolted as it improves battery life. ..hope this helps!!

message from Sams inFuse running REFUSE from the great h8
[Samsung Infuse 4G] bedwa:
K. This is a PSA:

1. Stay away from OnDemand, period. (I am going to remove the option from 2.0, It's been too much hassle since becoming unstable.)

2. As much as I love SetCPU, please go with Voltage Control. It seems that those with instability have a tendency to be using SetCPU or SetCPU with VC, just an observation here.

3. If you are going to be concerned about how much more juice OCing takes, please do one of two things: Do like me and have a second battery (after all, it's the one of the reasons I went with android over iPhone.... removable batteries rock,) or please, Please, PLEASE, take the time to set up your own UV settings that work for your device. As the main developer for the overclocking my phone is going to be more flexible than most others since I've gradually moved into my settings in comparison to anyone just coming to this kernel from stock.

Thank you for your time with this PSA,

-B
[Samsung Infuse 4G] TehInternetzOozer:
Dude, that is exactly what I did yesterday and with only switching from SetCPU to Voltage Control, my battery life improved. Over 7 hours of phone sitting with WiFi always on and screen off, I lost only 11% of a battery. I have multiple apps, that are running in the background and uses internet every few moments.

The settings I use with conservative scaling are:

1.8 GHz - 50

1.6 GHz - 75

1.4 GHz - 100

1.2 GHz - 125

1.0 GHz - 150

800 MHz - 150

600 MHz - 150

400 MHz - 150

200 MHz - 150

100 MHz - 150

With those settings I have had no SoDs, no heat issues and everything runs smooth.
[Samsung Infuse 4G] bedwa:
Thank you. Case and point my friends.

As I mentioned, I LOVE SetCPU, but it was designed primarily for most other processors other than Samsung processors. Enter the wonderful man Xan and his app. He made this from the ground up so that we ALL could be noobish and not have to rely on manual script editing.
[Samsung Infuse 4G] Dani897:
this is true. noop is a simple scheduler and would be inferior on a mechanical disk, flash memory doesn't really care. other schedulers will optimize mechanical disks in one area or another. there is no reason not to use noop. don't trust benchmarks. even if they give you greater scores with other schedulers it is using resources to do so, this isnt bad on a pc with multi channel ram and multi core cpus and resources to spare but i think on this generation of phone hardware we should keep things simple and streamlined. deadline may give an advantage if you are heavily multi tasking but will normally show lower benchmarks, it may do nothing at all on the stock settings.
[Samsung Infuse 4G] byuboy87:
what were the changes made with voodoo sound? in laymans terms plz? lol thanks...

message from Sams inFuse running REFUSE 1.6, INFUSION 1.5
[Samsung Infuse 4G] Dani897:
supercurio released a new driver version. not sure what that means exactly but maybe he has documentation in his thread in the i9000 forum
[Samsung Infuse 4G] Ltilt2:
Well said Bedwa.

LOVE THIS KERNEL!!!
[Samsung Infuse 4G] drowningchild:
I've been running interactive 100-1800 no problems at all since last night, smooth as butter :)
[Samsung Infuse 4G] JordanElliott:
Interactive?
[Samsung Infuse 4G] drowningchild:
its a governor :)

similar to ondemand

what smartass is based off of

got smartass commits im going to test soon too :P
[Samsung Infuse 4G] JordanElliott:
Ok.sweet. Let us know how.it.goes
[Samsung Infuse 4G] drowningchild:
laggy :(

1234567890
[Samsung Infuse 4G] JordanElliott:
Lol.dang that blows
[Samsung Infuse 4G] The Jack of Clubs:
how do you have interactive?
[Samsung Infuse 4G] drowningchild:
My own repository :)
[Samsung Infuse 4G] corps20k:
Do you HAVE TO remove OnDemand?

It works flawlessly for me ever since your first kernel and I get great battery life. I'm running 1800MHz and I'm undervolting. All I do is make a SetCpu Screen Off (sleep) profile that uses the conservative governor, 100MHz min, 800MHz max and I have never gotten a SOD or any freezes.

Thank you for all your hard work!
[Samsung Infuse 4G] drowningchild:
could be replaced by interactive??
[Samsung Infuse 4G] tight686:
Care to share? :)
[Samsung Infuse 4G] lucifurr:
LogCat errors

Just installed 1.8 today... some strange occurrences like VC not being installed after upgrade, but just re-installed it. Reset my VC settings to settings similar to bedwa's, but without UV.

Am seeing a lot of these messages in my LogCat via Eclipse/DDMS when device is idle:

07-12 18:30:42.414: ERROR/DataRouter(2746): [*] Received suspend/ resume event but DUN is not up so neglect

07-12 18:30:42.573: ERROR/DataRouter(2746): [*] Received suspend/ resume event but DUN is not up so neglect

Is this anything to be worried about, especially since I'm trying to improve battery life?

Many thanks to all of you in this thread, my Infuse is smooth and fast (also running Infused v1.5)!!

Thx.

Kevin
[Samsung Infuse 4G] drowningchild:
for those who are brave ;)

interactive, kernel hz set higher, smartass(that doesnt work) bfq, v/r, & fifo schedulers, tinyrcu & ext4 patches

thats it

http://www.mediafire.com/file/fa8xz0l7oq06p1r/nukeinfusion.zip

just flash from CWM

i want teh feedbacks
[Samsung Infuse 4G] Ltilt2:
what app do you use to control oc and what are your settings?

more info would be great, thanks!
[Samsung Infuse 4G] crazynfo:
Re:drowingchild

Maybe try seeing if there is something you could use in the OC Daemon:

http://xdaforums.com/showpost.php?p=14529333&postcount=5

They are using some C code running outside of Dalvik space to change governors without delay. Looks promising, but I don't have the skills to port it over.

Flashed your modified kernel using SGS Kernel Flasher, no problems with the flash.

Using Voltage Control for settings. I will confess I have finally gotten off my SetCPU horse and I am now running voltage control too, with the new 1.8 kernel, setcpu was causing some weird issues for me.

I hope you can collaborate with bedwa and have your changes merged for 2.0, seems like we've got you, entropy and bedwa all working hard on changes for a even better 2.0. I'm going to have to go look in the bank account and start contributing to more dev's...our scene is growing. I think I owe bedwa a second donation too :)

Presently Stable: BFQ/Conservative 1800,1600,1400(-75);1200,1000,800,600,400,200,100(-50) (Testing limited to stabilitytest for 10 minutes on performance, settings have otherwise proven to be safe on my personal device using bedwa's builds)

Find me on IRC (freenode@#INFUSE4G) if you want me to try different settings, I'll be on a for a while... Thanks for sharing your build drowningchild.
[Samsung Infuse 4G] MotoMudder77:
Not sure if this is a Kernal issue or not, started a few days after running v1.5.2.

Having issues charging, Phone will not recognize being plugged into anything every day or so, having to pull and reinsert the battery while plugged in to a charger to "shock" the phone, as someone told me. It works, but still an issue being so frequent.
[Samsung Infuse 4G] tight686:
So far so good bro!

Edit: I like how smartass runs more than interactive!
[Samsung Infuse 4G] turbodolphin:
So happy thankyou!

VoltageControl settings now

Gen: max 1.8ghz (apply)

Advanced 100 - 1800mhz all -100

Bionix 2.0 Infusion1.8

Forgot: cfq & ondemand

Seems stable so far? We'll see!
[Samsung Infuse 4G] bedwa:
can't quite make out the screenshot info, what was your quad score?
[Samsung Infuse 4G] turbodolphin:
2242, sorry ... Trying out new screenshot app, guess it doesnt upload the same
[Samsung Infuse 4G] bedwa:
no problem... Thanks! :)
[Samsung Infuse 4G] Dani897:
bedwa, any plans to go to 2.0ghz? and if i want to compile your kernel from source but with different clock settings where can i find all the multiplier and divider tables and which apply to the cpu and gpu?

also is there anything else that has to be done?
[Samsung Infuse 4G] crazynfo:
drowningchild -- quick update on your kernel testing:

I've locked my frequency @ 1.8 1.6 1.4 & 1.2, and ran stability test 1.5 for at least 5 cpu runs, at each frequency and gotten rock solid stability with my settings above. Everything looks good so far on my end. I'm about to halt my stability testing, and just give you a day's use feedback. I'll be on IRC a while yet if anybody needs me to test anything.
[Samsung Infuse 4G] bradbusa:
why is it that you only use two UV settings for all frequencies? wouldn't you be able to use less battery if you were to stagger the uv settings?

again, only asking to understand.
[Samsung Infuse 4G] Ltilt2:
Trying out nukekernel with crazyinfo settings. Seems stable for the moment.