yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] lexluthor:
So are those tweaks that might help with the speed and stability over stock?

And I can install this kernel on my stock phone? If I want to revert back to the stock kernel, I can just reinstall that from the backed up copy that I'll make using SGS kernel flasher?
[Samsung Galaxy S (4G Model)] lumin30:
Please move your questions to Q&A forum.
[Samsung Galaxy S (4G Model)] icy56:
Weird, my phone actually runs cooler and has better battery life when undervolted and on smartass v2. And it also doesn't crash when I underwolt on setcpu compared to when I used tegrak ultimate. My phone is super unstable with tegrak
[Samsung Galaxy S (4G Model)] QUIETLYloud:
Just thought I'd share...

I'm on scom-Floyd edition with setcpu (smartassv2 with voltages set -75 across all frequencies except 1300 & 1400 which are set -50) no reboots running cool
[Samsung Galaxy S (4G Model)] nazcalito:
I'm back to beta 5. I tracked the speed using OS Monitor and liked the way the phone uses the 1000, 1100, 1200, and 1300 frequencies that got put in to the kernel as well as the 1400 I have it set at. I think any funny results with tegrak or quadrant are something those programs are doing and not the kernel. Antonx's kernels have been very stable.
[Samsung Galaxy S (4G Model)] AntonX:
Updated OP to version 1.1 rc1 with few more featured for completeness.

Added two I/O schedulers, SIO and BFQ. You don't have to use them, especially if you don't exactly know what they are.

Added native swap support (somebody asked), but I don't recommend ever using it. They system will become too unresponsive with it. Native swap doesn't go well with Android memory management, it doesn't work well with slow flash drives, plus you trash your SD card a lot sooner.

Switched config to smaller faster TinyRCU, seems to be a logical change for one CPU systems.

Things that didn't make to the kernel:

Tiny Preempt RCU - it will not make the phone any faster, and it seems that some kernel devs have problems with it.

zRam (compcache) - I actually added it, it kind of worked, but was sometimes crashing the phone during initialization. It's probably not a good thing to have on our phone anyway. So I took it away.

Unless somebody comes with an idea what else to add to the kernel, I'm going to freeze the changes, wait few days for bug reports, and name it a release.
[Samsung Galaxy S (4G Model)] lainvalenajr:
Love overclock kernel. Set to 1.3 ghz with no problem other than my battery dies quicker lol
[Samsung Galaxy S (4G Model)] daothanhduy1996:
Ya, after I did GR and reflashed the rom, it seems to be cool now but still a little heat on and I guess just because of the weather of Vietnam as it's very hot here (32 Celsius Dregree now @@) lol...and btw, how can you UV with Setcpu (I mean what are the value you set as I set it minus 25 each from 1000 - 1400 but it crashed after few hours use :s)
[Samsung Galaxy S (4G Model)] eollie:
The kernel is already undervolted so lowering the undervolt setting even more is too much for your specific phone. Each phone is slightly different and can handle setting differently.
[Samsung Galaxy S (4G Model)] JonnyStreetz:
There Is a thread in the general section you should check it out.

Sent from my Maybach s 4g
[Samsung Galaxy S (4G Model)] ipaq_101:
I am getting terrible battery life since 0.3, all kernels after that had drained my battery faster.

Not using overclock or bln. Think I might go back the the third beta release. Oh well...
[Samsung Galaxy S (4G Model)] AntonX:
Don't go to older version yet, let's try to troubleshoot. I'm myself running 1.1rc1, the battery is good and no different from 1.0b3. It can be some app issue, I had couple of weeks ago Tapatalk suddenly not letting the phone sleep.

Install BetterBatteryStats (apk link at the bottom of second post):

http://xdaforums.com/showthread.php?t=1179809

Connect the phone to power and disconnect to reset the counters.

Let the phone sleep for some time, like half an hour or more.

Start BetterBatteryStats and select Other | Since Unplugged.

Check Awake and Screen On. The difference between them should be 3%-5% max.

If it's more than that select Partial Wakelocks. See if any program at the top of the list is holding a wakelock for a long time. If there is, that's your problem.

If there are no partial wakelocks, check Kernel Wakelocks. See if there is any wakelock at the top taking more than just few percents.

If you don't find any wakelocks, I think your battery should be fine. Just keep checking every now and then for Partial Wakelocks to see if you find a program that gets stuck.
[Samsung Galaxy S (4G Model)] eollie:
AntonX Im not sure if it is available for our device but would it be possible to add this governor to the kernel?

Found the description in this thread http://xdaforums.com/showpost.php?p=19846276&postcount=1
[Samsung Galaxy S (4G Model)] ipaq_101:
I will give it a shot, thanks!
[Samsung Galaxy S (4G Model)] Juls317:
hmmm, two random reboots in about 30 minutes time. i've been messing around with setCPU seeing if i can get it to run my old Tegrak voltages and it doesnt seem to like that si i'll up my voltages and see if that fixes it
[Samsung Galaxy S (4G Model)] ipaq_101:
Tried what you said Anton, looks like the wifi radio is the culprit, I will do another test to confirm. But no other apps were draining the battery. I am using the SCOM 4.4 rom. I have to use wifi calling all day because I have no signal at work.

Maybe I should switch roms....
[Samsung Galaxy S (4G Model)] AntonX:
What voltages were you trying to set? So we'll know what not to set our phones to ;)
[Samsung Galaxy S (4G Model)] AntonX:
The source is available, I can include it. I don't think that it will behave better that any interactive governor like smartass or similar. I can make a test build and if you like it I keep it, if not I kill it.
[Samsung Galaxy S (4G Model)] AntonX:
What was the difference between Screen On and Awake? There was nothing in the Partial Wakelocks or Kernel Wakelocks? Or WiFi Calling was there?

Wifi On itslef usually shows a lot of percentages in the Other, it's normal.
[Samsung Galaxy S (4G Model)] QUIETLYloud:
I'm currently using scom-Floyd, oc/uv(with tegrak, couldn't figure out how to change the go io scheduler with setcpu) scheduler set to bfq and governor to smartassV2 and my battery has done well... I'll try a different setup after this charge cycle
[Samsung Galaxy S (4G Model)] AntonX:
You can try Voltage Control, it's similar to SetCPU (no extra modules needed) but lets you change i/o scheduler as well.
[Samsung Galaxy S (4G Model)] QUIETLYloud:
play store gave me a error, will try to get it after the games
[Samsung Galaxy S (4G Model)] bhundven:
Note the top three processes in the battery stats. PowerManagerService, svnet, and radio-interface.

It would be interesting to find out if there are any other phones that have the same "ST Ericsson's THOR M5730 HSPA+ Thin Modem" (ifixit) and if they have the same kinds of power management issues as our phone?
[Samsung Galaxy S (4G Model)] xaocon:
Btw? Are you getting ok performance with that? Usually not a good choice on flash memory.
[Samsung Galaxy S (4G Model)] AntonX:
Bryan, I'm not seeing any problems with power management. I've been monitoring it recently quite carefully and didn't see anything strange. I don't have any suspicious kernel wakelocks, the top three usually are PowerManarerService, svnet, and mmc_delayed_work, but together combined they take very little, maybe 1 to 3%, which is nothing and quite normal. radio_interface is not even in the top ten on my phone. You have any of the these taking more %?

I'm not using WiFi Calling, in fact I don't even have it installed. Can in be doing something weird? Anybody has apk with it so I can install it back and try?
[Samsung Galaxy S (4G Model)] eollie:
This is a nice app. I like the interface and the ability to change the scheduler is awesome.
[Samsung Galaxy S (4G Model)] chadster214:
I tried this kernel but it seems that it's holding back 70mb of space when replacing the FOTA files. compared to bhundven latest rc1 kernel.
[Samsung Galaxy S (4G Model)] QUIETLYloud:
Outside my realm, but Google indicates that the Sidekick 4g has it.

Haven't noticed anything slowing up lagging or functioning poorly. For what it's worth my benchmarks are higher, measured with Antutu.

May have been to the fact that when I'm in my sons doctors office I have no service, perhaps it's the modem trying to connect. Since it has moved down the list
[Samsung Galaxy S (4G Model)] m0bstr:
what are the best setting to get the most battery life??
[Samsung Galaxy S (4G Model)] AntonX:
Turn it off.
[Samsung Galaxy S (4G Model)] eb13:
I'm about 90% percent positive that the sidekick 4g is the only other one. It was specifically designed to handled T-mobile's network speed (something I learned in a corporate training last year, selling point for techy types) the newer version I believe is Hercules.

"These are not the droids you're looking for..."
[Samsung Galaxy S (4G Model)] bhundven:
hrrmmm. ok. When you hit a brick wall, get a book on demolition.

I'd say.
[Samsung Galaxy S (4G Model)] Juls317:
I will tell you as soon as I figure out where you posted your voltages so i can go back to them (i saw them somewhere in I'm pretty sure this thread but i cant find them now)
[Samsung Galaxy S (4G Model)] eollie:
Is this what your looking for? I knew where it was because I had it bookmarked for some reason.

http://xdaforums.com/showpost.php?p=25368027&postcount=136
[Samsung Galaxy S (4G Model)] Juls317:
Yup, thats it!
[Samsung Galaxy S (4G Model)] daothanhduy1996:
Look like those seting is far lower than values go with the kernel and it seems to be unstable (got some reboots with those) but I just decrease about just 10 - 20 each value go with the kernel and it seems to be ok :p (keep the voltage vl go with 100 - 800 mhz and slightly UV 10 - 20 mV depend on which 1000 - 1400)...anw, I prefer to stay on what AntonX gave to the kernel than UV more since it didn't improve anything :D

Sent from my bricked 8-bit NES with ICS 4.0.4 lol
[Samsung Galaxy S (4G Model)] AntonX:
Here is 1.1rc2 TEST-ONLY version. You don't have to download it unless you want to check the new governors.

Tegrak's lulzactive governor. This will stay. It seems quite popular, plus you can fine-tune it with Lulzactive app from market.

Intellidemand governor. This one is for testing only. It's not very popular. Most probably I will remove it unless somebody really likes it. It seems that the description is deceiving, it has nothing to do with GPU. It's just regular ondemand when CPU load is high and something else when it's low. I'm not sure it's worth including it in the kernel.

http://dl.dropbox.com/u/74713966/sms-T959V-KJ6-antsvx.v1.1rc2.test4.zip

EDIT: lulzactive is acting up, being stuck on one frequency. I think started doing this once I installed to control app.

EDIT2: Maybe I fixed lulzactive. Uploaded 1.1rc2.test2, link changed.

EDIT3: Maybe not. Still gets stuck when switched to from other governors.

EDIT4: Removed lulzactive, unreliable
[Samsung Galaxy S (4G Model)] mike-y:
Anton, I've been on your beta1 for about a week, and it's been rock solid and very good battery life (this last charge lasted over 3 days).

Going to install your newest revision on the next charge. Thanks for the hard work
[Samsung Galaxy S (4G Model)] FBis251:
Has anyone else tested ondemandx yet? On my phone it got stuck on a low frequency and it lagged the hell out of my phone until I switched back to smartassv2.
[Samsung Galaxy S (4G Model)] geekilized:
FB, I will try it today and report back later tonight or tomorrow.

Sent from my SGH-T959V
[Samsung Galaxy S (4G Model)] AntonX:
I tried it, seemed fine. I forgot, are you on Tegrak or SetCPU/VoltageControl?
[Samsung Galaxy S (4G Model)] eollie:
AntonX thanks for adding that governor. I suggested it since it seemed that it would be better on battery life. I about to flash it.

FB I was using ondemandx it didnt seem to get stuck on on freq but it wouldnt stay ramped under load. If I was using a app that was cpu intensive it would goto max then drop to 800 and stay there until I closed the app and reopened it.
[Samsung Galaxy S (4G Model)] AntonX:
Updated TEST-ONLY version.

Removed lulzactive governor, it has a bug. When switched from and then back on, the startup code is incorrect, so the governor does nothing after that. I's designed to be started upon boot and never changed after. I probably can fix it, but not sure if it's worth it (it behaves too similar to smartass2), and at least one mode dev is fighting the same problem, so I'll watch him ;)

It's possible that some other governors don't like being switched to and from on the fly, that's why sometimes we are seeing the phone stuck on one frequency.

I also removed smooth ramping-up to high frequencies. It seemed to be a decent idea for ondeman-like governors, but more intelligent interactive governors should take care of this by themselves.

Intellidemand governor is still there.

This is test-only version, it will not go to OP, you don't need to try it unless you want to.

http://dl.dropbox.com/u/74713966/sms-T959V-KJ6-antsvx.v1.1rc2.test4.zip
[Samsung Galaxy S (4G Model)] Kyndig66:
On test2, with Tegrak app, scaling with lulzactive governor, 100-1200 values, and lulzactive app (all values default), I was talking on the phone with my bt and the phone rebooted. Then bt wouldn't reconnect, so I immediately flashed back to 1.1 rc1. This happened several hours ago so I don't have any data. Thought I'd let you know though, in case the info might be helpful in some way. Thanks for keeping on top of things! I'll flash test4 in just a bit.
[Samsung Galaxy S (4G Model)] AntonX:
Maybe lulzactive has more than one bug. 2:0 against it in the kernel.
[Samsung Galaxy S (4G Model)] nazcalito:
quadrant scores increased by about 500 on test2 and that was simply using ondemandx and smartassv, not lutz. Tested on two different phones.
[Samsung Galaxy S (4G Model)] eollie:
AntonX I think its safe to say intelleidemand can be nixed. I charged the phone lastnight fully. Unplugged it and went to sleep. 7 hours later im at 58% and nothing but a little browser lastnight and I think I checked my email twice this morning/afternoon.
[Samsung Galaxy S (4G Model)] AntonX:
I didn't find it to be any better that others. It will be removed.
[Samsung Galaxy S (4G Model)] TerrorCandii:
Ever since update to RC1, my girls phone won't hold the OC. It keeps going back to stock clock. Any ideas as to why it does this? Should I just flash back to beta?

TerrorCandii™ Gaming uses

Juggernaut5.0/Streamline kernel
[Samsung Galaxy S (4G Model)] AntonX:
Updated OP to 1.1rc2

Intellidemand governor is nuked.

Smooth ramping-up for high OC frequencies is back but only for ondemand-type governors that tend to jump to 100% speed right away. For other governors it's disabled.

Couple other small changes.
[Samsung Galaxy S (4G Model)] QUIETLYloud:
Downloaded... But just to be sure, would YOU qualify "badass" as ondemand-type? I've read that it's a mix.

Off topic alert:

Very good job on the kernel
[Samsung Galaxy S (4G Model)] AntonX:
badass is more of interactive, it's using a timer and goes by average load. I've looked at it, the guy wrote it for a device with big frequency table (almost 30 discreet frequencies) when we only have 7 if overclocked all the way. Because of that calculations for our device are not quite right. Some parameters need to be adjusted, but I don't think it's worth the effort.
[Samsung Galaxy S (4G Model)] mikhail777:
Is 1.0b3 the only kernel not overclocked
[Samsung Galaxy S (4G Model)] daothanhduy1996:
Yes, just read the OP carefully man (in changelog)
[Samsung Galaxy S (4G Model)] AntonX:
The latest is not overclocked by default as well. It will run up to standard 1 GHz unless you enable scaling to higher frequencies.
[Samsung Galaxy S (4G Model)] nazcalito:
Can you stick a 1.5 ghz in the overclock just for the hell of it and maybe some intermediate levels like 1150 1250 etc or something like that? At least with tegrak the phone will use all the available sppeeds up to the top one which may be an advantage. On the previous non OC kernel the speeds would have a jump between 800 and whatever the top speed is. I suppose I could do it myself but I don't have a Linux partition on my desktop although I have plenty of disk space. It's just a few lines of code. :-P
[Samsung Galaxy S (4G Model)] AntonX:
1.5 Ghz - NO! I thinks even 1.4 is a little too much. It's probably OK for short bursts but if constantly run at that speed somebody may fry the CPU. The phone is freakishly fast even at 1.3, why more?

50 Mhz steps will not make much difference. I thought about adding 1.1 Ghz so governors will use this one first instead of jumping to higher frequencies. Should I do it?
[Samsung Galaxy S (4G Model)] turtlepa:
I slightly disagree. I think my phone may be a bit more flexible with uv oc etc, but not enough where i couldnt safely lower even more. i want to switch back to tegrak and use dsextons original values from his post with his build.prop. They are hundreds of mAh	lower. I usually add 25 onto all of his values (not the kernel defaults) since they are so low, but then my phone is on for 2 days minimum w/o recharge. the set values in this kernel he made them UV yes, but the values are not enough to cause any instability voltage wise whatsoever. Just what i have tried. For 1ghz my phone uses 1100 mah or something. Its 1300mAh i think in kernel, 25mAh is not so insane a drop.

Hrm i didnt read dao comment completely right. I cant believe u have reboots at 25 more under. Search for dexstons values and use tegrak to put them in (paid). then add 50 to each value, worth a shot. Actually ill test it out for u as i wasnt on this kernel when i uv i was on rc3 by bryan. Ill report back
[Samsung Galaxy S (4G Model)] eollie:
Please read AntonX's instructions on how to properly use Tegrak on this kernel.

http://xdaforums.com/showpost.php?p=25462529&postcount=4

He is recommending setcpu or voltage control. If you try to OC/UV this the way you would the kernels without native oc/uv turned on you will have issues TRUST ME. I flashed the kernel with oc/uv natively turned on and didnt realize it and did the typical oc/uv settings and had all kinds of issues.
[Samsung Galaxy S (4G Model)] nativesmiley:
whats the best settings for SCOM Rom with SetCPU?
[Samsung Galaxy S (4G Model)] eollie:
There isnt best settings for any rom. Trial and error is your best bet. Check AntonX's thread he has some values posted.
[Samsung Galaxy S (4G Model)] xaocon:
agreed. most of my speeds are -75 to -100 mAh below stock. runs great. i may be able to go farther but I haven't tried.
[Samsung Galaxy S (4G Model)] nazcalito:
re: NO 1500 -- My phone is not.presently stable at 1500 but I figure that some 4g phones got a better batch of CPU s and might be. Even so, Antonx's cautiousness paid off with this kernel as it's very stable.
[Samsung Galaxy S (4G Model)] itzik2sh:
Hi AntonX

Video recording audio distortion is supposedly related to some audioautogain that is implemented in the kernel (see thread from SGS i9000) :

http://xdaforums.com/showthread.php?t=896826

Can you look into it or maybe contact Supercurio on this ?

On my opinion this is a crucial issue for our device.

Thanks !!!

P.S - I posted this on the Q&A forum : http://xdaforums.com/showpost.php?p=25671136&postcount=9

but I think it is important enough to raise the flag high and above. Is there something I can do to help analyze this ?
[Samsung Galaxy S (4G Model)] turtlepa:
I was just explaining on how i was getting great battery with tegrak hence why i switched amd disagreed that yhis kernels values arent that low
[Samsung Galaxy S (4G Model)] AntonX:
itzik2sh ,

The Recording Presets in Voodoo actually work, but to the limit. If you set it to Loud Environment, the recorded level drops quite a bit. Unfortunately it doesn't make the sound much better. I guess that's the best Supercuirio could do, and I see that he did try to adjust the gains. If the microphone itself is distorting there's nothing can be done.

I haven't changed anything that would affect memory, except added some stuff to the kernel (governors, swap support). The additions were not that big, maybe about 10KB. You didn't use any different lowmemorykiller settings in init.d or anything like that? What memory are you checking, Andorid? It can be misleading, Android tries to stuff as much as it needs into memory. Check /proc/meminfo, MemTotal, that's how much memory is left to the system. Mine reads 330916 kB.
[Samsung Galaxy S (4G Model)] AntonX:
I made another TEST version, not yet ready for OP, but you can try.

- Extended frequency table with 600MHz, 900Mhz, 1.1Ghz frequencies.

WARNING!!! If you have set UV values already, check them! The frequency indices have shifted so your table needs to be adjusted.

- Small tuning of smartass2 governnor to make it slightly more battery friendly.

- Small change to Voodoo Sound, it's possible I was applying recording presets in the wrong place and they were overwritten (maybe partially) with Samsung values.

Note: The new frequencies may or may not be used by all governors. For example smartass2 ramps up in 200Mhz steps so it will most probably pass 900Mhz and 1.1Ghz all the time. It can hit them on the way back (it ramps down in 300Mhz steps) but it depends on the maximum OC frequency you set. You can play with smartass parameters in sys/devices/system/cpu/cpufreq/smartass.

WARNING: This version DOES NOT work with Tegrak Overclock. Don't even try.

http://dl.dropbox.com/u/74713966/sms-T959V-KJ6-antsvx.v1.1rc3.test1.zip
[Samsung Galaxy S (4G Model)] itzik2sh:
Hi AntonX

Thanks for the quick reply.

I haven't used the voodoo sound "loud env" recording preset. I will test that.

Setting 'HiFi recording' (128x oversampling) didn't change the recording sampling one bit though...still 66kbps, 16khz...

Regarding the memory - I was referring to the free memory I see in Go Launcher EX and to the fact that apps starting to crash due to lack of memory.

I will check the /proc/meminfo, MemTotal and let you know.

Adrenaline shot 14.1 uses this RAM script

:

#!/system/bin/sh

# Copyright� 2011 Juwe11

# 13.8.2011 Updated VM values - Thanks to [Kalis] for help

# 18.8.2011 Added values for oom_adj

if [ -e /sys/module/lowmemorykiller/parameters/adj ]; then

echo "0,1,2,4,6,15" > /sys/module/lowmemorykiller/parameters/adj

fi

if [ -e /sys/module/lowmemorykiller/parameters/minfree ]; then

echo "2560,4096,6144,12288,14336,18432" > /sys/module/lowmemorykiller/parameters/minfree

fi

if [ -e /proc/sys/vm/swappiness ]; then

echo "0" > /proc/sys/vm/swappiness

fi

if [ -e /proc/sys/vm/vfs_cache_pressure ]; then

echo "50" > /proc/sys/vm/vfs_cache_pressure

fi

if [ -e /proc/sys/vm/dirty_expire_centisecs ]; then

echo "1000" > /proc/sys/vm/dirty_expire_centisecs

fi

if [ -e /proc/sys/vm/dirty_writeback_centisecs ]; then

echo "2000" > /proc/sys/vm/dirty_writeback_centisecs

fi

if [ -e /proc/sys/vm/dirty_ratio ]; then

echo "45" > /proc/sys/vm/dirty_ratio

fi

if [ -e /proc/sys/vm/dirty_background_ratio ]; then

echo "25" > /proc/sys/vm/dirty_background_ratio

fi
[Samsung Galaxy S (4G Model)] daothanhduy1996:
Just wanna confirm: DON'T EVER USE TEGRAK WITH THE RC3 (test1) or you'll mess your phone up ^^
[Samsung Galaxy S (4G Model)] AntonX:
Ouch. What happens? With the latest tegrak version? Even if you just set scaling and voltages?

If 600 and 900 really create troubles maybe I should remove them. They seem to be running fine though with SetCPU.
[Samsung Galaxy S (4G Model)] AntonX:
Oversampling will not make any difference. It's all internal, ADC upsample digital signal so all downstream processing is more precise. At the end it's downsampled again. It makes sense for Hi-End systems but not for out crappy microphone.

Setting recording presets - I wonder why you didn't try it before, that's exactly what supercurio did to improve recordings in different environments.