yashsingh1/xdaforums huggingface dataset:
[Samsung Infuse 4G] slider2828:
doubling quadrants to 2400-2500 level is unbelieveable... At this point your are probably 3x speed of a dual core tegra 2
[Samsung Infuse 4G] jonnyboy_jbmatrix:
@a3plew

I added 01 to the filename:

S_.......

to

S01_.....

Sent from my Samsung Infuse 4g using the XDA Premium Android App.

Infused ROM 1.5.2, Infusion Kernel 1.8
[Samsung Infuse 4G] a3plew:
Thank you.
[Samsung Infuse 4G] jonnyboy_jbmatrix:
No problem.
[Samsung Infuse 4G] trouzzermouse:
Ok, got it to hit 1.8 On performance. Its shows on cpu spy, linpack and stability test.

will 1.8, 2.0 run on conservative with the new release?

Thanks!
[Samsung Infuse 4G] Entropy512:
Already plenty of hints to that on bedwa's github repo...

Due to the issues found with 1.5.1/1.5.2, we're all a bit more careful about doing local testing before releasing. bedwa doesn't want another broken release.
[Samsung Infuse 4G] MikeyMike01:
It certainly CAN. It depends on the kernel.

Sent from my Infuse 4G
[Samsung Infuse 4G] TehInternetzOozer:
Many of us could get over 2200 with the 1.6 kernel. With 1.8 I got more than 2400 on clean ROM.
[Samsung Infuse 4G] bradbusa:
2200mhz. As in cpu speed, Not quadrant score.
[Samsung Infuse 4G] bedwa:
Speaking of, I'm making another source push as we speak..... anyone who can download and compile, please do for testing. I want to make sure this is stable before release incase I need to revert.
[Samsung Infuse 4G] xan:
Good luck! :)

I dont own Infuse 4G, but always looking to have more devices supported by Voltage Control!
[Samsung Infuse 4G] bedwa:
Part of the reason when I went for OC scripts to start working from.... I made sure they had UV as well. ;)

Always loved your app when I had a Cappy.
[Samsung Infuse 4G] Entropy512:
One thing I've always wondered - what exactly is the difference between VC and SetCPU that makes Samsungs angry with SetCPU?

Technically they use the exact same sysfs interfaces to the kernel, so it shouldn't matter which one, unless maybe SetCPU makes settings changes in an unsafe order (like enabling OC before tweaking voltages.)
[Samsung Infuse 4G] tjy8tim:
how come people are having so many problems with the setcpu? i've been using it with conservative governor and it's working fine....or am i doing something wrong?? lol
[Samsung Infuse 4G] Agpilot!:
No problems with SetCPU here. Overclocked and undervolted, using conservative governor.
[Samsung Infuse 4G] tight686:
Same here. I've had nothing but good times with SetCPU.
[Samsung Infuse 4G] Entropy512:
Some people claim they've been able to significantly crank their OC/UV settings with VC beyond what they can achieve with SetCPU.

I personally haven't tried, although I'd love to achieve -100 mV undervolt at 100-400 MHz.
[Samsung Infuse 4G] bradbusa:
Been running really well for me and getting excellent battery life. i went to bed last night with 75% battery, woke up this morning with 73%, 7 hours later. the phone was on all night and off the charger. Using infused 1.5.2 with infusion 1.8
[Samsung Infuse 4G] JordanElliott:
Can u write.out the.full setttings you used bro?
[Samsung Infuse 4G] bradbusa:
i reset the stats in cpu spy to see which frequencies were running, and how often. the freq's that are unused i just disabled in VC. no reason to have them enabled if it wont use them anyways. i cand kind of understand why it doesnt like to use the odd numbered frequencies, but i dont know why it wont use 1000, and 600 mhz? and for some reason, the only time my phone will use 1.8ghz is when i put it into performance governor. that explains the 39seconds from the cpuspy screen shot.
[Samsung Infuse 4G] bedwa:
Teaser link....

http://nena.se/nenamark/view?version=1&device_id=512
[Samsung Infuse 4G] JordanElliott:
Ty very much
[Samsung Infuse 4G] JordanElliott:
Damn..
[Samsung Infuse 4G] bradbusa:
you're welcome :) i hope that works as well for you as it has been for me.. i've been on the phone wayyy more than i normally am and i'm still at 15%

usually i try to limit my daily usage to conserve.. now i'm just trying to be wasteful!
[Samsung Infuse 4G] bradbusa:
jesus tap-dancing christ man! that has got to be terrible for battery life! what kind of temps are you seeing when running at those speeds?

i cant seem to get my phone to run any higher than 1.6, unless i put the performance gov on.

i'm seriously impressed with the durability of this phone's hardware
[Samsung Infuse 4G] Ltilt2:
try bfq/ interactive and it will use 1.8
[Samsung Infuse 4G] bedwa:
Fairly well.... seems temp sorta decreases at 2.0+ range unless charging/wireless tether/using simultaneously. Conservative doesn't get as good, but I've had a few 2400+ quads as well....

Gonna release in a few days. Hop over to my git and check my commit for that clock speed..... ;)
[Samsung Infuse 4G] Entropy512:
Already pulled and compiled a few hours ago. Of course I'm only UVing so most of the last few commits don't matter to me... Still on the 2009q68 toolchain.

Have a guest coming over soon so not going to do much more tonight. Almost started mangling the charging code but at this point I think I'll wait until the Canadians get Gingerbread. :)
[Samsung Infuse 4G] bradbusa:
Yea, I dont have bfq or interactive. I'm rocking bedwa's 1.8 release.
[Samsung Infuse 4G] bradbusa:
I dont know what a git or a commit is, nor do I know how to use it.

I'm good at following directions if you tell me how to do something, but I'm not that knowledge about techy stuff unless you're talking about cars or bikes
[Samsung Infuse 4G] Ltilt2:
Oh ok
[Samsung Infuse 4G] popesmasseuse:
A little random, but I noticed that when I turned the governor on to performance my battery charged at a significantly faster rate. I am going to play around with this, but in the matter of 30 minutes it went from 60% to close to 100%. That's not normal.
[Samsung Infuse 4G] Dani897:
wow, i didnt know this chip had it in it! that is amazing! you should start overclocking the gpu as well. 223.334 mhz was perfectly stable on almost every captivate with unhelpfuls kernel. i feel that 250 or more is well within reach for many of us.

now we just need to see if we can get data to the cpu faster. it seems like the benchmarks aren't improving like they should above 1.5ghz. maybe play with ram timing, change the file system to nilfs2, some other things that i dont understand, i know there is a lot of potential in there.

are there any tweaks we can do to stagefright? i know turning it on with gingerbread will break playback on the stock player for many file types but it also increases h.264 encoding and decoding so much faster that you get 1000+ more points in quadrant! my captivate had close to 3100 at one point.
[Samsung Infuse 4G] popesmasseuse:
I found that 1600 and above is when I start to see close to no benchmark improvements. However, for me, 1500 to 1600 adds almost 200 to my Quad score.
[Samsung Infuse 4G] bedwa:
Let me look into it. That's why I haven't released 2.0 yet.....
[Samsung Infuse 4G] trouzzermouse:
I ran on-demand for half of the day and it was stable. I got consistent 2200 - 2300. I switched back to conservative at 1.6 and I am still getting 2200 - 2300. Maybe breaking in that 1.8 helped, on demand made cpu run at like 75% 1.8 when looking at cpuspy. Wow just ran again and got 2473 on conservative with dealine 1.6mhz small level of UV.....I dunno seems kind of weird, Just got 2486 again same settings.

I know that we are told that the quad scores don't mean much but something is definitely changing. I think Bedwa also said we needed to break in the CPU in a previous post
[Samsung Infuse 4G] Ltilt2:
Are you using bedwas kernel or the nuke kernel? What are your settings? The best i get is 2200 then starts going down.
[Samsung Infuse 4G] bedwa:
I may have an explanation for that.... Not sure, still doing investigation on it, but according to here.... (under the 4_6 STABLE heading) I may have been calculating the clocks and such wrong. I need to evaluate everything over the weekend and I will get accurate readings on this. By the time I'm through, we'll have both accurate readings and performance.

Though, this would account for the inconsistent readings I've been getting and inaccurate benchmarks. May have a line or 2 of code missing too.....

Thank you everyone for your patience while I sort this out to be sure where I'm at. ;)

Also, Thank you Dani897 for mentioning OCing the GPU, without it I wouldn't have stumbled across this....

Edit: More info here. Will continue to keep updated.
[Samsung Infuse 4G] ookba:
What ROM?

10char
[Samsung Infuse 4G] indymx:
I've been playing with 1.8 for a couple days.. Tried a few different settings, and got my phone kicking serious ass. However, all of the music players I have tried stutter really bad. To the point that music is impossible to listen to.

Any ideas?
[Samsung Infuse 4G] bradbusa:
So how might one go about acquiring these bfq and interactive governors I keep hearing about?
[Samsung Infuse 4G] trouzzermouse:
Bedwas 1.8 kernel
[Samsung Infuse 4G] trouzzermouse:
Infused 1.5, everything seems normal again 2200's
[Samsung Infuse 4G] Ltilt2:
Get the nuke kernel.
[Samsung Infuse 4G] bedwa:
Check in the voodoo control app by pressing menu and seeing if the sound driver has been loaded. If not, that would explain it. (The jitter was part of Samsung's shoddy coding.)

Now back to my calculations... found why my supposed 2.4 was getting me higher fps. When I did my calculations, I was only running CPU at 1560 instead of my inflated 2.4GHz, but the GPU was running at ~222 MHz instead of the regular 200.

We may not have up to 1.8 or higher after I am through, but I can promise 2.0 will have better and more consistent performance. ;)
[Samsung Infuse 4G] Entropy512:
Next Infusion release will include the BFQ I/O scheduler in addition to a few others.

Interactive isn't in bedwa's tree yet, only drowningchild's. I think DC wants to beat on it a bit more before firing off a pull request to bedwa.
[Samsung Infuse 4G] AiyoX:
Still new to the android scene. How would I got about flashing this kernal above Infused 1.5.2? Could I get step by step instructions if possible?
[Samsung Infuse 4G] Khan99:
Quick question by a OC/UV noob, I have all the settings in Voltage Control set up to 1800. I have the Max slider set to 1800. When the governor is on conservative and I enter stability test, it only runs at 1400. I can only get stability test to run at 1800 when I set the min/max sliders to 1800, or put the governor on performance or ondemand. Am I missing something, or do you need to run the performance governor if you want the phone to really run at 1800?
[Samsung Infuse 4G] bedwa:
@AiyoX: Just flash in CWM, or use Kernel Flasher but Neldar from the market.

@Khan99: make sure you have checked the red dot for that frequency in the voltage tab. Elsewise that frequency will not be active.
[Samsung Infuse 4G] ookba:
I got the same issue. Music stutters BAD! I heard this was common with Froyo ROMS. I read somewhere that there's a kernel patch that takes care of this!?
[Samsung Infuse 4G] bradbusa:
@kahn: mine doesnt go to that freq often either. download cpyspy and you can see how much time it spends there while you're using the phone
[Samsung Infuse 4G] terra-starr:
I had the same problem, I got around it by turning off all frequences between 1200 &1800.

Works great now, and with UVing, it hasn't hurt the battery.
[Samsung Infuse 4G] bedwa:
In the voodoo control app, is the module loaded? The SGS sound driver sucks without it.
[Samsung Infuse 4G] AiyoX:
Up and running! Lastest Infused kernal + the experimental addon.

Currently running @ 1.4Ghz with everything -150 stable. Very smooth and noticeable performance boost.

Will try up to 1.8 with -150! :D

EDIT: @1.7GHz -150 to all on conservative!
[Samsung Infuse 4G] speedfreak228:
Are you using voltage control? Let me know how -150 does on 1.8 I want to try it
[Samsung Infuse 4G] ookba:
Dont see an option for load module. Any other way I can check?
[Samsung Infuse 4G] indymx:
Ill check that
[Samsung Infuse 4G] AiyoX:
Woo! Successful 1.8GHz with everything at -150

Though when testing I had to disable 1.4/1.6/1.5 to actually bench at 1.8.

I kind of want to see if I could push the voltages lower, but stability tests take too long and I'm a bit impatient after testing for half the day.. :rolleyes:

Now rolling at 1.4 as min 1.8 max

@speedfreak228: Yup! Voltage Control. 1.8GHz at -150mV
[Samsung Infuse 4G] tight686:
Won't that ruin your battery life?
[Samsung Infuse 4G] a3plew:
Those that have trouble benching at 1.8 without disabling frequencies below I think I have a solution. What rom are you running and do you have a program to view root directory such as root explorer?
[Samsung Infuse 4G] DevilDogAK:
Thanks Bedwa

It took quite a bit o tweaking to OC at 1.8 and UV and have a stable device. With your help my phone is wicked fast and I have decent battery life. Keep up the great work! I can't wait to see what comes next.
[Samsung Infuse 4G] TehInternetzOozer:
BATTERY DRAINING INFO:

I used Google Maps with Navigation over 4G with GPS while shopping in a 90 degrees and that was a really sunny day, so the screen was at full brightness. I lost over 70% in under 40 minutes of navigating. The battery temp reached 113 degrees. As soon as I lowered MAX freq. to 800MHz, everything went to a normal level and still, it was smooth and UC let me extend the battery life. I really could not tell the difference between using phone at 1.8GHz and 800MHz. Really. It was just as fast as I expected.
[Samsung Infuse 4G] bradbusa:
i think the first day the phone needed to get used to the fact that the 1.8 freq was there. it only used it when i applied performance gov. both yesterday and today i noticed the phone would use that freq on it's own. and it's starting to use it more often now.

btw, you mentioned a solution, but didnt provide one? wth

lol
[Samsung Infuse 4G] bradbusa:
if you download cpuspy, you can view the frequencies your phone uses, and how often. you'll notice that for some reason this phone really likes 800mhz. most of the apps and programs running will not NEED to use more than that. certainly you can do more with higher speeds, but in most cases i've found nearly no lag at 800mhz
[Samsung Infuse 4G] TehInternetzOozer:
I agree with that. I use CPU Spy for weeks and the most used frequencies are 100MHz, 800MHz and 400MHz.
[Samsung Infuse 4G] bradbusa:
Heres a screenshot from today. Played angry birds for a bit, sent some texts, and cruised the forum. Using conservative gov and noop scheduler.

it took a couple days, but my phone is starting to use 1.8ghz on it's own now
[Samsung Infuse 4G] Entropy512:
This doesn't surprise me - Google Maps does OK even on my old AT&T Tilt 2 with XDAndroid. Really only games are going to push that CPU hard.

There is no persistent state/memory that affects the conservative governor's decisions. The phone can't "get used" to anything in this regard.

The odd thing is that the transition threshold table should make it easier to ramp up past 1.4 GHz. The up_threshold is only 80% CPU usage, not 90% in that range. Down_threshold is also slightly higher, so the CPU might be more likely to "drop down" in this range too.

However, past 1.4, on some benchmarks I/O bottlenecks might cause the CPU to get starved for data. I don't think the governor considers iowait() time when stepping. (It would be stupid for it to do so.) Another reason why benchmarks are synthetic and not indicative of real-world usage.

I should read through cpu-freq.c and figure out what transition_state does. There might be something broken there in terms of going from 1400 to other frequencies.

Edit: I'm fairly certain transition_state is broken, it will always cause the governor to "step up" to 1.4 GHz for any transition start frequency higher than 1.2 GHz. Gonna PM bedwa with details after a shower
[Samsung Infuse 4G] bradbusa:
not arguing, but all i know is that for the first two days with the latest kernel the only time my phone saw 1.8 was when i used performance gov. now it's using it on it's own *shrugs*
[Samsung Infuse 4G] a3plew:
Haha yeah . Got lazy plus I had a couple questions to ask. there seems to be a couple different issues . One issue its making sure the file its being saved in the init.d folder. the other is making sure the file in the init.d file is renamed so that it will be the first thing to apply at boot. I usually delete the volt scheduler file under /ect/init.d and then Make sure to apply the min max freq, conservative governor, and then your undervolt profiles. Once you apply save as boot files. Then with a root explore program go to /ect/init.d and make sure the new file is there. Make if not mount as rw and try again. Once that file is saved make sure if other scripts are present rename it so that it will apply first. Once this is done reboot. After everything is loaded make sure that stock in voltage control app. After go into stability test and it should show your max freq in the biomips.
[Samsung Infuse 4G] a3plew:
Could be if your using infused 1.5.2 that the volt scheduler is set last since there are now other scripts that apply in alphabetical order.
[Samsung Infuse 4G] bradbusa:
i renamed it so that it was being read first.

all the other freq's were used but it wasnt going up to 1.8 on conservative gov. for the first 2 days. didnt think this had anything to do with renaming the file?

for some reason it is using 1.8 now though.. no problems either way. i couldn't tell the difference
[Samsung Infuse 4G] byuboy87:
just downloaded cpuspy... the only frequency thats ever used is 1800. is this a bad thing? im using performance governor. btw, not really sure exactly wat each governor does, but i think i have an idea thru context...

message from Sams inFuse... REFUSE 1.6, INFUSION 1.8
[Samsung Infuse 4G] a3plew:
it appears to revert to a 1.4 overclock and settings that don't truly apply if it isn't in init.d folder at boot.:( It's a series of multiple issues. now entropy seems to found another problem. hopefully this is all sorted out soon. :D
[Samsung Infuse 4G] Entropy512:
That'll kill your battery life.

The governors:

performance - ALWAYS uses the highest clock speed allowed. Will suck battery like crazy. Only good for benchmark epeen IMO

powersave - ALWAYS uses the lowest allowable clock speed. Going to result in a VERY slow device.

ondemand - pretty much ping-pongs between slowest and fastest clock speeds

conservative - Steps up to the next clock speed once CPU usage goes above a certain percentage, and down when it goes below. Will slowly ramp up the speed to max if the CPU is consistently in high use. However I think in current kernels, the "next" state for any frequency above 1200 is 1400, so unless you remove everything in between, you'll probably cap out at 1400. I sent bedwa information on a fix. I don't overclock so I'm a bad candidate for testing the fix.

interactive - Ramps up speed to max as soon as the CPU comes off of idle then ramps it down if usage isn't high. Not in any released kernels yet. drowningchild's commits mark this as "not stable".

Right now our conservative governor uses a fixed hardcoded threshold table where the thresholds change with frequency. I'm discussing with bedwa the merits of having frequency-dependent (but not user changeable) thresholds vs. a single threshold pair that is user-changeable.
[Samsung Infuse 4G] AiyoX:
Hmm after more testing and fiddling, my phone seems to be fine. Leaving it at 1.3Ghz did put noticeably drain the battery faster, but not too much actually. I'm not a heavy user, mainly just texting/twitter/browser/music. :D

With CPU spy, my phone mainly stays at 1.3GHz peaking at 1.6 for anything intensive.

(remember I'm running -150mV every Freq, CFQ I/O, Conservative governer)

I started messing with the CPU governers. With Performance, it always stays at 1.8GHz, Ondemand crashes. Too lazy to figure out why :cool: I'll just stick with conservative.

I decided to lower the min to 100Mhz. I'm starting to find out that it doesn't really go to 1.8GHz unless the lower freqs are disabled

@tight686: Not too much! But it depends on what you do. I decided to lower min to 100Mhz again though

@byuboy87: I think its supposed to do that. It is labeled as "performance" after all. :p

@a3plew Lastest infused rom + loopy addon and I use root explorer

EDIT: ohp, Entropy512 beat me
[Samsung Infuse 4G] The Jack of Clubs:
http://xdaforums.com/member.php?u=2789960 <- how does he have 2.2ghz? i want 2.2ghz.
[Samsung Infuse 4G] drowningchild:
build from sources :D

but as bedwa said its wrong :P

its not hard if you have a linux box, theres a readme right in the git repo
[Samsung Infuse 4G] byuboy87:
thanks for the info dude. my battery life does indeed suck ass, but it has been that way since the day i bought the phone. i actually thought the batt life got better with the 1.8 kernel, but it could be in my head..lol.. anyway, thanks again. we genuinely appreciate the efforts u guys are putting in...

message from Sams inFuse... REFUSE 1.6, INFUSION 1.8
[Samsung Infuse 4G] bradbusa:
i want to know what all this means! and how to make changes like this!
[Samsung Infuse 4G] bedwa:
State of the Kernel 7/17

As has been said, some of the frequencies above 1.8 on my test kernels happen to be phantom GHz. This and the transition states are what I'm going to fix in the 2.0 kernel. It's going to be a total revamp. I don't want anyone to think that I'm forgetting you guys, I'm just having to calculate things extensively as per this post HERE. Look under Version 4_6 STABLE heading.

and Entropy512's right, there are a few transition issues, I'm working on that as well. Sorry for all the issues guys. Shows I'm still a noob in a few things, but I'm learning more each day.

Edit: more info here.
[Samsung Infuse 4G] bradbusa:
if i understood any of what you're going through i'm sure i would appreciate it a hell of a lot more. all i know is that this phone came to kick ass and chew bubble gum. and it's all outta gum! i would not be as happy as i am with this phone, were it not for yours and other dev's hard efforts.
[Samsung Infuse 4G] bedwa:
Thank you, that means alot to me....

Continuing on, I'm rewriting all the clocks for the frequencies as we speak. I've done all the calculations, and am getting ready to type up the clocks soon. Part of why the original code worked as samsung had it and went to 200 steps from 200 on was to sync all the clocks with each other. I have rewritten what I plan the freq steps to be. With 2.0 hopefully these will be the steps (as long as they are stable.)

250, 500, 750, 1000, 1250, 1500, 1750 and 2000

This will allow us to overclock the system bus (which controls both the step variable of the CPU and the main GPU speed) from 200 MHz to 250 MHz, along with upping another bus from 100 to 125. In addition the graphics busses that ran at 40 MHz in the stock will be running at 50 MHz. If it doesn't work, I'll revert to stock figures and calculate the correct increases from there. ;)

I'll make it work. I'm stubborn like that. :P
[Samsung Infuse 4G] 3GBeyotch:
I must be dumber than a bag of hammers...

I'm running Infused 1.50 with Voodoo enabled. I attempt to flash this kernel in rcwm says it successful and when I reboot I get the boot loop.

I've used GTG's unbricker and started over and always end up with the same results. Do I need to disable Voodoo first then apply then re-enable the Voodoo lagfix or what ?
[Samsung Infuse 4G] clown_luv:
How long do you wait before using the unbrick? I flashed straight through red cwm and no issues. And no this kernel is voodoo enabled so there is no need to disable the lagfix
[Samsung Infuse 4G] 3GBeyotch:
@clown_luv - Thanks for the reply - I let the phone sit there about 30-40 minutes before I got tired of waiting. I was watching the logcat, which I posted in the thread earlier, and it was always the same thing.
[Samsung Infuse 4G] bedwa:
Ill track back and take a look at the logcat. I just got to work so it may be a few hours, but I want to make sure it works also..... :/

Edit: question, have you reflashed your rom back over the top of it. With that logcat it almost looks like data corruption with rom parts. If you would, try that....