yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] zacharias.maladroit:
Hi existz,

I don't know which variant of the smartass governor you exactly used but from the initial smartass governor commit

there were lots of additional patches (especially the ones from netarchy)

that should help with the downscaling and higher frequencies

so in total there should be like 3 variants of the smartass governor in my repo alone:

android_kernel_samsung_aries/commits/governors

if the commits confuse you - just take the final resulting cpufreq_smartass.c in drivers/cpufreq and you should have a (hopefully) working variant

hope that helps :)

and thanks for your message on github & adding to the repo !

edit:

branch on the talon kernel (still based on the 0.2.x back then)

linux_gt-i9000-gb/commits/governors
[Galaxy S I9000 Android Development] existz:
Well, what the problem is, is that with an all in one OC (the up to 1.6ghz version), it seems to work fine, then with my non-oc and 1200 versions (100-200-400-800-1000 and then 1200), it scales perferctly fine...but with my 1400/1440 versions (100-200-400-800-1000-1400/1440) it will not come off of 1400/1440... I dont know if its just to big of a jump from 1000-1400 thats messing it up or what.. Havent really looked into it much but with it on the 1000/1200 versoins compared to Ondemand, i still decided to stick with ondemand, IMO its been the most reliable, atleast on Talon... But ill check into it sometime and see if i can get i going with the new 1400/1440 versions, and then might start tweaking it some
[Galaxy S I9000 Android Development] Bo$s:
Are apps like CWM and Tweaks from CF-Root kernel are compatible with Talon 0.3.1 or not?
[Galaxy S I9000 Android Development] existz:
No, not compatible with latest released 0.2.2, I dont use CFs initramfs anymore, we use a voodoo based initramfs.. most of those tweaks did not work well with Talon or better settings are already applied by default in the kernel

Sent from my SGH-I897
[Galaxy S I9000 Android Development] Bo$s:
Thanks :) So I will remove them ;)
[Galaxy S I9000 Android Development] rlorange:
@exitz I'm still not clear as to why you hesitate to add 1200 in with the 1400 version to bridge that big scaling jump. Just make it clear to everyone that you can't use that version and try to limit it to 1200 as it will still spike to 1400 with some apps.

**Simply Honey3.8, Talon 0.3.1 t5 kernel1.4ghz**
[Galaxy S I9000 Android Development] zacharias.maladroit:
would following

with 1400+1440 MHz kernels help ?

I know that it could be done more elegant but this one should cover each step

if (cpu_load < min_cpu_load) {
//if the current frequency is below 1.0ghz, everything is 200mhz steps
if(policy->cur <= 1000000 && policy->cur >= 400000) {
/* catch the extra 200mhz gap between 400 and 800 when scaling down -netarchy */
if(policy->cur == 800000) {
new_freq = policy->cur - 400000;
return new_freq;
}
else if(policy->cur == 200000) {
/* 100 MHz gap between 100 and 200 MHz */
new_freq = policy->cur - 100000;
return new_freq;
}
else {
new_freq = policy->cur - 200000;
return new_freq;
}
}
//above 1.0ghz though, there is only one 400mhz step
if(policy->cur == 1000000) {
new_freq = policy->cur - 400000;
return new_freq;
}
/* catch the extra 40mhz gap between 1.4 GHz and 1.44 GHz when scaling down -zacharias.maladroit */
else {
new_freq = policy->cur - 40000;
return new_freq;
}
}
if (cpu_load > max_cpu_load) {
if(policy->cur < 1000000 && policy->cur > 200000) {
/* catch the gap between 400 and 800 when scaling up -netarchy */
if(policy->cur == 400000) {
new_freq = policy->cur + 400000;
return new_freq;
}
/* 400 MHz step above 1 GHz */
else if(policy->cur == 1000000) {
new_freq = policy->cur + 400000;
return new_freq;
}
/* 40 MHz step above 1.4 GHz */
else if(policy->cur == 1400000) {
new_freq = policy->cur + 40000;
return new_freq;
}
else {
new_freq = policy->cur + 200000;
return new_freq;
}
}
else {
new_freq = policy->cur + 100000;
return new_freq;
}
[Galaxy S I9000 Android Development] existz:
A little note about upcoming 0.3.1, ... I will more than likely make it a CWM3 flashable zip this time, but during the flash im making it where it wipes cache and dalvik cache, plus remove any kernel related scripts (Voltage settings, any scripts that sets the scheduler, ramhacks, systemtweaks or screenstate_scaling scripts).. Im doing it this way to ensure everything that would conflict with the new Talon is removed ...should make things a cleaner install and prevent any issues... So first boot after flashing will take longer than normal...so don't freak out.. also if your running a custom bootanimation, it will only show a black screen during boot.. Ill make note of this in the OP when I release it, but wanted to go ahead and spread the word so there's not 100 post from impatient people saying it doesn't boot or is stuck during boot..etc... Again, this will only happen on the first boot after flashing.. Im going to probably get 0.3.1 up tomorrow if everything goes as planned
[Galaxy S I9000 Android Development] corgar:
in 0.2.2 init.d script are working? got some script but doesn't seem they are executed.
[Galaxy S I9000 Android Development] Darcia:
Yes it works ^^.

For check it you could use voltage control for set oc at boot and check after reboot if you use oc frequency. Or you could put Juwe's script in, reboot and check with galaxy tuner if you have Juwe's values. ( litle hard way, could exist a shorter way)

But even with old kernel dirty files in a system, I don't know if you really couldn't have init.d supported with Talon.
[Galaxy S I9000 Android Development] corgar:
i'm checking sdcard values for cache but are still the same.
[Galaxy S I9000 Android Development] Darcia:
In a previous page of this thread, someone share the link to a kernel cleaner script flashable by CWM. Use it and reflash Talon, that should work after this. ;)

If not.. You should make a totally clean install' .
[Galaxy S I9000 Android Development] paratox:
someone could pm me T8 or the last test version 1200MHz? thanks! :)
[Galaxy S I9000 Android Development] morphjk:
Um I might have missed something but in recovery I can't see a voodoo section to enable ext4. This is using the JVH 0.2.1 kernel.

Can someone tell me where I can find it?
[Galaxy S I9000 Android Development] Darcia:
In 0.2.1 you should convert your system in ext4 by Chainfire's app' ;)
[Galaxy S I9000 Android Development] morphjk:
Oh okay. I just saw this in the first post:

Enable/Disable Voodoo Lagfix in CWM->Voodoo

I now see that is for 2.2
[Galaxy S I9000 Android Development] existz:
Yea im including something very similar to the kernel cleaning script in the next release, going to make it a cwm3 zip so it can wipe on install... this should prevent any conflicts or issues

Sent from my SGH-I897
[Galaxy S I9000 Android Development] jaiiscool:
My compass has an error of exactly 180°. Does any1 else face this issue?
[Galaxy S I9000 Android Development] existz:
0.3.1 coming up soon, just released it for Captivate, should have I9000 up soon

Sent from my SGH-I897
[Galaxy S I9000 Android Development] jetcz:
yes, on galaxian kernel compass works fine
[Galaxy S I9000 Android Development] jaiiscool:
Hey existz, any fix for this?

Thanks man!
[Galaxy S I9000 Android Development] RichMD:
Thanks eXistz! I just flashed the stable 0.3.1 (no overclock) via CWM. It's nice to have the CWM capability and I don't use overclocking so this is great. We appreciate all the hard work - I've seen how many test builds you go through to get a stable release.
[Galaxy S I9000 Android Development] existz:
First make sure your flashing the I9000 version (not captivate), 2nd, if it still happens on I9000 version then its probably something sticking from the captivate config...ill look into it, I can't fully test everything since I don't have an i9000, but ill check into it

Sent from my SGH-I897
[Galaxy S I9000 Android Development] ooohhh2:
This is a really great news. I'm waiting eagerly. But i have one question, i saw the captivate thread and it said that you will need the app control freak to change gpu freq, but it just works with captivate, right? Is there any alternative for galaxy s.
[Galaxy S I9000 Android Development] existz:
Actually Control Freak will work with I9000 as well, ill post a link to it once i get 0.3.1 up....feeding the young one right now, so might be a few, but ill get it up shortly...also ill look into the compass issue, not sure if ill get it in this release, but i should the next.. Already got 0.3.1 compiled and ready to go , just need to upload and post them
[Galaxy S I9000 Android Development] jaiiscool:
Thanks existz. I am using the i9000 version for sure. I am certain tht u will work out the issue. U r the best.

Cant wait to get my hands on 0.3.1
[Galaxy S I9000 Android Development] The Undertakerr:
Same here Existz...

Can't wait to get my hands on version 0.3.1.

I LOVE your kernel and your support. Your kernel is in my Rom(Holland)

MANY Dutch people are using it and love the kernel!!

Version 0.0.2R2 is allready perfect in my opinion, allmost as good as it can possibly get! So I'm very curious!

Thanks a lot mate!!

Ps: Also a lot of thanks from my theming man, who you helped out a few days ago with the bootanimations!!
[Galaxy S I9000 Android Development] existz:
UPDATE

TalonDEV-0.3.1

added sched_autogroup patch

added configurable gpu oc (for future use)

fix BLN not working for some users

introduce non-oc version of talon

independent oc versions (1200/1400/1440)

compile wifi as Os instead of O2

set wlan power on delay back to 80ms

use samsung bootanim when no custom zip found

NOTE

Now CWM flashable!...Zip will wipe cache and dalvik cache during flash, also removes any kernel related scripts (voltage settings, ramhack scripts, scheduler scripts..etc..etc..) so first boot WILL TAKE LONGER THAN NORMAL and if your using custom bootanimation, screen MAY BE BLACK ON FIRST BOOT...

You can control GPU OC with Shane87s app "Control Freak" ...remember its the initial support for GPU OC, so it may/may not fully work, may/may not have bugs, this is expected..its only the initial support for it

Download Control Freak Here: http://xdaforums.com/showthread.php?t=1072403

Since I already had 0.3.1 compiled and ready to go, ill have to fix the compass issue in the next release..
[Galaxy S I9000 Android Development] komoornik:
Would love to test it now.

But it's downloading so slow.
[Galaxy S I9000 Android Development] Crimsonthunder:
Can't wait to test it! Thanks for your work!
[Galaxy S I9000 Android Development] existz:
Dont know if its getting slammed or what since captivate and i9000 versions were both just released, but give me a few min and ill get mirrors up
[Galaxy S I9000 Android Development] Crimsonthunder:
Yes the download ist damn slow at the moment..
[Galaxy S I9000 Android Development] Tababaer:
is it possible to flash it over a JVH Firmware or do i need to upgrade ?
[Galaxy S I9000 Android Development] zenosteam:
existz , thanks for these multi version kernel so i want to know if ramhack is jew's ram script ,also if i understand it's not necessary to use any task killer or ram optimizer with the new 0.3.1, i, control freak there is gpu oc i don' know what it is it possible to have a little explanation, must i mont systeme in cwm to add some zip add on ... finally keep the good work

nb: if these questions are asked before i am sorry
[Galaxy S I9000 Android Development] Tatsuya79:
I can't select 1300MHz on the 1400 version, it's just 1000MHz or 1400MHz, nothing in between (using voltage control app).

But thanks for your work! :)

...still testing
[Galaxy S I9000 Android Development] hackeron:
Thx existz and the co-devs for awsome work !! Much appreciated.
[Galaxy S I9000 Android Development] existz:
MIRRORS

TalonDEV 0.3.1 340MB No-OC CWM3

TalonDEV 0.3.1 340MB 1200MHZ CWM3

TalonDEV 0.3.1 340MB 1400MHZ CWM3

TalonDEV 0.3.1 340MB 1440MHZ CWM3
[Galaxy S I9000 Android Development] existz:
Yea thats the way its suppose to be
[Galaxy S I9000 Android Development] asicman:
Is this the first kernel with GPU OC? What do you hope to accomplish with GPU OC? Just higher FPS? Are there any benchmarks that show GPU OC actually affecting anything?
[Galaxy S I9000 Android Development] existz:
You probably wont see much difference with benchmarks..etc.. the fps cap is still locked at 56fps...(no i wont unlock it, causes colors to be washed out at low brightness, turning blacks to brownish/redish)... but it will help with other gpu accelerated task, such as browser rendering..etc..alot of things are actually gpu accelerated..so should make overall UI,..etc more smoother/quicker
[Galaxy S I9000 Android Development] petsasj:
I OC'ed the GPU by 25mhz @1200 and 1000 mhz. Have others achieved a stable higher OC in the GPU?
[Galaxy S I9000 Android Development] Cy4n1d3:
I had to recompile the 1200 mhz version with voltage increased to 1300 + internal voltage of 1125. 1275 / 1300 + internal voltage of 1100 are not stable for me :\

Anyone else having the problem of pimp my cpu not showing 'sio' scheduler?

Other than that: great work, keep it up!
[Galaxy S I9000 Android Development] existz:
The SGX540 is actually clocked at 400MHZ, samsung has underclocked it by quite a bit (200MHZ), theres actually quite a few other phones out there with the same cpu/gpu (ARMv7/SGX540) that are clocked at 380/400.. Im currently running 350MHZ (150mhz OC) with 1200 version. Different steps will like different gpu oc..for example, 1200 might like 350, but 1400 might only like 280... so its going to vary from frequency to frequency and from phone to phone... this is just the initial support, alot of things are still left to be figured out and learned, but it looks like 350-400 on certain frequencies and phones works ok (of course it all varies on the phone).. so for all we know, 400mhz might be stable for most (since its actually the max clock for sgx540 gpu).. so we havent really gotten into actually overclocking the gpu much yet

But like i mentioned above, the fps is still locked at 56fps, so your not going to see higher fps or that much higher in benchmarks.. But in actual real world situations (browser rendering..the UI..etc) will actually benefit from higher gpu clock

But also remember that max is still only a 200mhz oc, so drastic improvements are not expected, its not that big of an OC...it should give a subtle improvement with overall experience ...once more is learned about the gpu and how it OCs, higher clocks might be added.
[Galaxy S I9000 Android Development] st4rk:
Just wanted to say thx for the new version, 1.4ghz is perfect for me with tw4, clock to 1.0ghz normally then jump to 1.4ghz when necessary, or when tw4 feels like it..lol. Will send you a beer soon for all your hard work ;-)
[Galaxy S I9000 Android Development] komoornik:
I don't really get all the things in ram.conf.

Can anyone tell me which preset should I choose to kill apps more often?

Coz with deafult preset 7 I'm hitting 40 MB of free RAM and i hate it - my phone really starts to lagg.
[Galaxy S I9000 Android Development] existz:
edit..removed for now...will get different settings up later
[Galaxy S I9000 Android Development] Timo Schmidt:
Hi there!

What's the difference between the nooc version and the 1,2 GHz Version of Talon? Is the only difference that 1,2 ghz can't be selected in Control Freak or are there other changes (like RAM Timings etc) under the hood? :D
[Galaxy S I9000 Android Development] existz:
No-OC is as it says, is a non-oc version (max clock is only stock 1ghz), the 1200 version is up to 1.2ghz .. and so on...nothing different besides the max clock.
[Galaxy S I9000 Android Development] tomeks:
cpu is still at 800mhz when plaing music with stock player

the same setup with semaphore and the cpu staying at 100mhz

except that, great and fast kernel, thank you for your work

sent from my GalaxyS@JVP/Semaphore@1,2mhz
[Galaxy S I9000 Android Development] zacharias.maladroit:
everyone has been complaining about the frequency

BUT:

you compared the battery consumption for a longer period - say 2-3 hours of playback and compared those 2 kernels ?

how much does it really consume in those "800 MHz"

THAT would be interesting to know :)

because samsung's kernel offers a ULP (ultra low power / DIDLE ?) state and some accelerated codecs that let it consume very low amounts of energy

by chance the frequency at which the processor enters those states is 800 MHz

like I already wrote (on github ?) it might be a aesthetic/cosmetic issue that it doesn't display the lower frequency

anyone willing to do this kind of testing ? (different kernels, mp3 playback -> talon showing e.g. 800 MHz, the other 100 or 200 MHz; running that way for several hours and noting down the battery consumption;

this afaik of course would take several days since battery would need to be calibrated and run on that kernel for a longer time to exclude any calibration/battery related errors in readout)

(this post isn't meant to be offensive or appear snobbish)
[Galaxy S I9000 Android Development] existz:
Compass issue seems to be fixed, will be in the next release
[Galaxy S I9000 Android Development] Timo Schmidt:
Hmmm...

I have a strange problem. I cant convert back from ext4 to rfs...

I also cant convert the rfs system partition to ext4.

With Speedmod conversion in both directions is fine. Someone has a solution for this problem?

Thanks in advance.

Timo
[Galaxy S I9000 Android Development] existz:
If your battery is below a certain level voodoo will not convert, or if system is full it wont convert either...voodoo checks these things before conversion...check the logs in /sdcard/voodoo/ ... im not sure on the exact battery percentage, but over 50% it *should* convert , again i dont know the exact percentage

Sent from my SGH-I897
[Galaxy S I9000 Android Development] The Undertakerr:
Thank you very much for this kernel Existz!

It feels very stable, more stable then any other kernel!!

One question though, do you really advice against using Juwe's ramscript with your kernel? Or is it ok to use it?

I know it is deleted by your script and I'm sure that's with a reason:p, but will it give problems when I add it again?

Thanks again for the great kernel!:D
[Galaxy S I9000 Android Development] The Undertakerr:
No problems here with converting back to RFS...

It's the voodoo conversion system; a save&good one.

Just converted back for testing and no problem at all...
[Galaxy S I9000 Android Development] existz:
We actually advise against it...there is actually 2 places that lmk settings are set, (1, the kernel settings, which is what most scripts, like Juwe's sets...and 2) in the userspace....so the problem is, when just using those scripts, it just sets it in the kernel settings, so theres actually 2 different sets of lmk settings set, and could cause conflicts... But the settings in Talon are configured for Talon and ZRAM, Juwe's script may work great on other kernels, but Talon operates memory management differently than other kernels, so it may not work as good as Talons settings... But if your wanting to use his settings, then the best way to do it is add it as a preset in /etc/ram.conf .. You can edit preset 0, its for custom user profiles, and then just set PRESET=0 ... But just using scripts may cause conflicts, and Talon/ZRAM works differently than other kernels, so its just best to use kernel defaults..Kodos96 is always working on improving the LMK settings
[Galaxy S I9000 Android Development] The Undertakerr:
Thanks for the answer!!

That's what I thought allready, they may conflict with your settings. You probably know what's best settings for your kernel.

But are all the settings of juwe's script covered by settings in the kernel, or is there something usefull left in his script I can still use?

If you say everything in the script is covered by your kernel, I will not use the script anymore. Every setting in juwe's script you have in the kernel?(optimised)

Thanks man!:-))
[Galaxy S I9000 Android Development] existz:
well, some of it is...not all of it...but again, it will probably not work so good on Talon as compared to other kernels... Some of those VM/Memory tweaks could work against Talon/ZRAM, compared against either non-swap kernels or even kernels with just swap enabled. Which there is some work being done with Talon regarding those type of settings, tweaking them to work well with ZRAM
[Galaxy S I9000 Android Development] Tatsuya79:
Stock player is just using 100~200MHz on my phone with Talon 0.3.1 1400.

@Existz: is it too much work to make a 1300MHz version or just some values to change without breaking stuff?
[Galaxy S I9000 Android Development] oswade:
OMG Finally got wifi to work!!! (on 3.1).

I had to manually set my IP settings in wifi settings/advanced.

Hope this helps the other people having trouble with wifi (stock jvp people?).
[Galaxy S I9000 Android Development] existz:
I might do a 1300 version in the close future...i actually didnt plan on doing a 1440 version, but alot of my testers actually requested one, so i was compiling a 1440 vesion anyways, so i went ahead and release it...initially i was just going to do a 1200 and 1400 .. But it shouldnt be to much trouble for me to do a 1300.. but only thing it will be (100-200-400-800-1000-1300)... But ill see what i can do and "might" include one in next release..it all just depends on what we are working on at the time, if theres alot of down time for me to mess around, ill do it..but sometimes we have a few bug fixes that takes up most of our time and only concentrate on that..but ill see how it goes
[Galaxy S I9000 Android Development] mab71:
hi existz!!! i would like to use your kernel, but i need some clarification...

i'm on this rom now http://xdaforums.com/showthread.php?t=1133395

and would need to know whether its compatible with your kernel, cos its using darkyys ram hack. thanks....
[Galaxy S I9000 Android Development] existz:
Yea it should work fine, during install of Talon, it should wipe the ramhack script, if it doesnt, then you can use something like Astro or Root Explorer and go to /etc/init.d/ and remove the ramhack script, and i also recommend removing the sdcard tweak script as well...but the sdcard script is up to you, but i HIGHLY recommend getting rid of the ramhack script
[Galaxy S I9000 Android Development] mab71:
thanks!! theres also a S99complete file in the same folder...should i remove it too??...and also since im using voodoo lagfix and on ext 4, i dont have to cconvert before installing right?
[Galaxy S I9000 Android Development] existz:
That one is fine...just the ramhack script conflicts with Talon, and could give negative results, our LMK settings are highly tweaked for ZRAM/Talon,..plus the script can cause other issues, because its only setting it for the kernel setting (the userspace values are not getting changed), so when using those scripts, its setting 2 different lmk settings in 2 different places, which can cause issues... if you want to use different LMK settings in Talon, you can edit the file /etc/ram.conf , you can edit the #0 preset, and then just set PRESET=0 and reboot...that way it sets it in both places..

You should be fine with ext4, but remember that the Talon zip wipes cache and dalvik cache, so it will take longer on the first boot...
[Galaxy S I9000 Android Development] mab71:
i cant thank you enough!!! keep up the good work!!:)
[Galaxy S I9000 Android Development] jaiiscool:
Thanks a lot mate!
[Galaxy S I9000 Android Development] existz:
That one was actually my fault, I had left it in the config for how the captivate is setup, and never changed it back when I started doing i9000 builds... I apologize for this...but will be fixed in next release

Sent from my SGH-I897