yashsingh1/xdaforums huggingface dataset:
[Samsung Infuse 4G] crazynfo:
My comprehension of the conservative Governor versus ondemand: Conservative governor will step through each frequency one at a time until the top is reached or cpu usage is between the thresholds. My understanding of ondemand is that is tends to stay at your high and low frequencies mainly.

So given the above:

The fewer frequencies set the less time it will take conservative to reach your max. (Higher perceived performance, snappier feeling)

The more frequencies set the more opportunity for battery saving you have, but it may take longer to feel the full power of your phone. (Feels slightly slower, possible battery savings)

I have attached a series of shots with my settings, I am getting stable -125@100mhz, maybe it's luck, maybe it's a matter of time. With 1.0 I UV'd too much and managed to corrupt my internal sd(fixed with a format). I tested the -125 for 20 minutes with stabilitytest.

Anyone viewing the pics, it's a UOT based theme I am working on...I will post it in themes & apps when it's done.
[Samsung Infuse 4G] Entropy512:
It's a tradeoff, crazynfo described it pretty well. Fewer frequencies means you reach top speed faster. More frequencies means possibly better battery life.

I bet you'd see very different results if Quadrant "pre-ramped" the CPU by loading it for a little bit of time without measuring performance.

If you use the Performance governor, it'll peg the CPU at maximum speed at all times. Horrible for battery but a good way to get an idea of what your "best possible" Quadrant score will be. I would never use Performance for real-world use though.

For whatever reason, even though I never touched those values in the source, I'm seeing my device report 80/60. I'll see if I can poke at it when I get home, as I mentioned in my PM, tonight I'm going out almost immediately after returning from work.

Lower values for both of these will bias the conservative governor towards higher frequencies (better speed/lower battery), higher values bias it towards saving power unless performance is REALLY needed.

That's a good description of the tradeoffs.

Edit: When I get home I need to take a look at Battery Monitor Widget, it seems to be able to display discharge current? So it must be looking somewhere other than the location in sysfs that CurrentWidget looks at...
[Samsung Infuse 4G] DarkH2O:
If I'm going to flash back to stock from this to one of the stock ODIN firmwares is there anything special I need to do first?

Edit**

I see its not.
[Samsung Infuse 4G] tjy8tim:
my phone doens't read my ext-sd card anymore...can't format it either with the phone, is it corrupted? do i have to use a computer to format to fix it?
[Samsung Infuse 4G] MikeyMike01:
Try reseating it.

Sent from my Infuse 4G
[Samsung Infuse 4G] tjy8tim:
did...no luck. T_T

i think i corrupted without resetting the uv in setcpu before i flashed to 1.5.1...is that possible? it was -300mv across the board...sigh
[Samsung Infuse 4G] jojowill:
Is there a way to get rid of the startup glitch? You can refer to my thread in general if you are unsure what I mean
[Samsung Infuse 4G] samsungcaptivates:
hey crazy nfo i used your exact settings you posted and got sod so i changed to no uv on 100 and no more sod i guess you are lucky !
[Samsung Infuse 4G] 2sl0w:
Thanks for the settings... I was afraid to undervolt the 100mhz setting as low as you but other than that used the exact same settings in voltage control. I had initially set everything to -50 but these settings are showing even better batt life after 12 hours.

Cant wait to see your theme when it is done, I am using matted blues right now. But, It just isn't as good on this device as it looks on other phones.
[Samsung Infuse 4G] halfnelson117:
I'm having troubles with random freezes after flashing this kernel. I can only use the phone for around 30 seconds on V. 1.5.1. I'm running infused 1.5 with the matted blues theme.

Sent from my Infuse
[Samsung Infuse 4G] samsungcaptivates:
i have flashed every version available of this kernal including the latest and have had no real succes with any of them exept version 1.0 i have now gone back to 1.0 with the newest release i had sod on wake with uv setting so removed all uv and had issues with the screen not waking up after a call to let me hang up and the screen was unresponsive when trying to anwser calls not everytime just enough to annoy me into going back to 1.0 also with the new version and conservative gpu when my phone woke from screen off it would take 15 seconds generally for the screen to respond to any interaction i would wake up the phone and it would go back to screen off before i could get it to unluck i was running over stock rom
[Samsung Infuse 4G] 2sl0w:
What program are you using to overclock? set cpu or voltage control?
[Samsung Infuse 4G] 13_:
Just feel like saying this. I do not understand everyone's addiction to SetCPU. It baffles me. Voltage Control works great, is free and was made for this family of phones(HummingB), and have never had any issues with it.

lol.... i feel better now....

Also: Ondemand and Hummingbird is like peas and carrots for myself. Its prolly mem timings/scaling tripping it up along with a side of the fact its froyo.
[Samsung Infuse 4G] crazynfo:
tjy8tim -- When running more extreme UV than I am now, I experienced corruption of internal and external sd. I was only able to fix the internal sd by doing a ultimate unbrick including .pit. The external sd I fixed by putting in the pc and formatting. So use caution when trying settings, unexpected things can happen. My internal would mount 1 out of 10 times, but the other 9 it would loop through media scanner 2-3 times, then it would not show up.

My personal addiction with setcpu is presently simple... 2 things, A)I like the sliders for Voltage 120% better than the ones in voltage control (in voltage control my big fingers change UV settings while I scroll) B) I really like the Info screen & all it includes.
[Samsung Infuse 4G] samsungcaptivates:
I used set cpu why would voltage control do anything diff than set cpu arent they both doing the same thing just diff gui's
[Samsung Infuse 4G] 2sl0w:
From what I have heard voltage control is more friendly than setcpu.

I started with setcpu and had a ton of problems with voltage control it has been smooth sailing. At first I thought I had a bad CPU.
[Samsung Infuse 4G] samsungcaptivates:
Ahhhh ok well i tried voltage controll originally i was just so comfy with set cpu as i have used it on multiple devices many times
[Samsung Infuse 4G] JordanED69:
So voltage control is best?
[Samsung Infuse 4G] The Jack of Clubs:
this kernel did fix the ffc. but i have gotten a few crashes. ive turned off all undervolting, seems to have stabilized it for now. my battery life seems to have gone bad, probably because no uv? also im still not able to disable any frequencies. i might end up back on 1.5.2 soon.
[Samsung Infuse 4G] MikeyMike01:
SetCPU is free too... You can download it from its XDA thread.

Sent from my Infuse 4G
[Samsung Infuse 4G] 13_:
CPUMaster is out there also from Antutu. I think that everyone should not just stick with one for the sake of sticking with it. Try them all. Some devices will work better with one than the other, some will OC and UV amazing some won't do squat. Side note: I am not hawking VC, lol, I'm not even using it atm, I'm just stating it is simpler and more specific to cpu and have not had control issues using it. Good luck :)
[Samsung Infuse 4G] Ltilt2:
So what is the lates kernel? cause I see on the OP, it only goes up to 1.5.2 and I have read some where in here that it's up to 1.5.3.

how is 1.5.3 kernel? is it stable or are people still having sods and crashes? and are we still at 1.6 ghz?

If this has been asked and answered, disregard my reply and I will keep reading.

thank you
[Samsung Infuse 4G] 13_:
I think 1.5.3 is a revert to 1.5.1 except it has fixes for orig 1.5.1 making it 1.5.2 ,doing away with orig 1.5.2, and in revision history making it 1.5.3 but named 1.5.2 .... lol... I just confused myself. I think i remember mention of an update this weekend, maybe sit tight till then :)

Also.. mentioned was testing @1.7 and maybe push to 1.8 , of course i could be wrong.
[Samsung Infuse 4G] thomas101:
I installed 1.5.2 and it crashed everytime reboot. I were able to scan the sd card then crashed. I have to go back to version 1.5.1
[Samsung Infuse 4G] Ltilt2:
that sounded like, Who is on first and what is on second...lol

got it, thanks for the info.

I stayed with 1.5...its been good to me..speed and batt life aswell and no crashes or sod...
[Samsung Infuse 4G] Entropy512:
So here's the deal:

1.5.1 was originally planned to be just a fix for undervolting and a few tweaks to the build scripts (the latter of which only affects those compiling the kernel from source - bedwa and myself.)

So originally it would have been a build containing up to the "readme update" commit on 7/1/11 at https://github.com/bedwa/Infusion-Kernel/commits/master

At the last minute bedwa threw in the "speedmod" commit, and that became the 1.5.1 release. The speedmod commit from 7/2/11 is what broke everything.

Not sure exactly what was in 1.5.2

1.5.3, which hasn't actually been released as a compiled kernel, contains bedwa's 7/4/11 "revert speedmod" commit, which undoes the changes performed in the previous commit.

In theory, any kernel compiled from the source tree as of 7/1/11 and after 7/4/11 should be identical. The kernel that bedwa posted halfway through the thread is a build off of the 7/1/11 "readme update" commit. So it's "1.5.1 minus speedmod".

It may prove easier to reference kernels by build date/time or git commit revision rather than put a version number which can sometimes be confusing, as this proved. ;) Even referencing them by git commit isn't always good, as initramfs changes aren't reflected in the git history, and same for toolchain changes. (I'm going to be testing a move to a newer toolchain tonight, and if successful I'll throw bedwa a pull request on github for the changes.)

I'd put up my build, but it includes some tweaks I consider risky/dangerous unless you are 100% confident in the quality of your chargers, and as I've learned over the past week - there are a LOT of crap chargers out there.
[Samsung Infuse 4G] JordanED69:
Ty very much bro. Another brain always helps ;)
[Samsung Infuse 4G] Suzook1:
ok I am going to try this again and install along with infused 1.50

I have Kernel and Meta-Inf saved in drop box on the SD. In Kernel there are two files. Which do I choose when I reboot into Clockwork? Probably simply but this stuff is greek to me.

really appreciate the help
[Samsung Infuse 4G] Entropy512:
http://xdaforums.com/showpost.php?p=15350139&postcount=475 - Download the ZIP in that post. Do NOT extract it, just put it on your SD card, reboot to recovery (I recommend doing it by doing a long-press of the power button to bring up the power menu), and choose that zip from CWM. Make sure to choose the "zip from sdcard" option however it's worded. Do NOT use any of the "apply update.zip" options - those will simply apply whatever you have on the SD card that is named update.zip.

Sorry my instructions are slightly vague, I'm not booted into CWM at the moment.
[Samsung Infuse 4G] meltee:
Entropy, I'd love to try your build. I'm sick of the battery draining even though it's connected to a charger while using navigation. I've purchased 6 different chargers hoping to resolve the problem. The Samsung charger seems to work better than the rest yet the battery still discharges.
[Samsung Infuse 4G] Suzook1:
finally

Thank you SO much. I finally got it to work. Now my only question is which app should I download to control my over clock :)
[Samsung Infuse 4G] Entropy512:
Well, I'm not sure if my build will help THAT specific problem, in fact it may make the situation worse as it'll be more likely to brownout a weak charger. It's something I'm going to investigate further the next time I go for a drive of decent length, specifically whether the MAX8998 charge current includes or excludes phone drain (CPU/GPS/screen/etc.)

In any sane design it should not include phone drain, and hence increasing it may make the "battery drain during navigation" situation worse by overloading a charger.

Which chargers have you tried? I have tried the following:

Walmart "Just Wireless" charger - no published current spec - too weak

AT&T MicroUSB charger - no published current spec - weak on an epic scale

Monoprice "1A" charger - weak, analysis of the charger circuit says it's good for at most 400-500 mA. The 1A rating is a blatant lie

Griffin 2.1A charger for iPad - seems to work properly for navigation, but it's too small, almost impossible to remove from the car's jack

Scosche reVIVE II 2.1A charger for iPad - works GREAT with the car dock. Without dock it gets detected as USB (I expect the latter as the charger is designed for iDevices...)
[Samsung Infuse 4G] Suzook1:
so my quadrant score was 1018. that seems pretty low now that I am doing the oc. Seems others are getting much higher results?

using set cpu

Settings: First screen max 1600000, min 100000, scaling conservative, set on boot

Profiles: Screen off 100 max, 100 min, Priority 50 and conservative

voltages: 1600, 1400, 1200, 1000, 800, 400, 200, 100, set on boot

Advance: all -1

thanks for any help
[Samsung Infuse 4G] Entropy512:
As I understand it, conservative can cause quadrant to under-report performance, as Quadrant measures performance during the time conservative is ramping up.

Try the "performance" governor briefly to get an idea of what your best-case Quadrant scores are.

And then remember that Quadrant scores are relatively meaningless, it's an easily gamed benchmark that doesn't necessarily reflect the loads of real-world usage.
[Samsung Infuse 4G] Suzook1:
Entropy512 you are the best. I will give it a shot. So you are suggesting performance only as a temp and setting it back to conservative for good?

update: well adjusting that got me to 1195.

I guess it feels quicker but its hard to tell. My battery seems to be draining a little faster though.......
[Samsung Infuse 4G] bradbusa:
ya, performance governor will kill your battery quickie style. you can also get better results on the conservative gov, but only enabling the even numbered frequencies (1600, 1400, 1200..etc) i've been running like that for a couple days and am happy with the performance/battery life
[Samsung Infuse 4G] 13_:
HA... beautifully worded. For the life of me I could not construct that sentence. Tried and failed miserably. :cool:
[Samsung Infuse 4G] JordanED69:
using setcpu or voltage control? and wht kernel version?
[Samsung Infuse 4G] Entropy512:
Yup. In theory you should be able to change the up/down thresholds in Advanced with setCPU (or equivalent), however it appears that the up/down thresholds are hardcoded in a table in arch/arm/mach-s5pv210/cpu-freq.c

I'm going to talk with bedwa about figuring out if there is any way to make this user-configurable. The table has the neat advantage of having different thresholds for each frequency - unfortunately that also makes it much more difficult to change thresholds.

Something seems a little odd about your Performance quadrant score... I'll check into that, tbh I've never even bothered with Quadrant myself.
[Samsung Infuse 4G] meltee:
Entropy, I've used the following

AT&T MicroUSB charger - took it back. it sucked

Griffin 2.1A charger for iPad - I agree that its hard to remove. seems to work though.

Sasmsung CAD300M - Currently using

Rocketfish Premium Micro USB Vehicle Car Charger - Got this one from Best Buy. Seems to work good. has extra usb port.

I've had a couple of universal/usb tablet chargers from Fry's that claimed 2A output yet Battery Monitor Pro reported them as outputting 700 to 800ma. Don't know what that was about. The chargers listed above output 1100 - 1111ma.

I love this phone but the charging issues drives me nuts. I've tested Nav/Charging performance a bunch. If I use auto brightness + Nav I loose 3% battery in about 30 miles. If I turn the brightness all of the way down I can maintain the battery charge for that 30 miles yet its hard to see the screen. Seems that it has to be firmware that is regulating the charge. I'm no hardware engineer though......
[Samsung Infuse 4G] TehInternetzOozer:
I flashed this kernel and now I can again score @ Quadrant over 2200 points on conservative scaling 100, 200, 400, 600, 800, 1000, 1200, 1400 and 1600MHz without UV. Battery on this kernel lives long with heavy using. All day, everyday with WiFi 24/7 streaming Pandora for about 5 hours and about 3 hours with screen on @ highest brightness. Smooth, fast and flawless.
[Samsung Infuse 4G] bedwa:
That's how I went on my "how the @#$% do I get my kernel to compile excursion." I was compiling 4.x MB kernels, 11.x MB kernels, and after I made the build script AND swapped back I was able to make the 7.4 MB ones that booted.
[Samsung Infuse 4G] Entropy512:
All I had to do was swap back. In my case, the 2011 CodeSourcery release built a kernel of the correct size AND it booted and got to the launcher screen, that's when it died.

With your tree, it shouldn't even build with an upgraded toolchain, it'll bomb on one of the Samsung video drivers.

Unfortunately feeding the non-charging tweaks I have back to you is more difficult than a simple pull request - a pull request will include the charger tweaks. :(

So, I think this is the git-fu needed for you to grab the right tweaks:

git remote add entropy512 git://github.com/Entropy512/Infusion-Kernel.git
git fetch entropy512
git cherry-pick 8b1891d392328bebccf4
git cherry-pick 69ec2f9dd10473e762ea

The commits in question are:

https://github.com/Entropy512/Infusion-Kernel/commit/8b1891d392328bebccf4f9bffa1ac0af337797e2 (Re-enables dmesg)

https://github.com/Entropy512/Infusion-Kernel/commit/69ec2f9dd10473e762ea1aaed34e2db7003e5858 (fixes the one file that bombs with the new toolchain - still some Makefile-fu or something needed to work with the latest chain.)

Edit: To be clear, the second commit there does work with the old toolchain.
[Samsung Infuse 4G] bedwa:
K. I'll hop on it momentarily. I was thinking about adding the CC (CrossComp) fix, but again that was what was getting me my jacked up kernels (or something along those lines), so I dropped it like a brick.
[Samsung Infuse 4G] Entropy512:
I'm about to test the new toolchain again, using the compiler flag fixes in the Defuse kernel. We'll see how they go.

Oh, thanks for the link to the Hack Pack - the FSA9280 datasheet had some useful information (specifically, overcurrent protection kicks in at 1.5A, so that's another reason to consider dropping BAT charge current when in the car.)

Edit: The following two commits, in addition to the one fix above, seem to allow the 2011 toolchain to be used. Testing it right now, but it's working better than it did before:

https://github.com/Entropy512/Infusion-Kernel/commit/d699a376135022379f428f57d09a774f8fecbf11

https://github.com/Entropy512/Infusion-Kernel/commit/658f5f43c40797b6a5d07dfd8ebe254d3870cf97 - this one shouldn't be needed but I screwed up the previous one.

Edit 2: Oh yeah, when installing/reinstalling CodeSourcery, watch out for PATH mangling. Make sure your PATH variable is still being set right.

Edit 3: Crap just saw a spontaneous reboot...
[Samsung Infuse 4G] bedwa:
Work on the battery stuff and when you have a full pull available. Sounds like you're almost there anyways... ;)

Edit: and on the CrossCompiler, I download the advanced, dump it in a folder and leave it there and change my CC path. I've got both in my ~/Kernel folder. ;)
[Samsung Infuse 4G] drowningchild:
Just got this phone earlier today, great work on this kernel ;)
[Samsung Infuse 4G] crazynfo:
Welcome to the wonderful world of the Infuse! It's great to have another dev join us!
[Samsung Infuse 4G] bedwa:
Thank you VERY much. :)
[Samsung Infuse 4G] drowningchild:
just reading through this thread :p

stable with @ least -100 UV on each step using every other clock 100-1600

ondemand seems stable to me(all ive been using since installing kernel)

& you -shouldn't- have to port interactive to have smartass

late night toying with my birthday present :D
[Samsung Infuse 4G] Entropy512:
Well, so far, any kernel compiled with the 2011 toolchain has been unstable for me, even after working in the Defuse team's latest compiler flag fixes/tweaks.

I'm trying a kernel built from the latest sources using 2009q3 to see if it's stable - if it is I'm going to fire off a pretty big pull request to bedwa including the charging tweak. At this point I'm mostly convinced that it is safe.

Edit: I am going to go into the touchscreen driver tonight and set it up so debugging can be disabled. It's really chatty and responsible for 90% of our dmesg content. No wonder people want to disable printk() - we have some really chatty/spammy drivers. But disabling printk() is not the answer, making the driver shut up is... Even with BATTERY_DEBUG enabled, the battery outputs a fraction of what the touchscreen does as far as dmesg spam.
[Samsung Infuse 4G] LinuxBozo:
The issue with the newer toolchains is cell data. You can recreate the reboot issue by disabling wifi and using cell data. So, it's probably an issue with the modemctl module, but I haven't had time to investigate more. You may want to look at /proc/last_kmsg after a reboot. However, it's mainly an issue in gcc version. 4.4 works, 4.5 doesn't. Given that, you can go up to 2010q1 toolchain just fine.
[Samsung Infuse 4G] bedwa:
Thanks for the info!
[Samsung Infuse 4G] Entropy512:
Thanks for the pointers, and the tip on last_kmsg.

I hate modem-related instabilities... They plagued xdandroid due to wackiness in smd_tty.c that no one could ever figure out completely.

Now that I know where to look I'll attempt to poke a bit at it myself. I was going to try and hunt you down on IRC tonight to see if you'd had stability issues with the new toolchain but now I know the answer. :)
[Samsung Infuse 4G] justin860:
Wow this kernal is amazing fast set at 160000 :)
[Samsung Infuse 4G] Entropy512:
I think you left off a 0, either that or you have very low expectations if you think 160 MHz is fast. ;)

I found the manual page for "git rebase" which might give me an opportunity to get a pull request shipped off to bedwa more quickly than I originally planned.
[Samsung Infuse 4G] bedwa:
WOOHOO! :D
[Samsung Infuse 4G] slider2828:
Just thought I would post my stable settings. Seems to work great on 1.5.3 @ 1600mhz. Even on 1.5.0 my phone was only stable at 1.5, but 1.5.3 seems to work at 1600.

Noop and Conservative

1600 -75

1400 -25

1200 -25

1000 -50

800 -75

600 -100

400 -100

200 -75

100 -50

These settings worked well for me....
[Samsung Infuse 4G] tight686:
I'm gonna try these out. If I break my phone you owe me!

;)
[Samsung Infuse 4G] stuartmc:
I'm running 1.5.3 too and cfq / on demand with 100 min. 1600 max. and I've been rock stable for days now. I haven't played much with uv, but my battery life seems pretty darn good just as it is, so I'm happy. Thanks bedwa!
[Samsung Infuse 4G] Entropy512:
Holy crap rebasing did Bad Things, now it's problematic to push stuff back to my repo on github... I'm such a git noob. :( So I undid the rebase.

Well, you've got a pull request. I THINK you can reject some of the commits, which you should.

I wonder if there's a clean way to keep local Makefile changes local...
[Samsung Infuse 4G] byuboy87:
im on refuse 1.6 & infusion 1.5. completely stock, there was an option in the music player to output 5.1 surround. i still have the option on video player, but was wondering how/if i can use it with music player (got a pair of the beats by dre, highly recommend them). i do remember still having that option in one of h8's earlier roms, & i know that this kernel is based on the community kernel with voodoo fix. i guess wat im askin is.. it a rom thing? r a kernel thing?

message from Sams inFuse running REFUSE 1.6, INFUSION 1.5