yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
I believe it was someone else that said that about 3.2.6.3

but the fact is:

stock samsung wifi drivers all have a weakness that from time to time they tend to act up (maybe some buffer overflowing????) and this get worse with toggling.

You can reproduce the weakness by toggling the wifi on and off frequently in a short time. At one point it won't connect, and if you wait and toggle it again it will be normal again.

GM has patched these stock driver along the way, making it better and better.

I think as of 3.2.6 until 3.2.7.1 they were working great.

As of 3.2.7.2 he started experimenting with i9300 wifi driver and then they began hicking up again, even until now in 3.3.1.

I believe if he had more time he wil probably get that one working flawlessly also, but he's dedicating his time now to the sgs3 and maybe in time he will be back to sgs2 (I believe his intentions were to create one github from which he can compile to both sgs2 and sgs3 from same sources, but I'm not sure)..

so concerning wifi, it's just how you use it, if you rarely toggle, you'll have little problem with both versions. If you toggle a lot (maybe using some app), you'll definitly run into frequent non-connections with the i9300 drivers in their current state. Then I'll advise 3.2.7.1 down to 3.2.6.x with the older (patched) drivers

edit: just remember this part..the non-connection problems at one point also had something to do with the introduction of pegasusq, which made the device more hot-plug intensive than normal with other governors, and this was patched in 3.2.6.4 (together with the unlockscreen freeze bug)
[Galaxy S II Q&A, Help & Troubleshooting] :
Siyah 3.3.1

No OC or UV of CPU or GPU. Default profile for Siyah all the way, BLN enabled for calls, sms and whatsapp, autobrightness. Very sturdy battery perf for overall usage (calls, games, browsing, media etc.). No issues with wifi toggling either. Incidentally, I had gotten better results with 3.2.8.2, hehe, had no issues at all, for one complete cycle, though got a bit nervous reading all the posts, hence switched to the latest.
[Galaxy S II Q&A, Help & Troubleshooting] Oso Polar:
MaliStatus

I've created a tiny app that can display current Mali GPU stats on the recent Siyah kernels (AFAIK 3.2.7+). I've created it for myself in order to have some GPU stats and attempt to better tune GPU parameters in ExTweaks. Sharing with everybody, may be you'll find it useful.

Program is very simple, it is just an overlay on top of everything that displays current GPU voltage, frequency and usage. The only way to close it is to use task manager. After start of the app you'll need to press the "Home" button to move input focus away from the app, I don't know yet how to do this automatically, this is my first Android program. :o

BTW, I found out that kernel sometimes reports a different frequency then the one set in ExTweaks, e.g. if you set 40 MHz it'll tell that frequency is 50. This is not a bug in the program, this is what kernel actually reports.
[Galaxy S II Q&A, Help & Troubleshooting] Boat Traveller:
Thx a lot !

I turn the wifi on very rarely so I guess I'll can stick with the 3.3.1 for now.

But does anyone have a download link for 3.2.7.1 ? Just in case.

EDIT: Now that you have mentioned the Samsung wifi problem I remember that sometimes I tried to connect (with stock kernel) to a network but it couldn't. It showed authenticating and then nothing. I had to try a couple of time to connect.

Is that the problem you're talking about ?
[Galaxy S II Q&A, Help & Troubleshooting] Oso Polar:
http://xdaforums.com/showpost.php?p=27047682&postcount=1378
[Galaxy S II Q&A, Help & Troubleshooting] DigitalWarS:
vers. 3.2.7.2

Instaling only kernel over original Sam fw withouit wipes gave me lot of troubles (overheating, restarts), so watch out when istalling if u don't want to wipe...
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
answer to your edit: exactly...that's the weakness. It will connect after a few toggles, but for me that's buggy.

I have my data connection always off, and use 'tasker' app to program the device's behaviour. Tasker knows when I'm home and turns wifi on every 15 min. and syncs. When I'm away, it turns mobile data on every 15 min.

That way I always have connectivity (getting messages and mails) without having data connections always active (saves battery...)

I get a notification (sound) if it can't connect wifi in over 30 sec.

That's why it's important to me. I can program tasker to work with the other drivers, by checking, and maybe toggle a few times until it gets connection, but that's a bit inefficient.
[Galaxy S II Q&A, Help & Troubleshooting] bgx:
Great! But for me it seemed not to work; Stays all the time with the stock settings 160mh and 950mv.

Im on 3.3.1 and the last CM9 ver...

In extweaks I have 44,133,266 mhz and 800,850,950 mv.
[Galaxy S II Q&A, Help & Troubleshooting] Many40:
It works for me. I am using following GPU settings: 100, 160, 267 / 900, 950, 1000. Just after opened the app had similar issue like you (the app was stuck at 160MHz/1000mV what is wrong according to my setup but after a while it started working properly.
[Galaxy S II Q&A, Help & Troubleshooting] Goooober:
Sorry if this problem has already been mentioned but im a rush to go out so cant search for it.

I'm running 3.2.8 on Wanam V12 but BLN is not working. I have enabled it in Extweaks and done a test which works but when i actually receive a txt or whatever there is no BLN.

I was using the same Kernel version on Hydrogenics and BLN worked fine so i dont know what im doing wrong.
[Galaxy S II Q&A, Help & Troubleshooting] Radras:
Hello fellows,

I´d like to know if there´s any way to eliminate that Siyah logo from the initial boot screen.

Thanks in advance
[Galaxy S II Q&A, Help & Troubleshooting] MyLifeRocks10:
Create .nobootlogo file in ur sdcard.
[Galaxy S II Q&A, Help & Troubleshooting] Many40:
Create a file: "/sdcard/.nobootlogo". If this file exists no boot logo will be displayed.
[Galaxy S II Q&A, Help & Troubleshooting] CRudner:
eMMC Brickbug

Hi There,

I am just checking to see if anyone knows if Siyah Kernel 3.3.1 would be affected by the eMMC bug.

https://plus.google.com/117962666888533781522/posts/YPDxnye6rEw

I have used the app the checks and my one has this issue.

As they say in the link above if the Kernel has "MMC_CAP_ERASE" in the code then we at risk.

Can anyone confirm if this is in Siyah Kernel?

Should I just stick to Cyanogen Kernel or is Siyah Kernel safe? (I am currently on Siyah 3.3.1)

Thanks
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
Siyah is safe, its all over the threads. ;)

Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
[Galaxy S II Q&A, Help & Troubleshooting] CRudner:
Thanks for the quick reply, i was having a mini heart attack at work :-P

Thats great to know.

Thanks again!
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
No worries mate, have fun flashing. I advise v3.2.7.1. :)

Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
[Galaxy S II Q&A, Help & Troubleshooting] Oso Polar:
MaliStatus doesn't have any default values hard-coded. And it doesn't have any complicated calculation logic either. Application only changes µV to mV (e.g. 900000 => 900) and calculates percentage of GPU usage because original values are in the 0-255 scale (e.g. 77 => 77/255*100 = 30.2%). So, if you see that GPU usage still updates this means that application is not frozen and clock with voltages are updated as well and they show what kernel actually reports.

But I myself had a similar experience with discrepancy between ExTweaks settings and kernel values. My observation is that ExTweaks values are *NOT* applied immediately, in particular kernel will never change current frequency or scale to a lower frequency after ExTweaks changes. So, for example, I had 100/160/267 and my phone was currently using 160. I'm changing this to 40/160/267 and changing voltage for the steps. Kernel will not go down to 40 and it will not apply new voltages immediately. I think that it'll apply them only after scaling to the max frequency (267 in this case). For me running NenaMark2 after changing the settings in ExTweaks was always producing the desired results - after exit from the benchmark settings are always applied.
[Galaxy S II Q&A, Help & Troubleshooting] coloxim:
Gm is gone..

Ciao ciao...

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Q&A, Help & Troubleshooting] Ok_Kaleidoscope5109:
what kernel would you guys jump ship to now that development for Siyah is dead?
[Galaxy S II Q&A, Help & Troubleshooting] Ankit Tulsian:
I dont think there is a need to jump to other kernel as GM said he will stabilize the kernel and GM has got almost everything related to dual booting working and its quite stable.
[Galaxy S II Q&A, Help & Troubleshooting] Ba7rani123:
Finally some news about stabilizing the kernel :), I hope its really son because I feel 3.3.1 is battery draining for me and wifi I had no issues at all I felt no change, but I got corruption with 2.3.8 :( and I lost some data
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
Dump your BetterBatteryStats log here. I'll take a look at them. So far 3.3.1 is pretty battery saving for me. Having a 25MHz - 1.2GHz sure helps a lot with ThunderBolt!'s configuration for pegasusq as well.

I'm getting 18 hours uptime with 2 and half hours display time with HSDPA and Wifi (50/50) connected all the time.
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
why so depressed:confused: he's done a great job with what he left us with...

and if you're a bit adventurious and have a bit of knowledge of linux, there's a lot to discover underwater ( and to configure even more....:) )

just dive in!!...
[Galaxy S II Q&A, Help & Troubleshooting] baza14:
There is something wrong with accelerometer. :(

Odesláno z mého GT-I9100 pomocí Tapatalk
[Galaxy S II Q&A, Help & Troubleshooting] 11768:
What voltage value are you using for 25Mhz, 50Mhz, and 100Mhz?
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
I'm only undervolting 25MHz to 850mV due to the lack of time to find stable values. If I find time, I'll undervolt more, though I won't post the values here as its pointless. You have to find stable values yourself. No two phones will have the exact stability in certain volltage values.
[Galaxy S II Q&A, Help & Troubleshooting] :
Post here just as a reference. For sure it won't be stable on others phone, or it can be lowered even more. We can use your values to see if a voltage is high or low. If the phone crash we +25mV. If it's fine we -25mV. So posting your undervolting here isn't pointless :)
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
It is actually. A lot of n00bs will come here, not knowing all about undervolting and then applying my values. After that come screaming in the dev thread about SODs and kernel panics. It's bad.
[Galaxy S II Q&A, Help & Troubleshooting] alvin.durant:
Can you please share us your configs GOV/IO sched and mild to heavy undervolting on the latest siyah kernel?
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
You can download ThunderBolt! for the pegasusq settings as I use governor tunable scaling (good performance while screen is on and battery saving while screen is off).

Pegasusq/SIO. Won't share any undervolting. I can share how to undervolt though.

Undervolting:

Reduce your min/max frequency to the one you want to test (e.g. 200MHz. It'll make your phone slow down to 200MHz and cause lags though, don't worry about this we're just testing).

Reduce your voltage by 25mV.

Play an MKV file using software decoding in MX Video Player (or any video player) for 10minutes.

If it doesn't hang, reduce some more, until it hangs.

Add +25mV

Go to the next highest frequency (e.g. 300MHz)

Note: Hangs might cause higher risk of data (as in /data) corruption. Just a note. Be sure to backup.
[Galaxy S II Q&A, Help & Troubleshooting] nikha:
Possibly bricked my phone

I am on cm9 + siyah 3.2.8.Phone is AT&T Samsung Galaxy S2 (SGH I-777) Everything was working fine until I used Rom Manager to take back up of existing cm9 rom and looks like my phone has bricked.

Here is the state of it:

1) When I try to start it, I see the samsaung (with yellow triangle in my case) and then, the phone stop.

2) When I try to go into recovery mode vol up/down, power, It gets me to samsung but logo and then the screen goes blank.

Any sort of guidance on recovering highly appreciated.
[Galaxy S II Q&A, Help & Troubleshooting] Ba7rani123:
siyah 3.2.8 has bug where it causes corruption ;) hpnd to me too, it only boots to download so first flash a new rom and siyah 3.3.1, do a backup using titanium backup but dont reboot, then wipe everything and install a new kernel like siyah 2.6.4 or something in the 2.6.x range which is the most stable :) for me and many people

Thats what I did and it worked for me :D
[Galaxy S II Q&A, Help & Troubleshooting] Ba7rani123:
Which rom ? am using XWLP7, rom effects performance too :/
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
Pure XWLPG stock odexed.
[Galaxy S II Q&A, Help & Troubleshooting] vertrag:
Thank you master pikachu..:D btw about the governor smooth scaling (jump to the highest freq) there's restriction that cpu spike is min at 800mhz is it okay to test under such condition.. :S I mean is there any guarantee that the jump to the highest freq wont occur when i test (e.g. min 100mhz and max 100mhz).
[Galaxy S II Q&A, Help & Troubleshooting] egps2:
Benefits of aftr with dual core?

Hi does anyone know if AFTR idle mode is still beneficial with the the pegasusq governor which favours dual core mode? I understand that if the second core is active (almost always with pegasusq) then the AFTR/LPA can not be entered and only normal IDLE can. Does this mean IDLE+LPA would be better with pegasusq since IDLE can still be entered where as AFTR cannot until the second core is powered off? Even though IDLE is not as good as AFTR?

Also, I found that when I tweak the cpu, the performance can vary wildly but the battery will always be 3-4 hours screen on time as if the cpu doesn't even matter! Also, even with heavy under clock etc etc my battery will NEVER touch 5 hours let alone the 7-10 hours screen on time I have seen posted around here!

TL;DNR: Is IDLE+LPA better than AFTR+LPA since IDLE can be entered in dual core (which pegasusq likes) but AFTR cannot?

Thanks for any suggestions and if anyone reads this please just quickly mention typical screen on time at the bottom of your post (eg sot: 4hrs) :) thank you all kindly.

Another note: If I lock cpu freq to any value then it will accept HUGE undervolts (eg 900mv for 1200mhz) but will crash if the frequency can scale like normal. Almost made me consider locking 1000 at 850mv! Anyone else seen this?
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
That bug was fixed in the past few versions (don't remember which).

The deep sleep will only occur while your screen is off anyways. Hence, it doesn't matter what governor you're using. If there's no activity, dual core will be switched off (yes pegasusq will go single core when load is low.).

Yes, switching frequencies can sometimes affect undervolting also. It due to the nature of switching that undervolting isn't stable.
[Galaxy S II Q&A, Help & Troubleshooting] mekhonte:
I dunno whether GM is following Emmc lockup thread our not.but seems that they have found A possible workaround for the famous super brick.
[Galaxy S II Q&A, Help & Troubleshooting] egps2:
Hi I knew about deep sleep but does this mean IDLE, LPA and AFTR are also only used during deepsleep? If so then it would not matter as dualcore mode is disabled during screenoff. I though these were used during screen on as well to save power? And I know pegasusq does hotplug out the cpu but I thought that IDLE/AFTR/LPA could be used when the screen is on too (eg when there is SOME but not much cpu load) but maybe I was mistaken?

Thanks for your help, pikachu01 :)
[Galaxy S II Q&A, Help & Troubleshooting] mekhonte:
Delete.
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
that's one of problems with undervolting

finding the stable voltages per freq. is one thing

but....

jumping from freq. to freq. needs the cpu voltage driver to react just as fast to accomodate the jump, and as all systems it has it's latencies, so the voltage jump needs to be in accordance with the freq. jump and this the hard part in finding the right combination for undervolting

you might find a good combination (you think...) , until you use that 'other' app demanding more performance (and jumps...) and ...voila...crash!

so it's a nice hobby, undervolting, but it could drive you mad also...:D:D
[Galaxy S II Q&A, Help & Troubleshooting] egps2:
That makes a lot of sense! Do we know what the latency is for the voltage regulator/jump etc? If we know that we can tune the governor sampling rate for optimum stability (eg 100000>50000>>20000?). I am very temped to test 800mhz at 800mv locked and see how that compares. I think so far that AFTR/LPA will help save power when all 800mhz is not needed but I am still not sure if they can work when the screen is on?

Thanks for your replies everyone :)
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
Those states are CPU states akin to Intel C-states where it cuts off power to the CPU in stages to reduce current leakage. Yes, they only occur while the screen is off. There's not much documentation I can find about LPA/AFTR/IDLE (probably mostly from source code) but google up Intel Cstates to find out more about power gating/clock gating etc.
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
Sampling rate is not the latency you're looking for (though it does help accelerate boot hangs when doing massive undervolting). Even when you have a high sampling rate, the point of ramping/switching voltages is the one causing the hangs, not how frequent it does it (but the more frequent it is, the higher the chance of it hanging).
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
.mmm...I don't think you can compensate for the latencies using the governor's settings ; it's regulated on a much lower level in the kernel (maybe you change that with some parameter, but I wouldn't venture to go there...)

If I may suggest : just a moderate, even spread undervolting will work okay

trying to seek the outer limits ,is in a way pointless...there's little to gain concerning powerconsumption compared to just a moderate undervolting
[Galaxy S II Q&A, Help & Troubleshooting] egps2:
Ok so then these idle modes should make no difference when screen is on? This is strange to me because I heard AFTR could cause stuttering / other issues for some people. This would mean the idle modes make no difference to screen on time if your phone has screen on 100% (unrealistic I know). Also, I find the c6 vs c3 c-states help lower idle (screen on) temperatures for my i7 870? But this may be different since multiple cores can be powered on and off?

Ok this makes sense. My line of thought was that maybe a high sampling rate will help improve stability as the voltage driver latency would not be lower than the sampling rate although I heard the cpu frequency switching rate is something like 100us! I only have moderate -50mv uc and stock at 500mhz usually anyway.

---------- Post added at 05:44 PM ---------- Previous post was at 05:30 PM ----------

Thank you for that. This is what I thought anyway and have been using a modest uv for stability but I was very curious about how these changes would affect the battery drain especially seeing that some people have been posting screenshots with 7-10 hours screen on time and I have a modest 3-4 no matter how aggressively I 'save' power!

My biggest question I guess boils down to the effectiveness of AFTR vs IDLE when the screen is ON but apparently they are not used when the screen is on which suprises me as I though that they would be very useful to save power on an idle system say while reading a webpage when a phone was semi idle. I also heard a lot of information about RACING TO IDLE where (while the screen is on) it's good to have the system race up and then down again to sit in a semi-idle state using these power saving features. Also with the whole 100-200mhz debate I heard idle states mentioned as to why 200mhz at 50% enters idle states more but then again somone on a Siyah thread said 100mhz is still better? It is very easy to get confused with lots of conflicted information surrounding hardware concepts I do not understand well!

I like most people just want to make sure I am being as effectent as possible and for me so far I believe that is SMALL undervolt, 200-1000mhz and AFTR+LPA :) - but still I see these skeptical screenshots of 7+ hours screen on times and even other articles saying 8hours screen on watching videos on STOCK!

http://blog.gsmarena.com/our-samsun...e-test-is-complete-check-out-how-it-did-test/

Just me or are we missing something? Or am I the only one with this poor 3hours screen on time? Faulty battery?

Sorry for the long post and thanks again for all your help :)
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
The Cstates you're talking about are Core C-states, I'm talking about processor C-states (or package C-states) where the whole package is not doing anything rather than some cores in the package doing something while others are idling.

The AFTR and LPA are package C-states while IDLE should be a core C-state(someone correct me if I'm wrong).

I'm not sure about the voltage driver latency, though there's not much point delving into it since the ROI isn't that high anyways.
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
A lot of people are getting 7 hours to 9 hours screen on can be using 2000maH batteries or being fully disconnected from wifi and data connection (yes it's doable). I have an SGS running 1600maH that has a battery life of 3 1/2 days with wifi being turned on for 12 hours per day and no data connection (no Facebook, Google+, Whatsapp etc as well) and about 2 hours of screen time.

Also, from what I read about IDLE is that the core is essentially clock gated. I'm not sure how ARM handles clock-gating, but nothing can be processed if it's clock-gated, even the timers that govern the screen off process when it's time to switch off the screen (unless that timer is off-package, which is highly improbable).
[Galaxy S II Q&A, Help & Troubleshooting] Ba7rani123:
look at this screenshot, before on XXLPQ when I turn on music it stayd for like an hour and then it falls only by 1%, now its just draining my battery away :(, anyway I stopped using siyah since v2.3.8 data corruption so am gona wait for the next stabilized version :).