yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] daothanhduy1996:
hih, Idk, I just cleared Tegrak data, forced it to close and uninstalled, then flashed your rc3 test1 and reinstalled Tegrak (ultimate version, latest though :p) and when I chose "load overclock module" and the screen froze and after seconds, the phone rebooted and everything is fine (Tegrak module was unloaded)...seems like 600 and 900 or maybe 1100 not work properly with Tegrak module but honestly, I don't see it like big problem because I still prefer setcpu to Tegrak since I set UV values in setcpu Voltages down to nearly 100 each and everything is still okay (keep watching stability now) so, don't remove them soon AntonX :p

P/s: Sorry that I didn't log it since I have been using Setcpu now ^^
[Samsung Galaxy S (4G Model)] psguardian:
Anyone using on octane v3 w/SetCpu?

~psguardian
[Samsung Galaxy S (4G Model)] nazcalito:
Yep, the test version makes tegrak lock up on my phone. Don't know why -- the additions shouldn't have done that. reverted to rc2 and everything is fine.
[Samsung Galaxy S (4G Model)] AntonX:
Confirmed the Tergak crash with rc3.test1. E-mailed the developers with some logs, maybe they can fix it. If not I'll have to remove some or all intermediate frequencies.
[Samsung Galaxy S (4G Model)] xaocon:
Is incompatibility with a paid app that does the same thing as free ones important enough to remove good things from the kernel?
[Samsung Galaxy S (4G Model)] eollie:
Actually yes. Until the paid app can be fixed. It's a considered a bandaide fix but also the most logical.
[Samsung Galaxy S (4G Model)] QUIETLYloud:
Is it possible to also have a version with all the freq.'s left in place? I ask

this because since you've added them I have seen a dramatical improvement in battery life even without tegrak, and until this kernel tegrak is all I've ever used.

Okay, I'm confused... In earlier post AntonX clearly stated that it is better to use setcpu/voltage control because with the kernel in its current state, with native oc, there is no need to install the module that tegrak uses.

anyone willing to provide clarity would be appreciated
[Samsung Galaxy S (4G Model)] nazcalito:
The paid app (tegrak) does at least one thing that free ones won't do --OC over 1.4ghz.
[Samsung Galaxy S (4G Model)] TerrorCandii:
Why would you want to go over 1.4? I have my girls at 1.2 and it's silky smooth on everything. Is it just to push scores? I only do light OC'ing, to keep reliability, and life span of my phones....her's and my Galaxy S2. Just curious...

TerrorCandii™ Gaming uses

Juggernaut5.0/Streamline kernel
[Samsung Galaxy S (4G Model)] lainvalenajr:
I once had a g2/disire Z we were able to go to 1.8 ghz crazy how smooth it was but the battery would die in less than 2 hours. Snap dragon 2nd gen processor are nice
[Samsung Galaxy S (4G Model)] icy56:
hell, im undervolted at 1ghz and everything runs really smooth. I really don't think ANYONE needs to go above 1.2ghz
[Samsung Galaxy S (4G Model)] eollie:
Im not speaking for antonx. However if you have this kernel already then you DONT have to flash to a newer version unless you have problems.
[Samsung Galaxy S (4G Model)] QUIETLYloud:
Understood... Just wanted a little in-sight is all, everyday is a quest for knowledge for me, but thank you anyway
[Samsung Galaxy S (4G Model)] eollie:
I want to apologize for the brevity of that post. I didnt even mean to post it.

What I meant was I think the best thing is to not add the values until a fix for Tegrak or the kernel is figured out.

Also you can use tegrak on this just dont install the module. I think people like me that bought the app would like to use it. However I personally had issues and ended up using Voltage Control. But my problem wasnt because of either the app or kernel but because of accidentally clicking on install the module. If you follow the directions AntonX posted tegrak will still work.

Typically if a dev releases something that either breaks or causes another app to break you revert the change until it can be figured out how to fix it.
[Samsung Galaxy S (4G Model)] QUIETLYloud:
No offense taken... I'm sitting on a uninstalled paid tegrak(and voodoo) also
[Samsung Galaxy S (4G Model)] FBis251:
VB-FB Running Antonx's b5 kernel, 5 days, 5 hours, 19 minutes of uptime, logged with the uptime widget (you can grab it on google play). It finally rebooted on me while I was using feedly (an rss/google reader) app.

The phone was stable and worked well the whole time, but I guess it's time to test the latest kernels.
[Samsung Galaxy S (4G Model)] AntonX:
I got reply from Eui Woo Jeong (Tegrak). Unfortunately he will not attempt to fix it as he officially supports only stock kernels. This means that for Tegrak users I will have to completely disable OC/UV. So it will probably be two versions, with OC/UV and without. The version with OC/UV will have some priority with updates.

Here is his reply:
[Samsung Galaxy S (4G Model)] mike-y:
has anyone been having issues with wifi calling after flashing this kernel? It works, but the other party is getting an echo, which I haven't seen since the early GB roms.

Not sure if the kernel has anything to do with it tho.
[Samsung Galaxy S (4G Model)] psguardian:
If he only supports STOCK Kernels, CUSTOM Kernel DEVs really shouldn't bother supporting his app. Just roll with it AntonX, we can grab SetCpu Here for free anyways.

~psguardian
[Samsung Galaxy S (4G Model)] Warrenforfree:
Im on rc2 now using Voltage Control and it works just fine no reboots what so ever... and for those who are used to have tegrak they can check v1.0b3 since that's works great on tegrak..
[Samsung Galaxy S (4G Model)] nazcalito:
Unless something else is going on, maybe tegrak is set to only work with a set number of intermediate levels and no more. Tegrak works fine with the overclock kernel in RC2,which has two intermediate frequencies.

It should be easy enough to test this by adding one intermediate frequency at a time and seeing at what point tegrak locks up. The test version added three intermediate frequences as far as I know. If this is the only reason why tegrak is locking up, it should be an easy enough fix for tegrak's author. He might react differently if he knew that the fix was something simple.
[Samsung Galaxy S (4G Model)] AntonX:
Here is another TEST ONLY version 1.1rc3.test2 it two flavors.

- Config mods so I can build no OC/UV version.

- Change to VoodooSound that should fix low WiFi Calling microphone level. Who had problems with it please test and report if it's fixed.

Normal OC/UV version:

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

No OC/V version:

http://dl.dropbox.com/u/74713966/sms-T959V-KJ6-antsvx.stdf.v1.1rc3.test2.zip

No OC/UV "stdf" (standard frequencies) version has all the latest features of the normal except there is no overclocking/undervolting at all. You can use Tegrak with it as usual. With the normal version I think Tegrak will not even start anymore.

I will not make a version with limited frequency table for Tergak. I'm going by the guy's "specs" - if he says he doesn't support custom OC/UV kernels, so be it.
[Samsung Galaxy S (4G Model)] John McClane:
Anton

So far so good, with Non OC version and tegrak. :D

No FC's nor reboot. Will update tomorrow to see if there's any difference.

Thanks.
[Samsung Galaxy S (4G Model)] mike-y:
seems like the test kernel has fixed the echo I was getting on wifi calling. good work!

using the normal oc/uv version btw.

EDIT: While there is no more echo, my GF said that it sounded like sometimes I was "talking inside a bathtub".. I'll try and test it more today, to see if it was just a one-time occurrence.
[Samsung Galaxy S (4G Model)] thomas.raines:
This morning I got a "hot boot" reboot (it rebooted to bootanimation). I'm using the test2 NonOC version. This is what I pulled from the log which is moments before the reboot:

05-09 05:23:49.652 E/CurrentReader( 2833): java.io.FileNotFoundException: /sys/class/power_supply/battery/current_now (No such file or directory)
05-09 05:23:49.652 E/CurrentReader( 2833): java.io.FileNotFoundException: /sys/class/power_supply/battery/batt_current (No such file or directory)

I'm on eriks MIUI 0.2.2. I've been on this ROM for a few days now, and this is the first reboot of any sort I have had with this ROM. I flashed the test2 kernel last night.

Hope this helps!

On another note, the vibration seems a bit week on this kernel.
[Samsung Galaxy S (4G Model)] netrace:
How do you do! your kernel in our very popular, but supersu is the English version, the hope can the built-in [en.cn.tw] three language version, I am in this supersu v0.89 provide three languages and su files,In addition the kernel script automatically install always supersu and su files, and replace the new version really inconvenient, the hope can improve, thank you!
[Samsung Galaxy S (4G Model)] AntonX:
thomas.raines,

I'm not sure why it's crashed (what are your OC/UV values if any?), but the battery messages are benign. It's some app (probably toolbar) tries to get battery current statistics, but Samsung battery doesn't supply this. I think current_now and batt_current files have been completely deprecated in recent kernels.

Vibration is a know issue with MIUI and Vibetonz vibrator that Samsung is using.
[Samsung Galaxy S (4G Model)] John McClane:
AntonX

Still on test2, no problem whatsoever. Found out this morning, a kernel wakelock in better battery stats a bit huge. Checked and its for charging. I have the non-OC, using paid Tegrak and desex's UV values.

I have 70% battery right now as writing this post. Running for 7h 30ish minutes, from moderate to light use.

Thanks
[Samsung Galaxy S (4G Model)] AntonX:
Guys, can you edit your post to remove the overquoting of the whole OP?

I can change the initramfs script so it only installs the superuser when it's not present yet, basically during initial rooting. Right now it also checks the timestamp and updates it if newer version is available. Maybe it's a good idea to give the user ability to control the su versions after the initial rooting is done.

Opinions?
[Samsung Galaxy S (4G Model)] netrace:
Good idea, I think of the late users control updated version is more appropriate
[Samsung Galaxy S (4G Model)] stephen_w:
At what point, exactly? If an old/older version is left installed, won't the user get notified an update for SU is available through Google Play? More than likely most of them would update at that point. If I'm skipping an obvious reason for keeping an older version definitely let me know.
[Samsung Galaxy S (4G Model)] AntonX:
Exactly. But now the script is written so anytime I update the superuser file in the initramfs, the script updates it for the user as well. As you can see above it creates problems for international users.

I will remove this logic. The script will only check if there is no 'su' at all for initial rooting and will never update after that.
[Samsung Galaxy S (4G Model)] Bdub220:
I just rooted and flashed a kernel for the first time.. first time poster and I thought my observation might help. I second mike-y's wifi calling experience. Since flashing this kernel (plain ole 1.1 rc2) every time I speak to someone over wifi, they say they can hear themselves echo clearly and loudly... just like back with the old GB roms before KJ6. Not sure this is connected, but its definitely coincidental. Ill try the .test2 and confirm that fixed it.

PS Love my SGS4G, this board and all the work you devs do. Thanks AntonX, cant hardly wait to have this kernel solid.
[Samsung Galaxy S (4G Model)] thomas.raines:
@antonx

I think you are kinda right about the app... I had 3 more reboots this afternoon and was able to pull a better log... Unfortunately, because of the weak vibration, i switched back to an older version of your kernel...

Sent from my BAMF SGH-T959V!
[Samsung Galaxy S (4G Model)] mikhail777:
No issues with the rc2 no OC and great battery life! Keep up the great work!
[Samsung Galaxy S (4G Model)] bhundven:
Btw, gj on your kernel work!

imo, repacking the initramfs is also something custom rom makers can also do. It's not a difficult task, and I'll document a how-to on the wiki.

I'm just one vote, but I like the original logic. Where the su binary is only written if /system/xbin/su does not exist.

The market keeps my apps up to date, and the sterricson's busybox and chainsdd's su apps keep me up to date.

Sent from some other phone... Lulz :D
[Samsung Galaxy S (4G Model)] AntonX:
You are right about the desired behavior, but the original install_su.sh script does exactly the opposite ;) It checks if /system/xbin exists (test -d "/system/xbin"), then checks if 'su' is already there, but then compares the timestamps and forcefully updates if newer 'su' is present in initramfs. I'm removing only this forceful update.
[Samsung Galaxy S (4G Model)] bhundven:
Right on!
[Samsung Galaxy S (4G Model)] itzik2sh:
Hi

I apologize if someone already posted this, also let me know if you encountered this or you want me to try reproducing it with logcat.

While using RC2 kernel with setcpu 2.2.4 both on OndemandX & on SmartassV2 governers 100-1300 scaling, phone app got stuck while I was dialing and I had to reboot the device to end the phone session.

It didn't happen yet on conservative governer yet (now I'm on 200-1200 scaling).
[Samsung Galaxy S (4G Model)] Wodensman:
I don't know what I'm talking about, but I think your problem was setting your minumum freq to 100. No lower than 200 is what I've heard.
[Samsung Galaxy S (4G Model)] AntonX:
Why? 100Mhz is just fine. No need to waste CPU cycles when the phone isn't doing anything.

The only problem with 100Mhz can be that some apps that depend on CPU speed to run smoothly, like media players, would occasionally skip, especially with ondemand-type governors that tend to swing from minimum to maximum. Interactive governors ( smartass2) fix that. If you monitor CPU clock while running a music player, you'll see that with ondemand it constantly swings to max and then drops back to 100. With smartassV2 it stays around 200-600Mhz.

Never notices any locks up when dialing and I'm on smartassV2. Anybody?
[Samsung Galaxy S (4G Model)] Wodensman:
I haven't had anything lock up since using your kernel, and I'm OCed @ 1.3 with min @ 200. However, I use smartassv2, and my phone spends a little over 50% of it's time at max. why is that? I don't play games THAT much. While watching the clock, with nothing running except the SetCPU app that I'm watching, it jumps around everywhere.

---------- Post added at 04:33 PM ---------- Previous post was at 04:32 PM ----------

Also, I can't find the post that I read it on, but I had read that setting it to 100 can make it crash. Something about when it goes to sleep, it throttles down and something, I don't know. I'm not savvy on this.
[Samsung Galaxy S (4G Model)] AntonX:
Depends on the usage. Mine shows a little over 20% on the max today, but I've seen more.

Don't know who gave a crazy idea about crashing at 100MHz. The kernel locks on 800Mhz right before going to sleep anyway.
[Samsung Galaxy S (4G Model)] Theraze:
If you set your voltage too low it can lock up, but itzik2sh didn't say anything about additonal UV changes... But that's the only time I've had lockups with 100. Bump power by 5-10, run it a while longer, and bump it more if it locks again.

If itzik2sh is actually having problems with the default UV settings that AntonX has set, maybe the defaults need to be bumped slightly. If they're custom settings, then everyone else's experience shows that the settings are fine...
[Samsung Galaxy S (4G Model)] Bdub220:
Went to .test2 last night, made over a dozen wifi calls today and no echo issues. No reboots. Only issue I see with an untrained eye is the low vibration. Also, I have no idea if this is kernel related, but before I flash .test2 Google Play would force close on every open, even after a reboot until I uninstalled all updates. No issues with this after flashing .test2 so far.

Otherwise.. I am just pissed I didn't root earlier, the phone is sooo much better with this kernel and all the bs removed.
[Samsung Galaxy S (4G Model)] Warrenforfree:
I just wanted share some info guys.... im on rc2 and no issues WSE, i use Vc clocked 100-1300, ondemand-smartassv2 and i dropped the voltage by 25.. when screen on it stay's at 400-800 when screen off stay's at 100-200 and goes to max when i'm on games... the battery last a day and a half for that light to moderate use, So far so good. i'm sorry if i mess the space for this post... mods are in authority to del. this if necessary.
[Samsung Galaxy S (4G Model)] netrace:
HI ,Don't know can be closed touch screen LED lights when buttons will ?
[Samsung Galaxy S (4G Model)] itzik2sh:
NBA JAM seem to be stuck when launched with any governer with min scaling set as 200. No problem with 100 or 300... weird.

P.S even with conservative governer at 100 to 1200 my device heats noticeably.
[Samsung Galaxy S (4G Model)] Warrenforfree:
Mine works great and smooth... i'm using VCE scaling 100-1300 deadline/SmartassV2 w/o issue..
[Samsung Galaxy S (4G Model)] psguardian:
How far below stock voltage values are we on 1.1rc2?

~psguardian
[Samsung Galaxy S (4G Model)] Wodensman:
It works fine for me when I'm trying to reproduce your settings. However, I have problems with seigecraft. That game is really laggy and stuttering. How would I up my horrible fps on that game??
[Samsung Galaxy S (4G Model)] xaocon:
Ant idea how to set the max digital volume to 14 in voodoo sound?
[Samsung Galaxy S (4G Model)] AntonX:
It's controlled by the app, kernel has nothing to do with that. You should not need it though, it should sound fine on maximum digital amplitude. Is it distorting? Do you use some equalizer set on high gains? Try disabling it, maybe it miscalculates and goes into distortion.
[Samsung Galaxy S (4G Model)] stephen_w:
I am on rc3 test 2 (OC/UV) & was using SetCPU with a minimum of 200, a max of 1300, and the smartassv2 scheduler. This is the first of these kernels where I installed & used SetCPU, so I can't say if the following problem exists in the earlier versions though I am willing to try it if it helps.

I noticed over the last few days that notifications were not working most of the time. I was having to go into my apps to see if there were triggers that should set off the notification (new mail, my turn in a game, etc.). I also noticed that the screen brightness would jump up pretty high all by itself even though I have it turned all of the way down, automatic brightness is off, and power saving mode is not checked. I uninstalled SetCPU earlier tonight and, since that time, things seem to be working normally again.

Anyone else notice this behavior?
[Samsung Galaxy S (4G Model)] 95Z28:
I'm on rc2 and this is my first time using setcpu also, but I'm not having any problems with notifications, screen brightness, or anything. I'm running min 100 max 1200 with smartass v2 and my UV settings.
[Samsung Galaxy S (4G Model)] AntonX:
Updated OP to 1.1.0. Didn't see anything wrong with it over last few days, so let's call it a stable release and go from here.

Small change to VoodooSound to remove ADC oversampling when doing VOIP and recognition. Probably really unnecessary, just a little paranoia.

Looked at Vibetonz again, but didn't find anything wrong. Looks like MIUI knows about it, tries to use it, but does it incorrectly.

Removed forced superuser update.

If you used a OC/UV version prior to a test release that introduced extra frequencies (600, 900, 1100), review and update your voltage table!
[Samsung Galaxy S (4G Model)] itzik2sh:
I find Voltage control working much better than setcpu for me.You can set I/O scheduler and device less heats.

Thanks Anton for keeping up adding features.
[Samsung Galaxy S (4G Model)] m4xm4n:
There's literally no benefit to using vibetonz at all. Just switch to using aries-vibrator and you'll have no issues.
[Samsung Galaxy S (4G Model)] AntonX:
I know it doesn't do much, but for some reason aries vibrator does not work with the stock ROM. I tried making few quick changes to aries-vibrator.c, but nothing helped. Looks some service in stock ROM (TouchSense?) is tied directly to ImmVibeSPI instead of standard vibrator functionality. In the logcat is this:

W/System.err( 361): java.lang.RuntimeException: VIBE_E_NOT_INITIALIZED
W/System.err( 361):	at com.immersion.android.ImmVibe.SetDevicePropertyInt32(Native Method)
W/System.err( 361):	at com.immersion.android.ImmVibe.setDevicePropertyInt32(ImmVibe.java:251)
W/System.err( 361):	at com.android.server.VibratorService.setVibeStrength(VibratorService.java:586)
W/System.err( 361):	at com.android.server.VibratorService.vibrateMagnitude(VibratorService.java:254)
W/System.err( 361):	at android.os.IVibratorService$Stub.onTransact(IVibratorService.java:66)

Whoever wants to recompile for MIUI, all you need to do is disable CONFIG_VIBETONZ in the config file and and remove vibrator.ko from initramfs.
[Samsung Galaxy S (4G Model)] vwgtiturbo1:
I haven't been on in a while but something I realized in the last 2 kernels which maybe not even a kernel issue I think but with setcpu. Whenever I set my governor to smartassv2 it shows my governor to be ondemand.. I then have to switch to another governor and then switch back to smartassv2 to set it but after I reboot and I go to setcpu its switches back to ondemand on boot and not smartassv2 .. Anyone come across this?
[Samsung Galaxy S (4G Model)] xaocon:
setcpu has a safe mode that acts like that. Check the menu in setcpu for more info.
[Samsung Galaxy S (4G Model)] m0bstr:
What's the best setting for performance and battery life? Right now I have smartassv2 and set to deadline
[Samsung Galaxy S (4G Model)] vwgtiturbo1:
That's what I am using :) running like butter.. The only thing is when I reboot setcpu sets ondemand on boot instead of smartassv2.
[Samsung Galaxy S (4G Model)] xaocon:
I use sio for io. Like it better than deadline. 100 to 1300 all under volted by 100 works best for me.
[Samsung Galaxy S (4G Model)] xaocon:
I looked around and am not using an eq in any of the apps. I've always gotten distortion at the highest level. Just wasn't a problem as much when I could control that volume directly.
[Samsung Galaxy S (4G Model)] ipaq_101:
Using voltage control, 100/1300. Deadline/smartass2, undervolting by -25 on all.... Result smooth as hell, no crashes, insane battery life..About 32 hours
[Samsung Galaxy S (4G Model)] Wodensman:
Before I started using this kernel, my battery life was.... ugh. I could have a full charge when I leave for work, and 8 hours later it would be almost half gone without hardly any usage. Now, I can go to work and play games on my phone whenever I have the free time, and 8 hours later, I was still at 90%!!! But, this is also with AS14.1. Using this kernel, and AS has done soooo much for this phone. Thank you so much AntonX!
[Samsung Galaxy S (4G Model)] Jerry D:
What ROM are you on?
[Samsung Galaxy S (4G Model)] Wodensman:
Val Final
[Samsung Galaxy S (4G Model)] HB66:
How do you chanel the i/o
[Samsung Galaxy S (4G Model)] eollie:
What Oc app are you using?
[Samsung Galaxy S (4G Model)] 95Z28:
If you're using set cpu you don't. You can change it with voltage control though.

Thanks itzik2sh for pointing that out. I use both, voltage control simply to change the I/O scheduler to sio, setcpu because I like the widget so I can leave my phone at 1ghz and quickly change to 1.2 before starting a cpu intense game.
[Samsung Galaxy S (4G Model)] ipaq_101:
Just sharing and sorry if it's in the wrong place and has been posted before, but as we are talking a lot in this thread about Governors and I/O Schedulers, I found this thread useful as I didn't know about any of this stuff before. Hopefully it can help people out and prevent people from asking what is the best one or the best combo, read it and you will figure out its all based on preference:

http://xdaforums.com/showthread.php?t=1369817
[Samsung Galaxy S (4G Model)] nazcalito:
The update to tegrak overclock fixes the problem with tegrak locking up when the newest OC kernel is installed. Now tegrak simply gives an error message. So the guy did listen to Antonx about making his program more compatible since I guess not working is better than locking up the phone.