yashsingh1/xdaforums huggingface dataset:
[HTC One S] jodue:
LOL. we are talking about the international version here and no it doesn't have an sdcard slot!

@using an external usb disk: even IF this (usb host mode) is not possible with stock firmware custom rom/kernels will fix this problem ... i am looking forward to a one s running cm9 soon :D
[HTC One S] invasion2:
Oh ****....no SD slot? Can someone explain to me how that would work?
[HTC One S] mattionline:
2.21GB for applications (previous internal memory)

9.93GB as storage (comparable with SD card but then as internal partition via diskdrive or htc sync)
[HTC One S] invasion2:
But isn't the SD card where your phone number is? O_o or maybe I'm just confused. Thanks for all the patience because I've been around SD's for a long time and it'll be weird to not have one.
[HTC One S] l3ft3r1s:
Yes you are... that's the SIM card.
[HTC One S] jigr69:
Internal Memory

Speaking with a very nice woman at my local phone shop, I can confirm that the HTC One S will have 12GB available for the user. The other 4GB is used by the system and applications.
[Galaxy S II General] sahibunlimited:
WOW

Why don't you build your own kernels?
[Galaxy S II General] droidphile:
Because i like to spend my GS2-time tweaking and using the device rather than endlessly coding, making improvements and listen to mixed feedbacks from users :)

EDIT: After 10 minutes of opening thread, someone gave me a 1 star as first rating. :(
[Galaxy S II General] yoohoo:
good stuff

I'll keep this handy the next time I finetune my own kernel.

Keep up the good work!
[Galaxy S II General] Goku80:
Informative as always. Keep it up mate and very helpful as always threads that you make. Hopefully this becomes a sticky as it deserves to be. Thank you:)
[Galaxy S II General] :
Great thread mate, as its previous twin ;) it will become another legend soon!

Sent from my SGS2 - Powered by CM9
[Galaxy S II General] Lonzo_SGS2_506:
Great info mista D. Im learning a lot thx to you man. Keep up with the excellent contributions. Topics like this got me stuck to xda. Thanks!
[Galaxy S II General] krazykat:
Hmm.. seems legit.

Thanks for info. Great learning from you. =)
[Galaxy S II General] bala_gamer:
you are simply the best when it comes to kernels, your knowledge on kernels is outstanding!
[Galaxy S II General] ram3n:
Great topic !

A very best of ! Thanks for all those informations mate :)

Cheers
[Galaxy S II General] cillianire:
thank you

thank you very much for this, very well written and easy to understand, time to start putting some tweaks into action
[Galaxy S II General] hjuo:
I'm curious, all that:

echo XXX > /sys/devices/......

Where did you find those commands? Exist some kind of reference or is from a file in the kernel source?
[Galaxy S II General] Paradoxxx:
The one star guys is probably an ignorant idiot that didn't understand any word here. Awesome job.

Envoyé depuis mon GT-I9100 avec Tapatalk
[Galaxy S II General] pmcee:
i was hoping for a thread like this for a long time ;) have tried extweaks in every position but now i know what i am actually doing ;)

thanks!
[Galaxy S II General] droidphile:
Some of the locations are same as in GB kernels. Rest we can search and find out. And yeah, even sources can help. For example, file that's responsible for hotplugging on ics is stand-hotplug.c; and there's a stand_hotplug directory under sysfs...
[Galaxy S II General] screamworks:
Great work, man. Very thorough, very informative.

screamworks.
[Galaxy S II General] droidphile:
Hm dalvik/tcp tweaks? I'm not a fan of messing around with settings in the ROM space like dalvik or network tweaks. Especially dalvik tweaks - it won't make any significant difference in architectures like that of GS2 and GS3 :)

For I/O tweaks, you can refer threads by Pikachu. His thunderbolt script (which was partially adapted by Siyah) has lot of i/o scheduler tweaks.

This is really strange. ExTweaks app also uses kmemhelper binary for some tweaks, and they're applied at the initial stages of boot - before execution of any init.d script. I don't see why isn't kmem working with initd script. I don't have a GS2 to test this. Any how:-

- try another shell -> busybox

- Force some wait using sleep command

- set permissions for kmemhelper binary itself

- If you're running JB, make sure owner and group of the script are 0-Root and 2000-Shell

#!/sbin/busybox sh

sleep 10

chmod 755 /system/xbin/kmemhelper

LVL=`cat /proc/kallsyms|grep " level\."|awk '{print $3}'`;kmemhelper -n $LVL -t int 14
[Galaxy S II General] robertobsc:
I'm already using the ThunderBolt tweaks. My point is I don't really know what they do, just the general propose.

I want to understand the importance of each io, kernel and any tweak that I use. Just like you did in this unique thread, all variables for all governors. I want to learn it cause I know that always something can be improved or changed for each user need.

And I'm suffering a little to find awnser for each of them.

Enviado de meu GT-I9100 usando o Tapatalk 2
[Galaxy S II General] Many40:
Hi Drodphile,

I'm not very good at adb shell commands and scripting but always willing to learn :).

Good thing is that I managed to make my new touch frq working by init.d script but bad one is that I don't understand why:

This doesn't work:

#!/sbin/busybox sh

LVL=`cat /proc/kallsyms|grep " level\."|awk '{print $3}'`;kmemhelper -n $LVL -t int 14

But this works:

/sbin/busybox sh

su

LVL=`cat /proc/kallsyms|grep " level\."|awk '{print $3}'`;kmemhelper -n $LVL -t int 14

Do you know why? (Of course in both cases with correct permissions 755 and owner/group of the script set as root for ICS 4.0.3). Regards
[Galaxy S II General] droidphile:
Oh ok. Actually, I have been thinking about another (exclusive :) ) thread for sometime now. I wanna make it practical, in a way that's useful to readers and also satisfies me!

My knowledge sharing still continues across posts in S3 forums. After I'm done with the thread-in-my-mind, i will try to have a thread on i/o tweaks, dalvik tweaks, etc - the miscellaneous tweaks which people blindly flash as scripts without knowing what they do and what they don't do!

Sometime after posting my previous reply for you, i noted i missed "su". Thought editing and adding it won't be apt as you may not read it again.

You remember when you successfully executed command using script manager, you had set to run it as root?!

I think root privileges are required since the kernel space containing exported symbols and it's value requires root to modify (via kmemhelper).
[Galaxy S II General] fabioascoelho:
Neverming, i fixed my problem.
[Galaxy S II General] vitoski:
droidphile thank you very much for this thread! Thanks to your knowledge and shared information I was able to tweak pegasusq on my S2 according to my needs.

However there is one thing I would like to ask you to help me with...

Since some people started complaining about the way the latest betas of Siyah kernel handle hotplug (turning on and off second core), I would like to ask you if there are any other parameters or maybe logic that controls hotplug besides the ones you have mentioned in the third post?

Why I am asking?

Even though I set up my pegasusq settings with SetCPU similarly to values proposed by you (as yours in third post) I see that second core turns off only when I switch off the screen. As people report it started to happen since Siyah version 4.0.x.

I confirmed that second core only turns off when the screen goes off. However while screen is on and you do not touch the phone, second core is still online but on the lowest frequencies.

Hope to hear from you some info:)
[Galaxy S II General] droidphile:
When pegasusq is the governor, only the hotplug logic of pegasusq itself controls hotplugging IN & OUT CPU cores. Other hotplugging logic/algorithms are not active.

I don't own a GS2 now, so can't test Siyah 4.0.x 's. If you're sure about this problem, intimate GM he might be able to see what went wrong.

But, did you use tegrak second core app or similar to check no of cores? Note that opening that app causes an overhead of more threads(or increased run queue length) and it may take more time for second core to turn off. Another thing to check is rightly configured parameters. Most importantly, this condition should be met:- hotplug_freq_1_1 > hotplug_freq_2_0 > scaling-minimum-frequency. Otherwise, second core would refuse to turn off after kicking in.
[Galaxy S II General] vitoski:
Thank you so much for reply. I use CPU Usage Monitor app to see when the second core is online. I agree it may kick off when the app is launched but after some time it should go off, without need to turn off the screen:)

As for the parameters you mentioned I set them exactly as you mentioned, so it's respectively 400000, 300000 and 300000.

At least two person have reported this on Siyah thread (including me today), so we will see what GM will say about it:)

Last time he was not happy that people complain about it:)

Edit

Just to be 100% sure. So the only parameters that control pegasusq logic are the ones you listed. There is nothing more built-in pegasusq logic that kernel dev can change but users not?

Thank you for your help.

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[Galaxy S II General] droidphile:
It's not exactly as i mentioned. I said hotplug_freq_1_1 > hotplug_freq_2_0 > scaling-minimum-frequency.

Set scaling min frequency to 200 and check if 2nd core turns off.
[Galaxy S II General] vitoski:
Yea you are right:D

When I said "I set them exactly as you mentioned' I was referring to your third post, not the condition you gave me in the last post (hotplug_freq_1_1 > hotplug_freq_2_0 > scaling-minimum-frequency):)

Just one last question would like to ask you.

I am playing around with pegasusq settings so that my CPU will be scaled to most frequencies of the table instead of jumping from i.e. 500 to 1200 and back when I use the phone.

However here is the question. Do you think it's better for the phone (battery) to jump between frequencies or simply go to the max when the phone is utilized and go back down when i.e. I am listening music?
[Galaxy S II General] Many40:
Hi Droidphille,

Could you pls have a look at this issue related to problem with execution a command with kmemhelper after flashing Siyah 4.1/4.1.1?

http://xdaforums.com/showpost.php?p=30632442&postcount=12419

I would be greatful if you had any suggestions.

Best regards.
[Galaxy S II General] droidphile:
<again> No device, can't test :) </again>

- As you know the command reads all symbols with text "level" in it and awk append character digits as retrieved from 3rd column, starting from first row. In the latest Siyah, this symbol name might be invalid because now it should be retrieved from a different row other than first (and 3rd column) or so.

- For externalSDdo a thorough checkdisk and try again.
[Galaxy S II General] robertobsc:
Hi Droidphile,

Please take a look at the new governor that came out in Siyah Kernel. LulzactiveQ.

http://xdaforums.com/showthread.php?p=30839989

Yes, I'm the one who did it ;)

Enviado de meu GT-I9100 usando o Tapatalk 2
[Galaxy S II General] droidphile:
I heard of it from GM yesterday. Congrats! Should be the first ever interactive governor with hotplugging logic. I checked yours and GM's git and couldn't find the governor. Good you linked the thread :)

EDIT:- Read your post. Single cut-off frequency was a problem for luzactive. With dec_cpu_load, you have made scaling down more sensible. Separate thread for hotplugging is also a good idea. Good job. I will add luzactiveq to OP of other thread.
[Galaxy S II General] robertobsc:
Thank you! I'm very happy you and so many people liked it.

GM posted in other branch.

The default branch is ics but he created an ics-3.0.15.

https://github.com/gokhanmoral/siyahkernel3/tree/ics-3.0.15

Enviado de meu GT-I9100 usando o Tapatalk 2
[Galaxy S II General] robertobsc:
Hi Droidphile!

Some changes happened to Lulzactiveq since the first post.

Gokhan did a big merge with interactive governor, without changing the lulzactive concept.

I got the merge and then

- re added the dec_cpu_load

- Included the ignore_nice_load (from pegasusq)

- adjusted a mechanism from scaling up/down sampling rates.

Probably after migrating this governor to S3, we can say that the work with it is done.

The last sources are in gokhans repo.

Enviado de meu GT-I9100 usando o Tapatalk 2
[Galaxy S II General] droidphile:
Hi

I was really busy for the last 2-3 weeks. I will add info on luzactiveq to OP by tomorrow.
[Galaxy S II General] HTCinspiration:
Hello droidphile, i have a question about using daemon oc with certain governors. Since the daemon has a sleep profile, isn't it pointless to use governors like smartass, which have their own built in sleep "profile" can u use the 2 together or does one override the other? Thank u for any help u can provide on this & thank u SO much for this awesome thread! :')

Edit: My apologies, i thought i was posting this in your other kernel, modules thread
[Galaxy S II General] droidphile:
Hi

I replied to your PM yesterday, but the message did not go through as it said your inbox size quota has exceeded.

I am not so familiar with virtuous daemon. Anyhow the oc daemon will work only if all cpu tuner apps are uninstalled. If any such app is installed, daemon deactivates itself. For screen state scaling, my personal opinion is to use a script (you can find many if you search) or an app like SetCpu. SetCpu has transformed to a nice handy app that can configure parameters of any governor. The app supports sleep profiles and there's no lag while switching governor during screen state change. I'd recommend to fine tune your governor to make the device more snappier than to use VD.
[Galaxy S II General] Shahrokh.KING:
hello droidphile, how can i change sched_mc value? it not in extweaks anymore (siyah 4.1.5)
[Galaxy S II General] Many40:
Hi, if you have found couple of minutes and have red the 1st post you would have known that it's possible by a init.d script:

/sbin/busybox sh
su
#disable sched_mc
echo "0" /sys/devices/system/cpu/sched_mc_power_savings
#enable first core overloading
echo "1" /sys/devices/system/cpu/sched_mc_power_savings
#load balancing
echo "2" /sys/devices/system/cpu/sched_mc_power_saving

Use one of the three last lines depending what value you would like to set.

More about init.d scripts you can read in another very usefull droidfille's post

HERE.

PS. pls don't post the same question in different threads. If you are patient for sure someone will help you. Moreover, I already answered you on the main Siyah kernel's thread that according to gokhanmoral wish it is only for development related issues.

All the best. Regards
[Galaxy S II General] Shahrokh.KING:
it means i have to create a file named "sched_mc_power_saving" in that path? with a number in it?
[Galaxy S II General] droidphile:
You don't have to create any. The kernel creates the files while booting if the feature is supported.

In general, when such a file doesn't exist, it means a) Path was changed. or b) Feature is no longer supported. In either case, creating such a file manually and echoing values to it doesn't add a feature :)

So you just echo value to that file, to the path specified by many40. Remember to add ">" sign after echo.

echo "2" > /sys/devices/system/cpu/sched_mc_power_saving
[Galaxy S II General] frankcilo:
If I set min freq to 500mhz, I set the freq_for_responsivenes to 600000??

echo "600000"> / sys / devices / system / cpu / cpufreq / pegasusq / freq_for_responsivenes
[Galaxy S II General] Many40:
Yes, you can do that. You also can disable freq for responsiveness by setting it to a value of min scalling freq - in your case it's 500MHz. Test what is best for you.

BTW setting min scalling freq to 500MHz is not so battery friendly, is it? :)

Regards
[Galaxy S II General] robotbiru89:
cool stuff!
[Galaxy S II General] Many40:
Hi, droidphille

Could you then correct it in your thread (post no 1 / para 8). My fault was that I just copied the content from your OP without checking :). In other paragraphs ">" sign exists but this.

Regards and all the best.
[Galaxy S II General] plotinus:
Wrong thread. Sorry
[Galaxy S II General] swavab:
How to get deep sleep in secondary rom..?
[Galaxy S II General] frankcilo:
If I set 500mhz as min freq, I have more respond and same battery life!

Please, try it yourself!
[Galaxy S II General] Many40:
Ok, thanks I will. But I have doubts. If being on 500MHz CPU consumed the same amount of power as on 200MHz, Samsung would implemented 500MHz-1200MHz as default frequency scalling range but it didn't :)
[Galaxy S II General] willybarca:
setting touch freq doesn't work on cm10, i used to set my touch freq on 200 on ics but it dont work on jb,

Sent from my GT-I9100
[Galaxy S II General] willybarca:
also i remember there was a script to tweak the blue red green, cause my blue is degrading fast, i searched every where but i couldn't find it
[Galaxy S II General] willybarca:
wow this place used to breath before,
[Galaxy S II General] droidphile:
It still do.

Without actually describing what you mean, have no clue what is it about.

Try this

kmemhelper -n `grep "^$(cat /proc/kallsyms | grep ' mov_hysti$' | cut -c1-4).* level\." /proc/kallsyms | grep -o "level.*"` -t int 14
[Galaxy S II General] willybarca:
i dont remember exactly but i think

it was something like adjusting the mdnie values for the these colors

user_cb

user_cg

user_cr

my blue is really fading man,

---------- Post added at 04:07 PM ---------- Previous post was at 04:02 PM ----------

oh by the way for that command it says kmemhelper not found
[Galaxy S II General] droidphile:
You're on siyahkernel right. I don't follow Siyah development for GS2 since I don't own it now.

Whether using script or adb, put an "su" first. Kmemhelper requires root permissions to modify symbols
[Galaxy S II General] Honusnap:
Hotplugin..

Hi all,

A question about kernel and frequency scaling and hotplugin, do you know if the load_h0, load_l1 has to be updated when the scaling_max_frequency is increased / reduced ?

Or otherwise said : Are these three parameters connected, if yes .. how ?

- scaling_max_frequency

- load_h0

- load_l1
[Galaxy S II General] droidphile:
Yes, load_h0 and load_l1 depends on scaling_max_freq in Stand Hotplug. (Legacy Hotplug load calculations does not consider scaling max freq).

avg_load = (current_frequency * load) / (scaling_max_frequency * 2)

When condition "average_load is greater than load_h0 to turn 2nd core on" is met, the equation becomes

load_h0 = (current_freq * load) / (scaling_max_freq * 2)

OR

(current_freq * load) / (load_h0 * 2) = scaling_max_freq

If you're changing scaling_max_frequency, to maintain same characteristics as your previous values for load_h0 and load_l1, update load_h0 and load_l1 by dividing them with (1+x) where x is the percentage difference between new scaling_max_freq and old one.

For ex: if load_h0 was 25 and load_l1 10, scaling_max = 1200. For a new scaling_max 1400 (which is approx 17 % increase on 1200) new values should be

load_h0 = 25/1.17 = 21

load_l1 = 10/1.17 = 8.5

Round them off. Similarly for new scaling_max that's less than current scaling_max, divide loads by (1-x)
[Galaxy S II General] Honusnap:
Thanks a lot for this perfectly clear and well explained reply. For what i understand, the "Legacy" technique do not use scaling max frequency, but the "Stand Hotplug" does, the load_H0 that we are now using is relative to the max scaling... i understand that the point was to have a coherent avg_load among all frequencies...

See the attachment, i've used your formulae, AvgLoad is calculated based on the two previous columns, Max SCaling is 1200Mhz.

For what i see, if i want the second core to kick in at 200Mhz for a 50% load, i should use 4 for Load_H0 ... m i right ?

It means that when it reached 1200Mhz second core will kick in at 8% load (that give 4 as average load) ...

That's mean in fact that this way of using AvgLoad instead of "Simple Load" will start the second core faster (with a lower load) when the frequency increase ... right ..? Well .. why not ... :)

So i suppose that i should now try with a very low value since i want the second core to kick in early... something like 6 or 7 for Load_H0 and 5 or 6 for Load_L1...

Thanks again for taking some of your time to take me out of the dark .. :good:
[Galaxy S II General] droidphile:
Yes, legacy hotplug do not consider scaling_max_freq to make hotplug in/out decisions.

You can set your load_h0 and load_l1 considering average_load calculations depending on at what frequency and simple load you need second core to turn on/off. Hotplugging logic trick is to kick in second core at different frequencies depending on the load. For example, load_h0=8% means 2nd core can kick in at 100% load at 200mhz or 25% load on 800mhz, but not at 25% load on 500 mhz to save some power.
[Galaxy S II General] Honusnap:
Yes, that what i understand... but for what i know 2 cores at 200Mhz are more power friendly than 1 core at 400Mhz... (do not remember who i discuss that with), meaning that dual core should get a small "bonus" over single core... so this "average load" way of seeing things can certainly be improved.

100 Mhz Dual is better than 200 Mhz Single

200 Mhz Dual is better than 400 Mhz Single

.. etc

.... Well for some "single core" application this is not right... perhaps it would better to have one core in case one application only is running "actively", but there is already a trigger for that.

Globally for what i experienced in real world ... under very low load : Stay at 100 Mhz single core, load increase... go dual right to the top max frequency, the increase "grain" is small enought. (included picture).

The more there is available frequencies : 100, 200, 300, 400, 500, 600 ... 1200 (some kernels) vs 200, 500, 800, 1000, 1200 (stock CM10), the more the previous observation is true, "grain" is smaller.

What do you think ?

Ps : If that discussion bother you, feel free to gave it up ... :)
[Galaxy S II General] toonarmy4life:
I suffered from kernel panic I was on stock ics 4.0.3 LPQ I flashed siyah 4.0.1 cwm then phone kept restarting to kernel panic when I try acessin task manager or checking apps info nd I've tryed different kernels nothing fixed it so having to dual boot to get stable from cm9.1 but apps keep crashing so probably not have a working phone soon
[Galaxy S II General] cezarbigboy:
How remove this eye bootlogo ( splash screen) of Siyah Kernel from start?

Thx for ans.

Thats ok, got it - is in 5.0: http://www.gokhanmoral.com/?p=1536
[Galaxy S II General] Shahrokh.KING:
Could i have a more specific detail on cpu_up_freq and cpu_down_freq? Since its now included in siyah kernel
[Galaxy S II General] droidphile:
The interfaces are available, but he put them back for comparison purpose. Both the tunables are still not used in Pegasusq S2 or S3 kernels. Refer:-

https://github.com/gokhanmoral/siyahkernel3/blob/master-3.0.31/drivers/cpufreq/cpufreq_pegasusq.c

https://github.com/gokhanmoral/siya...ter-3.0.31/drivers/cpufreq/cpufreq_pegasusq.c
[Galaxy S II General] Many40:
Hi droidphille,

Just after reading again your great guide about dual-booting one thing puzzles me a lot - am I wrong by saing that:

FACTORYFS -> /dev/block/mmcblk0p9 = system partition of 1st rom

HIDDEN -> /dev/block/mmcblk0p12 = partition used by Siyah as system partition of 2nd rom.

If not, could you please correct it in your OP? (quoted beneath) Just for the others who could read it later.

Regards
[Galaxy S II General] droidphile:
Oh my bad, looks like they were swapped. Corrected.