yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
I would suggest 3.2.7.1 ; you can download it from this link:

(it's not on the official blog anymore, but still one of the best)

http://xdaforums.com/showpost.php?p=27047682&postcount=1378

---------- Post added at 07:44 PM ---------- Previous post was at 07:37 PM ----------

..I doubt it...rom features rarely depend that heavily on kernel linux base version, maybe in a very extreme but rare case....

So as long as the device hasn't reached it's life-cycle limit (nowadays at most 2-3 years), I'd keep on using it

by that time you'll also have an S3:laugh:.... or maybe even an S4:eek:
[Galaxy S II Q&A, Help & Troubleshooting] Jokesy:
Hi all.

I've been a long time user of Siyah kernel from Gingerbread days (which was well all-rounder for me) to ICS.

I've flashed every version of Siyah 3.x.x except 3.3.1 and I have always experienced one major problem no matter the ROM I am/was using. It tried it on AOKP ROMs, CM9 and even stock ROMs but the same issue persist. I never had this problem with fluxi but because I so much love the dual boot feature of Siyah, I had no choice but to come back.

What is problem?

I use Wifi-Hotspot/tethering feature a lot on my phone but Anytime I use this feature, my phone would reboot at least once every hour.

All my flashing have either been thru clean install or after flashing cleaning scripts, wipe caches etc.

Presently I'm running Siyah 3.3.2 but the issue still persists.

Please help
[Galaxy S II Q&A, Help & Troubleshooting] ufo900:
May I ask why not 3.3.2 but that version? ;)

Another question: after a little UV in extweaks, it is better to set battery profile in CMW or better to stay with default one?
[Galaxy S II Q&A, Help & Troubleshooting] Many40:
1. Some forum members claim that 3.2.7.1 is more battery saving (friendly) than 3.3.2. It is subjective issue so I am not convinced yet and still testing them both.

2. I am not sure what you mean. Kernel profiles are stored in /data/.siyah folder. They contain preconfigured settings by Dev to make you life easier. However you can customize (edit) them all according to your needs. You can switch between them from ExTweaks app (only paid version) or from CWM recovery. You can also shift back to the original profiles when you use "Reset ExTweaks settings" option from CWM recovery.

Regards
[Galaxy S II Q&A, Help & Troubleshooting] ufo900:
understood what you mean, thank you :)

now i'm leaving default profile from cmw with some tweaks and UV in Extweaks and then I'll put battery profile with tweaks to see the difference :)
[Galaxy S II Q&A, Help & Troubleshooting] robertobsc:
For me 3.3.1 is cleary more battery saver than 3.3.2.

But it has so much variables, for one can be great for other not so good.
[Galaxy S II Q&A, Help & Troubleshooting] robbytf:
ok so this is what happened: i am on stock ics 4.0.3 (I9100XWLP8_I9100XSALP4_I9100XXLPS_HOME.tar) and flashed (CF-Root-SGS2_XW_XSA_LP8-v5.4-CWM5) to get cwm, then on recovery i flashed siyah 3.1.2 (because it works) then reboted into the siyah recovery, then i did wipe data, wipe cache partition, went to mounts and storage and format /cache, format /system, format /data, format /external storage and format /preload. then i went back, went to kernal specific options menu, reseted extweaks profiles and "remove all files in init.d folder", then i went back, went to advanced and ddebigging menu, wiped dalvik cache and fix partissions. then i pressed "reboot into download mode" then flashed with odin (I9100XWLP8_I9100XSALP4_I9100XXLPS_HOME.tar) stock ics. then after it rebooted i flashed (CF-Root-SGS2_XW_XSA_LP8-v5.4-CWM5) to get cwm, then on recovery i flashed siyah 3.2.5.2. then when it rebooted, it goes passed the samsung boot logo then gets stuck on a black screen... i put it into download mode flashed siyah 3.2.5.2 with odin same thing happened with the black screen, i put it into download mode again flashed siyah 3.3.2 with odin same thing happened with the black screen,i put it into download mode again flashed siyah 3.1 with odin and it works like a charm,i put it into download mode again flashed siyah 3.1.2 with odin and it works like a charm, i put it into download mode again flashed siyah v3.2beta1 with odin same thing happened with the black screen, then i flashed siyah 3.2.5.2 again with odin same thing happened with the black screen.... something is wrong, all of the siyah versions that are under 3.1.2 work and the versions above 3.1.2 get a black screen after the samsung boot screen...
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
ok...I'm convinced you did all options suggested...so the only option still open is that it may be the particular version of rom you're using ; try downloading it from another source than where you got this one (samfirmware.com for example) or use one from another compatible region.

and if you're not commited to stock, try some other rom of your choice, as long as it's ICS...

If that doesn't solve it, then it must be some bug in your device,,,other than that there's nothing else I can imagine wrong here...:confused:

ps. you don't have to root before flashing siyah ; it auto-roots....(also possible link of breakage, here, the CF-root used,not that it's bad, but could be a source of the problem)

just flash siyah with odin directly onto stock. (may be this option is the least time-consuming, before trying al other above-mentioned : go back to stock(odin), let it boot and settle, download-mode, odin (1.85), and flash one of the latest siyah, reboot) (this way you skip cf-root, if it, is causing the problem)
[Galaxy S II Q&A, Help & Troubleshooting] sora9961:
Kennel siyah 3.2.7.1 better or kennel abyss ics4.0 better ???
[Galaxy S II Q&A, Help & Troubleshooting] ammar1514:
lol you are asking this in the siyah thread...ofcourse siyah is better

please press thanks if i helped :)
[Galaxy S II Q&A, Help & Troubleshooting] sora9961:
Why do you know kennel siyah 3.2.7.1 best???
[Galaxy S II Q&A, Help & Troubleshooting] coloxim:
Update .36?

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Q&A, Help & Troubleshooting] carlos67:
Yes, I have the same issue with the GPS toggling not seeming to work sometimes. Only noticed it today.
[Galaxy S II Q&A, Help & Troubleshooting] egps2:
+1 I Have the same gps toggle issue (anywhere in settings like above) and it is extremely frustrating as I have to reboot frequently to reset it! I asked around here before but no one seemed to have this issue! Please post here if you find any solutions!

Ps I did find one thing which seemed to help but I don't recomend! I cleared data on settings and settings storge apks and my gps toggle worked perfectly but my phone seemed to act strangely and I had to restore backups of those apks and then the GPS was buggy again but my phone was stable.

Does anyone know a good way to reset android settings (apk) not the WHOLE phone? It seems like this should help but then again this issue was not present on stock kernel so hopeful there is a fix somewhere as I can't (for a while) wipe my phone!
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
you write that you've tried all 3.x.x versions ; does that include 3.2.7.1 ?

(considering that the problem may be wifi related...)
[Galaxy S II Q&A, Help & Troubleshooting] coloxim:
With last cm9 rc.. when I'm in aeroplane mode I've many kernel wake lock..

I lost 5/6% this night...with another kernel this not happen..

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Q&A, Help & Troubleshooting] francesco.cordella:
Hi guys..can someone give me good settings for a great battery life?

I'm using siyah 3.3.2 and RR 2.5.1.. thanks
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
if you're on 3.3.x, maybe some compatability issues with cm9, because of parts taken out...?

have you tried with an older version of siyah?
[Galaxy S II Q&A, Help & Troubleshooting] alinawyx:
well, i posted this wrongly on development thread. i've got 8hrs screen on (posted with images). while and in case someone question again, why is there difference in battery % between the 2 images, it's because that i started charging when i reached 15%, then i realized i wanted to add in screenshot of the 8hrs of wifi, so i took another screenshot after a while. my initial idea was just to show the 8hrs of screen on. finally here is my config. but i like to say it once more, it works for my customization (ROM + kernel), and may not work for everyone (use it at your own risk) :eek: it was and is very stable for me :fingers-crossed:

P.S. I tested the so-called GPS bug, because i had it before. but previously, i realized it was due to the ROM (with JKay Deluxe Settings-XWLPG framework) that i'm using. After i reverted to previous version of the same ROM (JKay Deluxe Settings-XWLPF), i had no more of the GPS issue.
[Galaxy S II Q&A, Help & Troubleshooting] Many40:
Hi johnbeetee,

Great post, great settings. Some of them I am already using, some I am gonna use soon (with your permission of course;)). After going through your post I am wondering about two things: first one - I red somewhere that at 100MHz SGS2 consumes even more battery power than at 200MHz and the second one - by underclocking to 600MHz don't you disturb a balance between performance and power saving? Does your phone still have soul of a proud high-end SGS2 if limited to 600MHz? Just my stupid question. :) Regards and respect.
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
..you are welcome to try any one of the settings

The beauty of it all is that, thanks to pegasusq it's possible to use these (rather cramped) settings and still it doesn't feel laggy for me (which would sure be the case if it was one of the other governors). And when a liitle more power is needed, shifting it a few notches up is done in a flash.

(I can even up the freq. if I want per app using Tasker ; I'm a big fan of tasker, maybe you've noticed...;))

And that about 100mhz using more energy is very relative and clinical ; while using pegasus or any other well configured governor, it's not true at all.

I've used lots of monitor tools (cool tool is one of them) and looking at the normal functioning, when idle and on 100Mhz the load is usually around 30-40% average and doing those light task at higher and finishing faster won't save more energy in my opinion, as oposed to the energy consumed to scale up, perform, and scale down again...

So, in short, yes my sgs2, still has the soul and zest of a raving beast....(partly thanks to automation with tasker....:D)
[Galaxy S II Q&A, Help & Troubleshooting] robertobsc:
Very instructive post john, thank you.

An important point: I can be wrong, but I don't think that your pegaus tweaks in matter of enabling / disabling second core are being useful. Let me explain why:

To enable 2 core, the criteria is curfreq >= 1_0 freq && cur_qr >= qr_1_0. And the opposite for disable.

So, putting your values cur_freq >= 400 and

cur_qr >= 350 / cur_freq<=200 and cur_qr <= 345

The number of processes in queue that matters. See, if you have 345 process in queue its very possible that your load is high. I wanna mean that, there are no differences of 350 to 345. In fact, if you turn on the processor list in developers option, you can see that the number of process in execution changes a lot.

May be that the frequence to disable the second core is saving you, because If the load is high is very unlikely that the frequence is in 200...humm..... Can you explain what was your idea to put these values?

Thanks
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
That's one of the things I find very hard to predict theoretically, a process structure which is dependend on a number of interlinking variables...

so how did I came about to these values? Just trial and error and one usefull tool, micro cpu monitor from the market. It's very simple, but just that and it gives me enough insight when tuning governors and thresholds, even the classic governors and using the classic hotplug mechanisms: one or two fine lines at the top of screen, showing the processor(s) load (and thus 2nd core active or not).

You can try it out and look at the behaviour on load. The main goal of these settings (and they are just one set, maybe with a totally different set you can gain the same result) is to keep the frequency as low as possible when load is low, on higher load scale up, and when load high enough, hotplug 2nd core, but when job is done and load lowers, turn off 2nd core as soon as possible, to save energy.

And I've tested this extensively, in search of these settings and believe me, the 2nd core is being used just the way it is supposed to...

I do agree with you, at some point it would be possible to 'calculate' or at least simulate the behaviour of the system with a proper model, but for this purpose I chose the shortcut and just looked at the behaviour and a bit of trial and error and some instinct... :o
[Galaxy S II Q&A, Help & Troubleshooting] coloxim:
I've used another kernel with same app and same rom and seems better...

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Q&A, Help & Troubleshooting] robertobsc:
Although I'm more theorical your answer seems good to me. ;)

Interesting. I'm using this tool also. I think that it would be very interesting if he puts the number of process and frequency also. So we would understand much better how it works and it would make much easier to apply the correct settings for each one.

That's because the extensive tests you made make the results for you and possibly for much others it wouldn't work. Number of process and how we use the phone makes a good difference in that terms... in my opinion!
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
Totally agreed...this set of parameters isn't meant as 'the wholy grail' of all settings, but just as an indication and what works for me, and of course you are right, the number of processes and therefore the size and population of the queues matter a lot and would produce a totally different balance point for someone else or eve nfor me if my use would change along time.

It's simply a small indication of what's out there to be adjusted and 'played' with to find your own balance, mainly for people seeking a starting point....

and at times I can be theoretical too, but only if the situation calls for it...but that just as side note ...:)
[Galaxy S II Q&A, Help & Troubleshooting] bgx:
Using long time tasker to do this, with one difference ... I had a script witch get the sunset and sunrise. If its after sunset display will dimm down automatically! Lots of other tasks like this in my tasker like screen automatically invert if an app starts witch is normally white....

Hope I can give you new ideas! :D

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II Q&A, Help & Troubleshooting] #illidan:
Anybody know how to echo values for busfreq modification? Do we have to do it through kmemhelper only or can we just echo the value to a file path somewhere in /sys.
[Galaxy S II Q&A, Help & Troubleshooting] LocutusEstBorg:
Touchmove Sensitivity simply does not work. No matter what I set it to it's always 16px when testing in applications.
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
Most importantly, I'm always open for, and welcome new idea's, thank you...

but having a technical background, I chose for a slightly more complex, but elegant solution: (i've added 3 tasker tasks in the attachement)

I started by taking measurements using 'lightsensor' and determining which gamma_shift would be acceptable at that lightlevel.

After enough measurement points, I analyzed the data and confirmed that light(intensity) pretty much behaves like sound(intensity) and having a logarithmic scale of perception.

After that I determined a suitable function to calculate the gamma_shift with depending on the lightsensor intensity value (which varies from 0 in darkness up to 160000 or more in direct sunlight) which is :

-50 + 20 * (log10 (lightsensor)-2) for lightsensor >= 100

changing the factor 20 you can tweak for lower or higher preference (+/-20%)

Using this I made 'gamma_adj' task which reads the lightsensor and calculates the gamma_shift (-50 if lightsensor<150;caclulate if higher)

After 3 seconds, it takes another measurement and determines the max_gamma with using task 'gamma_range' (gamma_max 12 16 or 24).

This way, every time I turn my screen on, tasker calls gamma_adj, it determines the ideal gamma_shift and max_gamma, whether I'm indoors, outside, day or night, only depending on the light circumstances :) , and optimally saving energy
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
I don't think that's possible with echoing values ; at one point with version 3.2b6 and b7 we could change the internal voltages in :

/sys/class/misc/customvoltage/max_int_volt

/sys/class/misc/customvoltage/int_volt

but that interface has been removed in 3.2b8, so for now kmemhelper is the only possible way for the bus voltages.

I don't know if the frequencies can be changed at all, I think these are hardware determined and only 133 266 400 are valid values

I think you still can lock these frequencies like in gingerbread on a cpufreq basis (locking one bus freq to a cpu freq) as opposed to dynamic busfreq scaling

here a quote from droidphile:

---------- Post added at 10:35 AM ---------- Previous post was at 10:18 AM ----------

The sensitivity tweak in extweak is not actually a touch sensitivity value, but more like a damping interval to prevent jittering (hysteresis value) if you're experiencing any ; to really change the sensitivity, you will have to use kmemhelper and change some values using scripts and test....

# offset 59: MXT224_THRESHOLD_BATT_INIT
kmemhelper -n mxt224_data -t char -o 59 50
# offset 60: MXT224_THRESHOLD_CHRG
kmemhelper -n mxt224_data -t char -o 60 55
# offset 61: MXT224_NOISE_THRESHOLD_BATT
kmemhelper -n mxt224_data -t char -o 61 30
# offset 62: MXT224_NOISE_THRESHOLD_CHRG
kmemhelper -n mxt224_data -t char -o 62 40
# offset 63: MXT224_MOVFILTER_BATT
kmemhelper -n mxt224_data -t char -o 63 11
# offset 64: MXT224_MOVFILTER_CHRG
kmemhelper -n mxt224_data -t char -o 64 46
# offset 67: MXT224E_THRESHOLD_BATT
kmemhelper -n mxt224_data -t char -o 67 50
# offset 77: MXT224E_MOVFILTER_BATT
kmemhelper -n mxt224_data -t char -o 77 46
[Galaxy S II Q&A, Help & Troubleshooting] #illidan:
I was aware of the internal voltages part as well as the fixed bus frequency but what I actually wanted was to lock the bus freq to the cpu frequency instead of it being dynamic. Droidphile's post just mentions about busfreq voltages so I though maybe the free could be locked. That quote from droidphile just talks about locking bus freq in GB but in ICS those file paths are not there as I tried searching for them but i couldn't find them. Anyway I guess I would have to dig through kmemhelper to see if it's possible.

Edit: typo
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
if I understand you correctly, droidphile's posts is exactly what you want : locking a particular busfreq. to a particular cpcfreq. instead of dynamic scaling of the busfreq.

The path is there in ICS, only that particular file is not, because it's running default (scaling busfreq.)

You can add it by using a script containing:

#static bus frequency

echo "enabled" > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static

echo "0 0 0 1 1 2 2 2" > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static

this being an example with 8-cpu steps ; if you're using more, then there will be more 0 1 and 2's which represents the busfreq.level

whether this will have effect, depends on this feature being implemented in the kernel, which I don't know for sure.....you'll have to test that and find a way to measure and confirm..
[Samsung Epic 4G Touch] sfhub:
Reference Section

A) Resources

a1) tar.md5 versions of One-Click (for regular ODIN):

SPH-D710.FE16_CL579416_ROOTED-sfx.exe [Mirror1 / Mirror2] [MD5: 86c9bb2333987a348ddf934445f12676 / Size: 308,337,609]

SPH-D710.FE16_CL579416_ROOTED_NODATA-sfx.exe [Mirror1 / Mirror2] [MD5: 0a0caa5cb86eb22a517f24e0a9a459f6 / Size: 307,353,482]

B) (Individual) STOCK FE16 ODIN/CWM Components

b0) Odin3 v1.85 (windows)

- these are ODIN tar.md5 files bundled in a 7-zip self-extractor

- ONLY use

PDA Button

for any of the following

- Windows - Double-click on the self-extractor and choose your ODIN directory

- Mac/Linux - Use 7-zip to extract

b1) [ODIN] FE16 Modem [Mirror1 / Mirror2] [MD5: 31683497e9d5553488f520f6a365ffab / Size: 4,095,394]

b2) [ODIN] FE16 Kernel [Mirror1 / Mirror2] [MD5: 826477b287aca5f9abce2d4d222ac9af / Size: 6,078,544]

b3) [ODIN] FE16 ROM [Mirror1 / Mirror2] [MD5: bf4e59656017c29b96bdbce2d21102e4 / Size: 288,512,372]

b4) [ODIN] FE16 ROM + root [Mirror1 / Mirror2] [MD5: 5e5c73fae0d81c421762086cd3e2df87 / Size: 289,813,742]

b5) [CWM] FE16 Modem [Mirror1 / Mirror2] [MD5: 6a9fd88b5eb6315bd33a5e43dba66928 / Size: 5,133,881]

b6) [CWM] FE16 Kernel [Mirror1 / Mirror2] [MD5: b70c4b52e5953cf4f4e9a1d0deede8f7 / Size: 6,035,719]

b7) [CWM] Repack - FE16 Kernel (Unlocked Recovery) [Mirror1 / Mirror2] [MD5: 12a1e861440ee059cd3ab115cd729d02 / Size: 6,036,136]

b8) [CWM] Repack - FE16 Kernel (Plus) [Mirror1 / Mirror2] [MD5: b66ba5960bdd4bddf526717800ce9728 / Size: 6,021,172]

- Plus = unlocked recovery, initd, bootanim, usb-ms, adb-root

C) FAQ

c1) Windows tells me "Unrecognized device (code 42)" and ODIN OC doesn't see my phone

c2) What happened to USB Storage in ICS, how do I get the old GB behavior back?

c3) How do I run Auto Root, ODIN OneClick, or ODIN on Mac?

c4) What about the notification bug?

c5) How do I get Sprint TV to work?

c6) How do I get wifi tethering for ICS ROMs?

c7) How do I enable the stock ICS launcher instead of TouchWiz?

c8) How do I do screen captures in ICS?

c9) How come the wallpaper doesn't scroll?

c10) How do I resolve Contacts app Force Closing?

c11) How do I access the ##DEBUG# menu?
[Samsung Epic 4G Touch] Omar04:
I was waiting for this thanks a lot sfhub..:D

Also Have to do it sorry FIRST!!! hehe never have done it before.:p

I'll report any issues/improvements as soon as encounter them....

Report:

*Samsung added a new Bookmark widget. (first appears on FE14 I think so, if it's not new I noticed on FE14) lol

*Bookmark Widget Bug still present. urrrggh so annoying since I use that widget a lot and clear RAM several times on a day.

*Scrolling seems a lot smoother than before.

*FE16 modem performs a lot better than before.

*Chrome Beta still Locking up (Kernel related).

*Google Play Movies app added (First appearance on FE14). I think not sure

*Loop scrolling on widget selection feature added a few leaks back. (if you didn't notice).

*GPS locks way faster than before.

*Move to SD back and forth. Fixed!

*Notification light not pulsing while charging. Still present.

*Alarm Repeat selection. (New Selection Style).

*Alarm 10 Minutes Snooze Bug still present. (No alarm after First 10 mins)
[Samsung Epic 4G Touch] RainMotorsports:
Ill have the mirror up in a second im awake lol, screw the auto sync. I should be ashamed of myself :p
[Samsung Epic 4G Touch] sfhub:
Not sure if the sync got triggered but I had the sync file up about 30-45 min ago.
[Samsung Epic 4G Touch] RainMotorsports:
Its cool, sorry I haven't had time to fix the bug on the sync list download cache yet. I just woke up from a retarded worked schedule. I could have made it work but i figured its faster for me to just download them by hand for the moment as usual.

Files are up except the tars of course.
[Samsung Epic 4G Touch] wasscomedy:
Sweet tomatoes Batman! Thanks
[Samsung Epic 4G Touch] Ascertion:
Beautiful. Love ya, RainMotorsports and Sfhub. :)
[Samsung Epic 4G Touch] slick_rick:
Thanks sfhub, that was quick. Give your source a thanks from us also lol.
[Samsung Epic 4G Touch] humdrum2009:
As quick as these are being dropped we aren't far from ota.

I'll give it by the middle of June.
[Samsung Epic 4G Touch] robbyr:
NICE!

These builds have quickly become my go to! Thanks so much for your work on this! Can't wait for the plus repack!
[Samsung Epic 4G Touch] RainMotorsports:
As someone already said its not much of a sign. We have been getting them this quick for most of the leaks. Many many times they have been 2 days a part we even had 4 in a row?