yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] suntzu123:
Ok... So what I can see the phone ile like 50% of the time 100MHz and 50% of the time at 200MHz, when is IDLE.

It is big difference. 800mV vs 875mV for like 30% of the time (60% of the time my phone is IDLE 50% of 60% is 30%).

I want to force my phone to stay at 100MHz as long as I can. So when operation need more power and CPU is used at 75% it go up to 200MHz. It like all the time -it go to 200 after one second swich back to 100MHz. If I could change this limit to 95% it would be great. So this is the problem.

I also increase Sampling rate to 1,5 second... So even it is at 100% for 0,5 second it won't swich to 200MHz. But problem is Threshold.

Ondemand scaling got setup up_thershold at 95%, by default, and I can controll it. But conservative is I think better, and I can set down thershold.

Ondemand hang up my phone... I burn my CPU at 100, 200MHz... with rock player, stability test, SetCPU it all pass (like 30minutes of testing each one).... So my Voltage are stable. But when screen go off I can't turned it on. The fun thing is here that I can still make a Call to myself by another phone ( I can't hear the ringtones, screen is still off and phone look like dead)

What I can achive Nvidia said by simple image

Why our phone have to be running at 200MHz when is IDLE and we don't using it. If threshold+sampling rate would be set up like I said it also would be much lower frequency when we are browsing Internet.... Of course slower too, but if page is loading 10 second or 11 seconds I do not care.

---------------------------------------------

Why I'm doing it? because profiles suck. When someone call you and you set up scaling 100-100 when screen is off is like hell to answer.... And If I setup scaling less than xMHz -<800MHz(lees then 800) I got dead phone when screen go off. So scaling 100-100 not working.
[Galaxy S I9000 Android Development] android53:
Set it to 100-800 to fix the sleep death.

Or better yet uninstall setcpu as there is nothing wrong with how the phone currently controls cpu speed
[Galaxy S I9000 Android Development] mystik.:
should I disable the lagfix before the update?
[Galaxy S I9000 Android Development] IntExCZ:
Maybe the CPU is on 200Mhz due to load which is about 10% (with maximum 30% peak) used by "system" and "System Processes" when idle.

Try to look yourself by monitoring in System Panel app....
[Galaxy S I9000 Android Development] laststufo:
Mine in idle do not go over 3%
[Galaxy S I9000 Android Development] IntExCZ:
The "top" command in console shows that most of CPU usage is consumed by "system_server" process. Google says that it could be caused by "Use wireless networks" under "My location sources" section.

I switched it off and will see what happends...
[Galaxy S I9000 Android Development] suntzu123:
I wrote it, so nothing new. But tell me how to set threshold to 90% at conservative.
[Galaxy S I9000 Android Development] CampGareth:
Just a quick report from the field, when playing videos with kernel 4_7_3 and the stock video player sometimes the screen frequency scaling kicks in and dims the display, this is of course undesirable. Been changing the cpu speed at which screen frequency scaling kicks in but if I put it low enough for the video player then the display seemingly randomly lights up then dims again while sat on my desk idling.

Might be time to change tactic, disable display dimming when video players (or maybe the hardware decoder) are running? Give the user an app to choose which programs to disable it for?

Other than that great kernel, ultra smooth so thank you!
[Galaxy S I9000 Android Development] jimmy72:
screen flicking when the cpu is scaling

Hello Lastufo, very great kernel !

But i got screen " flicking " ( the screen light is changing when the cpu is scaling) even i set manually the brightness, do you have a solution please?

Thank you

Jim from france
[Galaxy S I9000 Android Development] layercake87:
i have also the same problem and it is indeed very annoying, even more as i'm used to watch everyday a film on my galaxy :-(

would be very happy if that could be fixed :-)
[Galaxy S I9000 Android Development] vukandric:
+1. Other than that, everything is great! ;)

Sent from my Galaxy S powered by VA GREEN
[Galaxy S I9000 Android Development] FuryriderX:
The SetCPU problem lies in the kernel, somehow.

I just flashed to speedmod K12T and was able to adjust the conservative governor settings slightly, but still it wouldn't save everything. Even modifying the sysfs files by hand did not help.

Is it something that needs to be unlocked/made settable in order for setcpu to adjust these values and for them to be saved permanently?

Allowing these values to be modified and making them stick would be really helpful in saving some battery - especially for us overclocked users! Please add this feature??

EDIT: Or, if they cant be made user-modifiable for some reason, could they be set by default to values that are more reasonable?

For example:

Up Threshold - 95%

Down Threshold - 80%

Freq Step - 5%

Currently the settings are, by default:

Up Threshold - 70%

Down Threshold - 30%

Freq Step - -1% (not even sure why this is functional!)
[Galaxy S I9000 Android Development] jeebspawnshop:
SetCPU is notorious for making systems unstable, and basically for not ever functioning correctly to begin with.

So if you guys wanna use that app, don't ask laststufo to fix something that he didn't screw up in the first place.
[Galaxy S I9000 Android Development] FuryriderX:
I didn't mean to imply that he 'broke' something, for all i know it could just be a tiny tweak that allows this. I have used his kernel for quite a while and i like it alot!

Alright, well, that being said - even if I am unable to use setcpu as a frontend, I should still be able to tweak the governor via the sysfs files by hand - i am able to do so with the settings files for VSF, and the changes stick.

The only reason why i bring it up here and not in an email to the developer of setCPU is that i see differences in the (conservative) governor setup between kernels (hardcore's and laststufo's) - so it IS possible to change the values. I think it would be cool if the possibility exists to tweak the governor to my own liking, setCPU or not.

EDIT: Tried 'CPU tuner' - same deal, it allows for adjustments of the governor - but the settings do not take effect, they stick at 70% up, 30% down. Think i will use CPU tuner from now on though, it seems a bit more full featured than setCPU. This shows that it isn't the app that prevents the adjustments, it's something else.
[Galaxy S I9000 Android Development] jeebspawnshop:
Well, now that I've read your fuller explanation, I understand what you mean.

In such a case, perhaps it is some settings in the kernel that override the app settings... or something.

Just wanted to say that.

:D
[Galaxy S I9000 Android Development] laststufo:
The real problem is that governors are heavly customize inside samsung kernel and these parameters are not customizable
[Galaxy S I9000 Android Development] FuryriderX:
Stupid samsung, messing up all our fun. That's probably why the 'ondemand' governor doesn't work very well at all. Well if anyone can solve the issues, its the dev's on xda! Thanks for taking note!
[Galaxy S I9000 Android Development] mazroui:
hey laststufo

could u pls have a look into a lagfix fix next version if possible ?

1. when choosing ext2, it automatically becomes ext3 and upon a restart it requests a new conversion everytime (from ext3 to ext2)

2. didnt bother with ext3 from what i read about it (being no good when compared to ext2 and ext4)

3. when choosing ext4, all is good(except for the market 30mb download fix)

4. when choosing jfs, all is good (except for when the phone starts it looses all the ringtones/notification tones)(empty list)

only option then is ext4, followed by jfs (if u wanna change notification tones on every boot) followed by rfs being factory setting
[Galaxy S I9000 Android Development] suntzu123:
Now I can see it.... But people say they choose Hardcore kernel because better battery time. I download Hardcore to see threshold values and guess what?

up threshold set at 80%

down threshold set at (I think) 50%.

.... Be better and set in next your kernel up to 95% up threshold, and down threshold I think 60% (think 40% would be better-> long story)...

On demand scaling is set at 95% up threshold and I can't see any difference in performance than conservative set at 70%.

But when I run system panel I see that my CPU is all the time 100MHz when IDLE, at conservative is going crazy.
[Galaxy S I9000 Android Development] laststufo:
1 I'll take a look

2 OK

3/4 Problems there's only if you convert system fs ? right ?
[Galaxy S I9000 Android Development] mazroui:
So u mean the problem occurs due to /system being converted away from rfs?

My /system is converted to ext4.

Currently Lagfixed to ext4,ext4,ext4,false,false,false,false

I would love to battery test ext2 but can't right now. Will convert /system back to rfs to test if it affects the process.

That market problem is due to 4 mb from cache is being used when converted to ext4

As for jfs, Will test if /system is causing it

Never tested with /system on default rfs
[Galaxy S I9000 Android Development] laststufo:
Version 4_7_4 is OUT !!!

Version 4_7_4 (2011-02-02)

- Fix the ext2 lagfix bug

- Optimal conservative governor settings (save a lot of battery)

- VSF changes :

MFC : When you see a video VSF will be disabled

Camera : When you use Camera VSF will be disabled

JPEG Decode/Encode : When you Encode Decode a Jpeg VSF will be disabled​
[Galaxy S I9000 Android Development] mazroui:
sweeeeeeeeeeeeeeeeeeeeeeeeet

^_^ that was UBER fast

downloading....

Thanx a lot bro
[Galaxy S I9000 Android Development] eliazu:
great!! thanx!

should i disable setCPU with this new version?
[Galaxy S I9000 Android Development] klau1:
just install overtop of 4.68 using normal procedure? any special instructions? no need to wipe or uninstall anything ie lagfixes ?
[Galaxy S I9000 Android Development] laststufo:
Yes normal one.. None particular
[Galaxy S I9000 Android Development] laststufo:
I think to give it a try !
[Galaxy S I9000 Android Development] mazroui:
can i say something regarding battery......

ext2 + all this goodness + UV = crazy good battery time, actually ever since flash of kernal @ 31% the screen was on and restoring/installing/configuring

now its 21% ....... i seriously should have a dead battery by now and i know exactly how much juice my phone eats up especially when screen remains on

simply AMAZING work! ! ! ! !

*continues testing with an evil grin*
[Galaxy S I9000 Android Development] FuryriderX:
You, sir, are the man! Thank you!! Some beer $$ coming your way....
[Galaxy S I9000 Android Development] martan1981:
Q

Is OC working fine for you guys?

I used 4.72 for two days OC to 1,2GHz and the phone freezes like every 6 hours. Of course only when CPU is on 1.2, while gaming or navigating?

What could be the problem?
[Galaxy S I9000 Android Development] knanda:
Can I flash this on darky 9.1?
[Galaxy S I9000 Android Development] waltharius:
Yes.
[Galaxy S I9000 Android Development] coine:
Seems like lagfix to ext4 making a loop to redo the lagfix after reboot.
[Galaxy S I9000 Android Development] zacharias.maladroit:
mazroui,

could you please post your UV settings ?

many thanks in advance

or are you using the ones from laststufo ?
[Galaxy S I9000 Android Development] Mortify1:
Yeah, I was on ext2 (didn't notice a bug) and flashed directly to 4.7.4 (From .3) and I was stuck in a continuous lagfix loop. I decided to wipe everything and flash 4.7.4 again, installed everything and going to do Ext2 right now.
[Galaxy S I9000 Android Development] Mortify1:
Stuck in a ext2 lagfix boot loop again...

I was:

Data_FS=rfs

Cache_FS=rfs

DBDATAT_FS=rfs

DATA_LOOP=false

CACHE_LOOP=false

DBDATA_LOOP=false

Now (In recovery)

Data_FS=ext2

Cache_FS=ext2

DBDATAT_FS=ext2

DATA_LOOP=ext2

CACHE_LOOP=ext2

DBDATA_LOOP=ext2

I'll try rebooting again:

Boots to GT-i9000 screen then New data filesystem config detected...

Going to choose... No, remove the new config (since I'm already on ext2 says recovery)..

Booting again... i9000 screen.

Straight into recovery.

In lagfix menu it says:

Data_FS=ext2

Cache_FS=ext2

DBDATAT_FS=ext2

DATA_LOOP=false

CACHE_LOOP=false

DBDATA_LOOP=false

Trying to reboot system again. At i9000 screen.

Taking its sweet time at i9000 screen and boots into the startup animation I have. (Going to time it)

And now its vibrating on the boot screen... Beep... Beep Beep Beep. Beep... Beep beep beep....

I try a restore all from clockwork backup and saying:

system.img not found. Skipping restore of /system/.

Restoring data...

SWEET it booted... letting it start up and going back into recovery to see what my FS is:

ext2 with no loops.
[Galaxy S I9000 Android Development] existz:
Anyway I can get updated sources or commits?
[Galaxy S I9000 Android Development] pcboyy:
regarding bold item above, do I need to use SetCPU to enjoy the awesomeness?
[Galaxy S I9000 Android Development] bigmo7:
Task manager keeps freezing up, not sure why but I can't use it at all.

Also, the responsiveness of my phone is less than what it was with Voodoo...not sure how to solve it, I'm on 1.2ghz and converted system to ext4 and applied ext4 lagfix without binds...:o
[Galaxy S I9000 Android Development] mazroui:
off to work with my big batteries ^_^

lot of lagfixes to test

seeya in 10 hours with results

regarding the uv (i use the same ones on the first post)

chose 100,200,400,600,1000,1200,1400(it said 5-7 so i chose the max)
[Galaxy S I9000 Android Development] js8:
Am on SM K12T w ext4 fs. Ok to flash this directly? Or should convert to rfs first?

Also sounds like some pref here for ext2 vs ext4? Better battery?
[Galaxy S I9000 Android Development] mazroui:
id suggest rolling back (to stay on the safe side)

u might think u can just flash this over and everything will be ok..... but what if something isn't ? spend even more time restoring ? up to u really

no hard proof yet regarding this latest kernal with battery (just a first picture) but with all the battery saving techniques used i guess it should, i'll test and post results with pics in a couple of days :)

gonna start with lagfixes, to make sure all are usable/with no bugs

then comes the battery part, i know everyone wants both best battery life and speed which is pretty hard to accomplish but i think were almost there :D
[Galaxy S I9000 Android Development] mazroui:
Thats true, im not sure if the lagfix ever worked like that but just tested

scenario 1 (ext2,ext2,ext2,false,false,false,false) = working good (no problems)

scenario 2 (ALL EXT2 + bind data) = no start (after converting and rebooting to start the phone, it stops on New Data Filesystem where it asks to convert data with restore,without.....) so this is a no go

back to testing (i mean work ;) )
[Galaxy S I9000 Android Development] mazroui:
lol did i just notice the media scanner proccess using only 200-400mhz on boot O_O

battery saving couldn't get any better than this i guess
[Galaxy S I9000 Android Development] mazroui:
The Lagfix Test

As of SO4_7_4 ext2 is working correctly :)

#1. Ext2 = working great, (conversion problem solved) converted from rfs to ext2 and was smooth sailing

(ext2,ext2,ext2,false,false,false,false) Thanx laststufo for a really fast one

#2. from Ext2 to Ext2 with binds = no good/ lagfix convert loop on every boot after the conversion (lost all apps when i went back to ext2 to get the phone working T_T had to restore all in CWM with the first backup and everything was good again (no start lagfix loop) i dont even remember ext2 on ext2 with binds was available as there's no benefit to it if i remember ryan from long back correctly.

(ext2,ext2,ext2,ext2,ext2,ext2,data)

~ from here tried ext3 just to see that it converts and my phone got stuck on backing up data with a file called .extfs and stayed there for like 10 mins so i had to force-restart it with 3 keys to get back into recovery ~

#3. from Ext2 to Jfs no binds = first backup showed (jfs,jfs,jfs,false,false,ext2,bind on) changed it to (jfs,jfs,jfs,false,false,false,false) worked fine ( all ringtones/notifications showup correctly so old problem is solved)

#4. from Jfs no binds to Jfs with binds = slow backup n restore but once done all is good with a little stutter here and there. ( all ringtones/notifications showup correctly so old problem is solved)

#5. from Jfs with binds to Ext4 no binds = all good

#6. from Ext4 to Ext4 with binds = all good

+All testings were carried out on froyo 2.2 JPJPG as base and Darkys 9.1 ROM+

need to check on ext2 on ext2, otherwise ext2,4 and jfs lagfixes working good (no idea about ext3 as iv never tried and guess i wont after i read all about the types of filesystems)

now the battery >_< came prepared with the 3000mAh today thinking it wont last long with all those conversions so i guess i'll start that once i reach home with the 1500.

Great job laststufo and wish u all the best bro
[Galaxy S I9000 Android Development] judhas:
hi, some blue/whiter stripe when scroll white backrounded screen...all the rest....is the best!!!

thanks!
[Galaxy S I9000 Android Development] aladin6:
Yes, there is many battery saving techniques in this kernel, i love it !

Logcat is it disabled too ? (like on SpeedMopd kernel ! )
[Galaxy S I9000 Android Development] LukeSP:
I also want to know about Logcat too. I heard from speedmod thread that enabling logcat will impact the phone performance. So hardcore has disabled it but it still can be enabled from CWM.

Edit: LOGCAT is not disabled in super optimize kernel. I has checked it using Android System Info which able to read the log. It can't read the log while using speedmod kernel.
[Galaxy S I9000 Android Development] aladin6:
So why not disabling it ??? :confused::confused:
[Galaxy S I9000 Android Development] laststufo:
i wrote 4/5 pages before about that
[Galaxy S I9000 Android Development] aladin6:
"Logcat use less that 0.01so disable it is useless" .

Understood ;) .

Thank you laststufo for this kernel, excellent really(with undervolt and 1.2Mhz CPU FREQ ;) )(And i just enabled tweaks, no lagfix needed with 2.2.1 ;) )
[Galaxy S I9000 Android Development] LukeSP:
You mentioned "Logcat use less that 0.01 so disable it is useless ". So you thinks that disabling Logcat does not improve battery life or phone performance?

I really like your kernel because it has an undervolt feature ignored by speedmod kernel.
[Galaxy S I9000 Android Development] laststufo:
I think performance gain will be not visible by user disabling it
[Galaxy S I9000 Android Development] LukeSP:
I understand, laststufo. Maybe you're right. I can't notice significant improvement in performance between speedmod and super optimize about disabling Logcat. Anyway, If you have spare time, I would like to see this feature included in your kernel.

Thank you again for your awesome kernel.
[Galaxy S I9000 Android Development] thestorm973:
Hi lastufo, the script for disabled VSF dont work.after every reboot VSF come back and i want disable Vsf tips.

Can you help me ?
[Galaxy S I9000 Android Development] thestorm973:
I think too its the best thing for have a better battery life.

Up 95

Down 70 or 80

in conservative mode .

with this as default threshold in kernel . we can have a lot better battery life :)
[Galaxy S I9000 Android Development] aladin6:
And Freq step, i change it to -5% ? or keep it at -1% ? for Down i choosed 80 :\ !

the values does not save with SetCPU !! how can i apply this threshold values ?
[Galaxy S I9000 Android Development] FuryriderX:
Far as i can tell (the governor settings still seem to be a tad flakey, every time i switch back and forth the 'advanced' tab in setCPU, the numbers change!), the 4_7_4 default is 90% up 55% down, which is far, far better than the 70/30 it used to be. If the down was 70 or 80%, it would probably be even more economical, but thats just my take on it.

I am mystified by the -1 in 'frequency step', this is the number that tells the governor how much (in % of total mhz range) to step up or down, when the criteria set above are met. It should be something like 10%, but maybe the -1 is because of the wider frequency range than stock (?)

laststufo posted why the values

cannot

be set manually - samsung has messed around with the governors in the kernel a LOT, and it can only be changed by the kernel dev.
[Galaxy S I9000 Android Development] farid993:
work fine for me!
[Galaxy S I9000 Android Development] aladin6:
Excellent explanation ;) ! And i'm sure that there is a reason why laststufo didn't choose 70% or 80% in down ! But, if there is a possibility to apply this value we don't say NO ;) ! we are always looking for the best battery life :p !
[Galaxy S I9000 Android Development] thestorm973:
With Gscript Lite ?
[Galaxy S I9000 Android Development] laststufo:
As i said before. Samsung governors are highly customized, by samsung. It's because setCpu do not work as it should.

This is the real threshold table implemented inside my kernel :

{55, 80}, //100

{55, 90}, //200

{55, 90}, //400

{55, 90}, //600

{55, 90}, //800

{55, 90}, //900

{55, 80}, //1000

{55, 80}, // 1120

{55, 75}, // 1200

{55, 75}, // OV

{55, 75}, // OV

{55, 75}, // OV

{55, 75}, // OV

Values higher than 55 start to make phone laggy.
[Galaxy S I9000 Android Development] klau1:
what is the purpose for disabling VSF?
[Galaxy S I9000 Android Development] suntzu123:
55 I think is good enough. You done amazing thing. Thanks :)

so-> At IDLE 100MHz is beast but it is laggy. At 200MHz is quite fine... So set down threshold at 75@200MHz I think would be mistake. 80@100 at up_thershold is really nice! And best values :)

So we can do it for 400-900MHz. It will be agressive slow down. At 200MHz Android working quite well, at 400MHz NFS Shift working really smoth.... So can force phone to use lower Freq as it possible... Not for 900-up. Some apps need power and it can make Dungeon Defenders like aps a little laggy. That is really fine.

But let's make a scenario.... We open webpage that used allmost all power. So CPU move MHz up to 400->600MHz->800MHz and it drop to 70% so CPU move to 600MHz and what happening in next 0,08 second? When CPU go to 600MHz is 100% used and CPU go up in next 0,08s and it loop up.

I just don't know. Is to good thing? But I'm sure that threshold values for 100-200MHz are really fine.

-> My ideas

since 400MHz up_threshold can be 95%?

since 600MHz down_threshold can be 80%?

What do you think?

"

{55, 80}, //100

{55, 90}, //200

{55, 95}, //400

{80, 95}, //600

{80, 95}, //800

{80, 95}, //900

{75, 80}, //1000

{55, 80}, // 1120

{55, 75}, // 1200

{55, 75}, // OV

{55, 75}, // OV

{55, 75}, // OV

{55, 75}, // OV
[Galaxy S I9000 Android Development] doudou1408:
Speed and battery life are better than speedmod ?
[Galaxy S I9000 Android Development] suntzu123:
@up

Stupid q, ofc YES... MUCH! LCD mode at 40Hz+UV make difference. But you have to set up voltage for your CPU.
[Galaxy S I9000 Android Development] aladin6:
I don't know but i think that there is a bug with the screen luminosity, when don't touching it after activation it it keeps doing luminosity MIX and luminosity NORMAL(not max), i don't know how to describe it ! :confused::confused:
[Galaxy S I9000 Android Development] Tababaer:
same here, luminosity is going up and done when doing nothing. automatic brightness controll disabled makes no difference
[Galaxy S I9000 Android Development] thestorm973:
I think its the VSF. its why i want disabled it if its the problem...
[Galaxy S I9000 Android Development] FuryriderX:
Put the disable script in your init.d folder, to turn off vsf. See first post for more details.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] Tababaer:
Worked 4 me thanks
[Galaxy S I9000 Android Development] vid200:
There are no stupid questions only stupid answers. So why don't you enlighten the noob question and explain to him how to get the most out of it. Since you know.