yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] bokil:
For Primary ROM, there is a seperate option to wipe data and cache.

For Secondary ROM, i saw there is wipe data/cache.

Is it possible to wipe just the cache for secondary ROM and not the data?

Thanks
[Galaxy S II Q&A, Help & Troubleshooting] BrandoHD:
I see your patience is growing thin, which is not good, I think you need to use you ignore button to avoid the repeat offenders of useless posts, e.g the Eric Filth individual, he makes those useless posts in many kernel threads, do what you needs to do to alleviate some of the stress on yourself GK, before your patience no longer exists

Also, if you do see useless posts, just ignore them and move on, you cannot be responsible for providing explanation to all with incorrect information, we are not your students
[Galaxy S II Q&A, Help & Troubleshooting] gokhanmoral:
everything has its limits.

I can still be patient to noobs and all nontechnical questions.

but when people are ignorant to the answers and requests it does not deserve patience.

I still do not humiliate people or insult in any way.

I tell them that their point in the development thread is pointless.

in this thread, they can ask just anything and I will answer some (or sometimes most, if I have time) of them.

and this change is not only my choice but also the request of other users who are not as patient as I am. a lot of people are very disturbed because of the unnecessary traffic in the development thread.
[Galaxy S II Q&A, Help & Troubleshooting] bleuxeon:
I have used SetCPU to tweak Pegasusq governor sampling but settings are reseted at each reboot:confused:

Could it be due to the "beta" nature of Siyah's Pegasusq?

or is it simply a known bug in SetCPU?
[Galaxy S II Q&A, Help & Troubleshooting] gokhanmoral:
it works with scripts, so it is either setcpu or you are missing a "set-on-boot" checkbox.
[Galaxy S II Q&A, Help & Troubleshooting] bleuxeon:
the "set on Boot" is ticked for "main", "voltage" and "governor" tabs but governor seetings are lost after reboot.
[Galaxy S II Q&A, Help & Troubleshooting] :
uncheck "set with profiles" and "set on boot" then recheck, reboot and it should work.
[Galaxy S II Q&A, Help & Troubleshooting] bleuxeon:
I have bypass this bug by creating a profil active when battery < 101% = 100% of the time:D
[Galaxy S II Q&A, Help & Troubleshooting] zedamalta:
Hello hello

The last update Siyah v3.2.4 [ICS] works on Checkrom v6 GB based?

Thanks for all
[Galaxy S II Q&A, Help & Troubleshooting] runedrune:
You answered your own question. Why would an ICS kernel work on a GB rom?
[Galaxy S II Q&A, Help & Troubleshooting] naveediftikhar:
@andreilux...reply to a comment he made on my post in development thread!

you are right..but it works for me..very minimal lags...very little that barely noticeable and it works so well that my phone spends as much time on 1000mhz(my max freq) as it would normally spend on 700 or 600..trust me...i got a heavily undervolted gpu..100-1000 cpu with heavy uvs aswell...so its pretty clear that iam after battery life with performance aswell..and pegasusq give me that atleast so for like hell....but andre it would be great if u can try it out for me n tell me if theres any other con to it than jus little tiny miny jerks...!?

heres my extweak setting and a script that i use!

extweak:

GPUFREQ1=66

GPUFREQ2=100

GPUFREQ3=160

GPUVOLT1=800

GPUVOLT2=800

GPUVOLT3=800

GPUTHRESHOLD1UP=85

GPUTHRESHOLD2DOWN=75

GPUTHRESHOLD2UP=100

GPUTHRESHOLD3DOWN=75

GPUSTAYCOUNT1=2

GPUSTAYCOUNT2=2

GPUSTAYCOUNT3=1

min_bl=150

min_gamma=0

max_gamma=12

rate=250

enable_mask=3

sched_mc_power_savings=1

chargecurrent=2

logger=off

secondcore=hotplug

scheduler=cfq

scaling_governor=pegasusq

load_l1=30

load_h0=35

load_rq=35

min_rq=2

freq_min=800000

install_root=on

mov_hysti=0

suspend_freq=500000

vibrator_level=0

user_gamma_adjust=-10

blnww=off

cpustepcount=18

notification_enabled=off

notification_timeout=0

led_timeout=1500

bln_effect=0

touchkey_brightness=2650

led_fadeout=on

led_on_touch=on

cpu_undervolting=0

script :

#!/system/bin/sh

echo "95" > /sys/devices/system/cpu/cpufreq/conservative/up_threshold

echo "120000" > /sys/devices/system/cpu/cpufreq/conservative/sampling_rate

echo "1" > /sys/devices/system/cpu/cpufreq/conservative/sampling_down_factor

echo "40" > /sys/devices/system/cpu/cpufreq/conservative/down_threshold

echo "10" > /sys/devices/system/cpu/cpufreq/conservative/freq_step

echo "95" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold

echo "140000" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate

echo "1" > /sys/devices/platform/samsung-pd.2/mdnie/mdnie/mdnie/user_mode

echo "130" > /sys/devices/platform/samsung-pd.2/mdnie/mdnie/mdnie/user_cb

echo "130" > /sys/devices/platform/samsung-pd.2/mdnie/mdnie/mdnie/user_cr

echo "750000 750000 800000" > /sys/class/misc/gpu_voltage_control/gpu_control

echo "NO_GENTLE_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features

echo "5" > /sys/devices/system/cpu/cpufreq/ondemand/down_differential

echo "0" > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias

echo "120000" > /sys/devices/system/cpu/cpufreq/pegasusq/sampling_rate

echo "95" > /sys/devices/system/cpu/cpufreq/pegasusq/up_threshold

echo "1" > /sys/devices/system/cpu/cpufreq/pegasusq/sampling_down_factor

echo "5" > /sys/devices/system/cpu/cpufreq/pegasusq/down_differential

echo "1" > /sys/devices/system/cpu/cpufreq/pegasusq/freq_step

echo "600000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_1_1

echo "1" > /sys/devices/system/cpu/cpufreq/pegasusq/io_is_busy

these settings give me a brilliant balance..but are these healthy...that my question?
[Galaxy S II Q&A, Help & Troubleshooting] bokil:
Can someone answer me?....or the question itself is wrong?

With primary ROM, I used to wipe cache, wipe dalvik cache, install zip (rom or kernel...etc), wipe cache, wipe dalvik cache, reboot system....these steps worked well.

Now with secodary ROM i cannot find wipe cache...i can see wipe data/cache...which wipes data and cache both (hopefully).

So, i wanted to know is there a way to wipe just cache.

Thanks.
[Galaxy S II Q&A, Help & Troubleshooting] starworld:
Nobody has a problem with the CPU?

set to 200 max. but displays a certain time 800.

(before 3.1.2 not bug)
[Galaxy S II Q&A, Help & Troubleshooting] runedrune:
No there isn't.
[Galaxy S II Q&A, Help & Troubleshooting] runedrune:
You can't set max frequency less than 800. Not a bug. Why would you want to anyway?
[Galaxy S II Q&A, Help & Troubleshooting] :
Well... I don't know about you, but I sure can.
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
as far as I can remember, the changelog for 3.2.7.1 was exactly the same as for 3.2.7.2 ; the only difference is

3.2.7.1 old wifi drivers (for me the good ones...)

(was on the blog download for maybe less than an hour...)

3.2.7.2 i9300 wifi drivers (for me ok, but a little bit buggy...has trouble connecting sometimes)
[Galaxy S II Q&A, Help & Troubleshooting] Simonetti2011:
Exactly. I have no idea why he assumed both devices would have the exact same wi-fi hardware or why the I9300 drivers would be better.

The latest stock drivers are excellent. Wi-fi with Siyah sucks.
[Galaxy S II Q&A, Help & Troubleshooting] runedrune:
Use the latest. The changes were reverted.
[Galaxy S II Q&A, Help & Troubleshooting] Syrus01:
First Post, first sentence:
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
I would go with 3.2.7.1 if you're having wifi issues

...it's the latest, best one for now

you can download from link : see some posts earlier....(courtesy of geko95gek)

---------- Post added at 02:40 PM ---------- Previous post was at 02:38 PM ----------

afaik, 3.3 and 3.3.1 are still using i9300 wifi driver

tested it, doesn't work for me....
[Galaxy S II Q&A, Help & Troubleshooting] KennyLegend:
Wrong. Latest 3.3.1 has i9300 latest source Wi-Fi drivers.

Also, 3.2.7.1 has i9300 wifi drivers guys. You'd have to go back as far as 3.2.6.4 (lock screen bug fix)
[Galaxy S II Q&A, Help & Troubleshooting] runedrune:
Yeah I just checked. The changes related to Wi-Fi drivers weren't reverted but all other merges from N7000 and I9300 sources were reverted.
[Galaxy S II Q&A, Help & Troubleshooting] Oso Polar:
3.2.6.4 has broken TriangleAway support. The only kernel that fixes just this single problem and doesn't add anything new was 3.2.7 that was never even published :(

Does somebody have a link to it?
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
I'm not completely sure (I'll have to dive into the github and trace that), but as I remember 3.2.7.1 had the same wifi driver as 3.2.6.4 (see changelog) and at the last minute GM decided to use i9300 driver and made it 3.2.7.2, which is why 3.2.7.1 was only up for about an hour....

doesn't matter really...the fact of the matter is 3.2.7.1 works great for me and much better than 3.2.7.2 and 3.3 or 3.3.1....so that's going to be my kernel for now

---------- Post added at 03:12 PM ---------- Previous post was at 03:08 PM ----------

3.2.7 was a build made by GM for Turkbey to use in his rom.

if you want to use that one, you'll have to download Turkbey's rom and extract the zImage from there

Tried that back then, the only downside was you will get Turkbey's bootlogo with it and for some reason it didn't auto mount my sd card (but maybe I did something wrong)
[Galaxy S II Q&A, Help & Troubleshooting] xavihernandez:
Hi peeps I know network connections are modem related but someone may have an answer on that: do you have troubles while switching from 2G only to 2G/3G? Sometimes it happens well, and sometimes it simply connect to Edge only even.GPRS and then cut data connection, then try again to connect 3G and fails again, it loops like that until it connects 3G or until I lose my patience and enable/disable flight mode. Even flight mode takes long time to be enabled in those period of troubles. I try to go to Phone Informations via *#*#4636#*#* on dialer but there is no info on data connection (while there was info before on GingerBread).

Dunno if someone else faces the issue or knows how to fix it. Any info will be good to read thank you!
[Galaxy S II Q&A, Help & Troubleshooting] toxicbubbles:
Not so sure about this as I'm on 3.2.7.1 now and wifi is working fine now, so guess the change to 3.2.7.2 must have been the addition of the i9300 wifi drivers.

Any ideas for a work around to use the latest kernel but with the stock wifi drivers or would this require recompiling the kernel?

Thanks to geko95gek for posting the link
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
you'll have to recompile....
[Galaxy S II Q&A, Help & Troubleshooting] predatorftp:
so what your saying is that i need to flash Syiah right after (without rebooting the device) using ODIN ?

1. Clone 1st rom to 2nd rom

2. Flash using ODIN the ROM (.tar)

3. Do not reboot the device

4. still using ODIN Flash the Syiah Kernel.

5. Reboot the device ?

is this the procedure to follow ?

I really don't want to wipe my device. (if i can help it).
[Galaxy S II Q&A, Help & Troubleshooting] Happy_Jack:
Yes, most definitely. I have only ever seen kernel panics when under-volted.
[Galaxy S II Q&A, Help & Troubleshooting] KennyLegend:
3.2.7.1 has i9300 drivers also but the difference is 3.2.7.2 has wifi driver source updates. Maybe its this update that is giving people grief.
[Galaxy S II Q&A, Help & Troubleshooting] Fed03:
many thanks:)
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
it's not mandatory, to flash directly after the rom, but booting after only the rom resulted in a bootloop or stuck on bootlogo (if I recall correctly?)

even after the bootloop you can still go back to download mode and flash siyah

if the bootloops are caused by some incompatability, this might help

but...have you by any chance been using version 3.2.8.x? 'cause the problems could have been caused by that version

(normally doing complete wipe (system,data,cache,dalvik) and proceeding with a totally different rom including it's own kernel (which fits in the standard partioning as on the device) doesn't ussually cause this)

if yes, read the last 10 pages or so of this thread, and you'll find enough suggestions how to deal with it...

you will have to wipe at least your data partition I'm afraid.....'cause that's where the problem probably lies....
[Galaxy S II Q&A, Help & Troubleshooting] predatorftp:
I'm using 3.2.8.2+.

So I will try to flash the ROM with ODIN (Original Operator ROM) and then i will right way flash the Syiah (latest one) with ODIN.

If it doesn't help then I will have to actually read the 10 pages you talked about :)
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
ok..thanx for the info ; then that should the source of all evil for the ones of us doing really crazy things with our wifi :D:):D
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
..won't hurt to try...but I'm pretty sure 3.2.8.2 is the problem now you've confirmed that....and you'll get the same result : not good

boils down to (if you're going to install another rom anyway) to formatting (wipe) your data partition and more importantly :

go for one of the other versions of siyah (not 3.2.8.x)

---------- Post added at 04:48 PM ---------- Previous post was at 04:41 PM ----------

does this mean you're still on 3.2.8?

what the exact problem with the whole range of 3.2.8.x version is, is not clear, but this could be a result of it....(which is not normal...)

(i think 3.2.8...wasn't removed from the download blog without a reason....)
[Galaxy S II Q&A, Help & Troubleshooting] predatorftp:
I'm flashing 3.3.1 as we speak, lets see if this helps solve the problem...
[Galaxy S II Q&A, Help & Troubleshooting] Tungstwenty:
No.

Right after experiencing the fs corruption with 3.2.8.2, I figured out how to recover to a working state - flashed 3.2.8 and restored /data from a nandroid. Worked fine after that, since. (I thus have the feeling that only 3.2.8.2 had the problem, or if 3.2.8 also did, I somehow didn't trigger it :))

Today I decided to do the "proper cleaning", even tough it was all running fine, and followed those steps (roughly what I did before) while migrating at the same time to 3.3.1.

It's all running fine as before, so my doubt is related to a) the "... different major ..." messages and b) the fact that e2fsck gives lots of errors but the fact is that it mounts RW and everything is fine.
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
...did some research, but my knowledge doesn't go as deep yet

all I can tell is there's probably some remapping being done, but the partitions (8-12) eventually do get a handle assigned (but in a different range) and are accessible, so I don't think that's a problem

as to e2fsck, I'm not that familiar with that, just that it's intended for to check parittions with an ext2/ext3/ext4 format and I assume the partitions are in that format, otherwise that would explain all those errors (would be great if it would just say : this is not an ext2/ext3ext4 part, but I don;t know if it does ; it should if it's programmed right)

all in all, if it's working ok, just be alert for things out of the ordinary

in the mean time I'll keep my device under a close scrutiny, for any problems

if it is a problem, we all have it by now, but I don't think it is.....
[Galaxy S II Q&A, Help & Troubleshooting] Tungstwenty:
Precisely what I thought about the partitions, but the fsck thing still puzzles me :confused:

I'm checking the logcat and the experience frequently :) so any issues will remind me of this vector if they are filesystem related.

Thanks!
[Galaxy S II Q&A, Help & Troubleshooting] kehinde:
revert color inversion?

does anyone know how to revert the color inversion use for saving battery life in web browser(making the background black)? i really dont want to be pressing the home key 4 times after every boot.

maybe i could comment out the code or something.

thanks.
[Galaxy S II Q&A, Help & Troubleshooting] pilgrim011:
I have the same problem, but don't have any solution...

Wrong, mate. 3.2.7.1 was the last version with old wifi drivers, but it was online for a very short time:

3.2.7.1 was the first version with negative mdnie effect.
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
Don't understand exactly what you're asking : I interpret it as if your device is booting up with inverted colors everytime, and you have press home button 4 times to get it back to normal colors?

If that is the case, you probably have some script (in init.d folder) setting that at boottime, and you can just delete the script or move it somewhere else where it's not referenced.

If you mean how to toggle inverted colors without using the home button, but with scripts :

echo 1 > /sys/class/mdnie/mdnie/negative

for inverted colors

echo 0 > /sys/class/mdnie/mdnie/negative

for normal colors

edit: just thought of /sbin/ext/tweaks.sh, but there's nothing there regulating negative colors, so it's one of the above....i think

---------- Post added at 09:02 PM ---------- Previous post was at 08:44 PM ----------

Whoever is right isn't so important (maybe just for the knowledge),

I've been back and testing 3.2.7.1 all day now and it's wifi actions are superb

(I toggle my data connection automatically every 15 min. and synching, and it did it excellently today connecting everytime within 5 sec. [3 mostly] , so I'm happy :p:):D:o)
[Galaxy S II Q&A, Help & Troubleshooting] KennyLegend:
Look at the screenshot I just took from Gokhans site. the info here is from 3.2.7.1. The bit added at the bottom (update 1/6) was just for 3.2.7.2.

Which means he used i9300 drivers on 3.2.7.1 too but updated them in 3.2.7.2. I remember it was mentioned the same say.
[Galaxy S II Q&A, Help & Troubleshooting] pilgrim011:
Nope, but I understand why you think so. Just read his posts - first time that he mentioned i9300 wifi drivers was when he announced 3.2.7.2. For example:
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
I think the only one who can give a definite answer is Gokhan himself.

Circumstancial evidence is pointing to : old drivers in 3.2.7.1:

refer to:

http://xdaforums.com/showpost.php?p=26815593&postcount=967

pointing out a new feature, namely negative color-feature for browsing

refer to:

http://xdaforums.com/showpost.php?p=26818411&postcount=974

about an hour later pointing out the new drivers from i9300

fact is the kernels datestamps are

3.2.7.1 31.05.2012 22:13

3.2.7.2 31.05.2012 23.37

I just went through his github, but couldn't find a definitive answer, because all changes were made on the 31st and no time record is mentioned anywhere (at least I couldn't find one)

The only clue is the last two ones were :

i9300 driver merge

and

a little tweak on pegasusq from i9300 sources

https://github.com/gokhanmoral/siyahkernel3/commits/update4-3.0.y?page=3

which does suggest these were the last minute changes of the day

which would suggest only 3.2.7.2 has them, but it's not hard evidence...

so maybe Gokhan could enlighten us someday ?? :)
[Galaxy S II Q&A, Help & Troubleshooting] KennyLegend:
Maybe I read it wrong... anyhow it doesn't really matter. My wifi seems to be ok... a little slow connecting when i come back in range of my router but other than that its fine. I have 3.2.7.1 if I need to flash at some point.
[Galaxy S II Q&A, Help & Troubleshooting] Tye:P:
I noticed that you're using CM9, are you using a recent build?

I've had problems with the toggle for this since the beginning of CM9 (I think it was a known issue for awhile there), but it seems to be working in the recent builds. It's working for me in the 20-05-12 build.

edit - I am also using LPS modem (the best for me so far along with LP6 - Vodafone/Melbourne, Australia)

Different strokes for different folks goes without saying here though.

Re-flashing your modem and/or toggling airplane with a reboot might be worth a shot.
[Galaxy S II Q&A, Help & Troubleshooting] xavihernandez:
Actually I'm using build 20120603. This issue appears for longtime, I thought I found a way to do by disabling data the switch and enabling data again but it sometimes fails. It's really random.
[Galaxy S II Q&A, Help & Troubleshooting] bundi22:
What exactly is the process when you select swap primary and secondary rom?
[Galaxy S II Q&A, Help & Troubleshooting] karlesg:
Those of you who have issues with wifi, did you have similar problems with 3.2.8.x versions? For me at least I think the best performing wifi drivers until now were these of the 3.2.8.x versions.

So beside the problems with data corruption, bootloops etc, what do you think about wifi drivers of 3.2.8.x versions? did you have any issues with them?
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
I was on 3.2.8.2 for a while, and had very little issues with wifi, so I think the drivers in that configuration are good.

I chose to move to another version, because of underlying problems, not knowing exactly where they originate, and not knowing what the effect could be in the long run.

Tried 3.3 an 3.3.1, but the wifi drivers didn't work 100% for me, so the next best thing was 3.2.7.1, and that one is ok.
[Galaxy S II Q&A, Help & Troubleshooting] greenemperor:
I am looking for the Siyah 3.2.6.3 so please provide me a link to download.

Thank you!
[Galaxy S II Q&A, Help & Troubleshooting] LegendZenify:
Here you go!

http://gokhanmoral.desean.net/siyahkernel/v3.0/Siyah-v3.2.6.3-CWM.zip
[Galaxy S II Q&A, Help & Troubleshooting] tintoverano:
l2_hsic wakelock

hello guys,

I'm using the latest release on Pure ICS ROM and this is the first time I see this wakelock: l2_hsic and it drains battery like hell.

Any idea where does it come from?

thanks a lot,

tinto

Found something here: http://xdaforums.com/showthread.php?t=1656705&page=5
[Galaxy S II Q&A, Help & Troubleshooting] Lady_Chloe:
I am using Spike pure ICS too, that wakelock comes directly from the kernel, you just need to choose a different Siyah version.
[Galaxy S II Q&A, Help & Troubleshooting] vizdak:
that wakelock is from note sources. use the 3.3.1 siyah kernel.
[Galaxy S II Q&A, Help & Troubleshooting] greenemperor:
Just followed your preference and replace the 3.3.1 with 3.2.6.3 and the wifi is way better..
[Galaxy S II Q&A, Help & Troubleshooting] tintoverano:
Thanks, actually I thought I was on it because the prev version gave the FCs as to everyone, but somehow I wasn't.
[Galaxy S II Q&A, Help & Troubleshooting] Rawi666:
I miss gokhanmoral pushing new kernels every day :(

I'm on holiday at Baltic Sea and I thought I would flash something from time to time :(

WTB gokhanmoral back :(
[Galaxy S II Q&A, Help & Troubleshooting] rlorange:
Tegrak OC app now supports Siyah kernel!

Apparently we can set GPU to 300mhz using this app
[Galaxy S II Q&A, Help & Troubleshooting] Boat Traveller:
What do you mean the wifi driver on 3.2.6.3 is way better than the 3.3.1 ?

I'm running 3.3.1 and it's ok to me.
[Galaxy S II Q&A, Help & Troubleshooting] danielsf:
I had a go, and 300mhz showed the exact same performance results as 267mhz in quadrant and nenemark 2. I wan't expecting 300mhz to work, but it would have been nice if it did :)
[Galaxy S II Q&A, Help & Troubleshooting] rlorange:
Yeah ditto... oh well
[Galaxy S II Q&A, Help & Troubleshooting] henrybravo:
+1, same here. Running a Sammy ROM.
[Galaxy S II Q&A, Help & Troubleshooting] Lady_Chloe:
I got a disconnect from time to time, now I am using 3.2.7.1, works great, no disconnects as long as I have signal. I didn't want to go back to 3.2.6.x because the shortcut for inverted rendering is really handy.