yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] johnbeetee:
Would you mind trying this?

if you have updated the superuser app at some time recently, goto settings-manage aplications and uninstall the update

you'll end up with the built in superuser version 3.0.7

the list of added app's needing root will be removed ; that's no problem

now install from the market 'superSU' from chainfire

open superSU app, and it will prompt you permission to update su binary : answer 'ok'

all app's needing root wil now be added to superSU, if you start using them.

if it doesn't help, you can keep using this setup, or if you don't want to, just uninstall superSU and you're back to superuser (chainsDD)

let us know if it worked out....
[Galaxy S II Original Android Development] MistahBungle:
Do you really think you asking every 2-3 weeks for this to happen (And you do. You ask constantly) will make it happen ? It won't. Gokhan has said many a time he tends to ignore people who constantly ask for this/that & refuse to accept he simply doesn't have the time to do all the things he'd like to do/he has a life outside 'all this'.

But you go ahead. Keep asking. That will make it a certainty it will never happen :-/
[Galaxy S II Original Android Development] toxicdust:
Is there currently a ETA on when Siyah would be 100% working on 4.0.4?

1. Bluetooth isnt working

2. Camera Preview isnt working

3. Plugging in phone to PC dont always pickup
[Galaxy S II Original Android Development] Tungstwenty:
I think that ETA question is best targeted at Samsung.

As for camera, look for a post from me done pages back where I shared a temporary fix
[Galaxy S II Original Android Development] str0ppy:
I am dual booting with NeatRom Lite and Paranoid Android. I understand that applications have to be installed from scratch rather than shared with the primary rom. Is there any decent way of sharing SMS over both roms? I am pretty anal about keeping mine backed up in one file and don't really want some texts coming through to the secondary rom and kept separate from the 20 billion texts I have stored on the primary?

Any ideas?
[Galaxy S II Original Android Development] vertrag:
Hi i got recently wifi anomali behavior i cant figure out the cause (either the chip or kernel driver)

Im using the latest 3.3.3d siyah

here's the brief dmesg log

<4>[ 199.272067] dhd_prot_ioctl : bus is down. we have nothing to do
<3>[ 199.272245] CFG80211-INFO2) wl_do_escan : error (-1)
<3>[ 199.272384] CFG80211-INFO2) wl_cfg80211_scan : scan error (-1)
<4>[ 200.274365] dhd_prot_ioctl : bus is down. we have nothing to do
<3>[ 200.274509] CFG80211-INFO2) wl_do_escan : error (-1)
<3>[ 200.274906] CFG80211-INFO2) wl_cfg80211_scan : scan error (-1)
<4>[ 201.277339] dhd_prot_ioctl : bus is down. we have nothing to do
<3>[ 201.277512] CFG80211-INFO2) wl_do_escan : error (-1)
<3>[ 201.277674] CFG80211-INFO2) wl_cfg80211_scan : scan error (-1)
<4>[ 202.278229] dhd_prot_ioctl : bus is down. we have nothing to do
<3>[ 202.278322] CFG80211-INFO2) wl_do_escan : error (-1)
<3>[ 202.278514] CFG80211-INFO2) wl_cfg80211_scan : scan error (-1)

<4>[ 6054.756327] dhd_preinit_ioctls: can't set country
<4>[ 6054.836837] Firmware version = wl0: Jan 17 2012 09:18:41 version 5.90.100.311 (CCX)
<4>[ 6054.858703] Broadcom Dongle Host Driver: register interface [wlan0]dhdsdio_probe : the lock is released.
<4>[ 6055.135989]
<4>[ 6055.136001] Dongle Host Driver, version 1.15.11
<4>[ 6055.136006] Compiled in drivers/net/wireless/bcmdhd/src on Jul 10 2012 at 10:14:12
<3>[ 6055.138415] CFGP2P-INFO2) wl_cfgp2p_supported : wl p2p error -23
<4>[ 6060.174911] dhd_bus_rxctl: resumed on timeout, INT status=0x00000000
<4>[ 6060.186683] dhd_bus_rxctl: rxcnt_timeout=1
<4>[ 6060.187255] wlan0: set allmulti 1 failed
<4>[ 6060.357893] Unknown PRIVATE command COUNTRY ID - ignored

PS: i perhaps mostly deleted some unrelated event on wifi_log3 due to the max size
[Galaxy S II Original Android Development] aviral1990:
Guys,,i am on stock rom and rooted..can i install siyah kernel on my stock rom without havin to do a wipe/factory reset?

thanks
[Galaxy S II Original Android Development] Many40:
Yes, I wipe before cache and Dalvik but it is up to you.
[Galaxy S II Original Android Development] yahyoh:
1- i'm not asking u :mad:

2- it's easy to fix by kernel

3-there 5 kernel for s2 so i don't care if will not get fix it ( it take 2 second to flash another kernel )

4- i have the worst battery life with latest syiah ( i'm really missing old days with syiah )
[Galaxy S II Original Android Development] toxicdust:
Ye i prefer a permanent fix. Bluetooth not working is way more important than camera in my opinion. Did look at your fix and would rather wait for siyah fix before releasing portal rom v2
[Galaxy S II Original Android Development] sobirin90:
Recently when I update to to paranoid v1.6, I experienced random freeze and reboot. Didn't sure why, it starts after i manage to update and change to siyah v3.3.3d kernel (before this I used fluxxi when paranoid v1.5 and right before i flash paranoid v1.6 I flash siyah 3.3.3c first).. then I try dorimanx kernel, also same.. after the reboot usually the battery got change a lot, like before reboot it was 92% and after it freezes and reboot, it become 80% and lower.

I think I might mess up the cpu steps settings.. Anyone got any tips for my problem? I don't mind battery drain, I just mind the random reboot and freeze -.-
[Galaxy S II Original Android Development] CRCinAU:
I'm on the beta for PayPal Here - which gives you this nice little card reader dongle that hooks up to the headphone jack.

Interestingly, when I use Siyah 3.3.3 kernel, the card reader does not work. The app sees it as connected, but nothing is read as you swipe a card. If I flash back to the stock kernel, it works perfectly. Flash back to Siyah, not working, stock, perfect.

Any ideas on how this could be fixed?

Currently using WanamLite 12.2 as a ROM...
[Galaxy S II Original Android Development] MistahBungle:
1) I don't care.

2) Fix it then.

3) So use another kernel.

4) Refer to 1) (and 3).
[Galaxy S II Original Android Development] johnbeetee:
don't know if it helps, but maybe you can try another option in extweaks, last tab, usb-mode ; see it makes any difference

if not, you can also try an earlier version of siyah ; maybe it would have worked then, but something got broken in the later versions?? (just speculating here..)
[Galaxy S II Original Android Development] igoa:
NTFS

How to disable auto install of ntfs-3g binary?
[Galaxy S II Original Android Development] godithisudha:
sdcard not mounted in 2nd ROM

SDCARD not mounting in 2ns rom, i am using wanamlite as primary and PANADROID as 2nd ROM, SDCARD data is not visible in file manager and apps also not reading data from SDCard.

flashed the latest siyah kernel 3.3.3d , still problem exists. please solve this problem
[Galaxy S II Original Android Development] [SIC]:
@OP: You should change the threadstart that your kernel handles everything incl. AOKP. I almost missed this brutal kernel because of that :o

Sent from my Paranoid SGS2
[Galaxy S II Original Android Development] timberwolf60:
This was not siyah kernel problem, ics 4.0.4 will assigned ext SD card to /emmc like in s3.

In paranoid the ext card was in /emmc. So many programs can't access it. I used this: http://xdaforums.com/showthread.php?p=28774285,

It worked for me. It will re-assigned /emmc to /SDcard/external_sd. Then download scan media from play store. Run it and it let you be abled to see your media files in ext SD card. Paranoid with remount SD will caused camera worked only with internal SD card. Waiting for new version.

Send from my GT I9100 using Tapatalk2, 1st ROM Paranoid V1.6a, and 2nd ROM XXLPW, Siyah 3.3.3d kernel, jkay 14.1 mode.
[Galaxy S II Original Android Development] timberwolf60:
Don't used siyah kernel with superSU. Just removed root within extweats apk as shown with auto install root enabled:

This was a great feature of siyah kernel. It also gave you a solid root by doing this.

Send from my GT I9100 using Tapatalk2, 1st ROM Paranoid V1.6a, and 2nd ROM XXLPW, Siyah 3.3.3d kernel, jkay 14.1 mode.
[Galaxy S II Original Android Development] cdaarif:
Hay man im a bgainner. i flash 3.3.3d in stock ics 4.0.4 XXLQ5 rom. Now i video dont display only sound. Camera & bluthoth is not works. Is it a beta?? Plz hlp me.

Edit: i faound this for video n camera fix. http://xdaforums.com/showthread.php?t=1772931. only need bluetoth fix.

Sorry for my bad english
[Galaxy S II Original Android Development] coolstory:
i want to instal dual boot and can't do it cuz i can't wipe data/cache first cuz error appeared. I tried to remove 2nd rom restore old i installed previous version i wiped data at 1st rom and the same story :( Help!

1. Dual boot settings

2. Wipe data/cache (E:format_volume: make_extf4fs failed on /mnt/.secondrom/.secondrom/cache.img Error formating 2nd rom cache! )

3. Cant instal second rom :( help! :(
[Galaxy S II Original Android Development] johnbeetee:
I know about that feature ; it's ok , but i'm suspecting there are some strange things happening, not because of the kernel, but because of the su binary included/used by superuser app (built in version 3.0.7 / su binary 3.0.3.2, you can update the app to version 3.1.3 if you will, but still....)

and I have been testing this all weekend now on stock and AOKP (hydrogen) on kernel 3.2.7.1 and now on 3.3.3.d...

why? (do you ask)

* Just like d3l1, I experienced that spike (cpu locked to highest freq.) when charging, coming from 3.3.3.d back to 3.2.7.1

* I had a spontanious reboot on 3.2.7.1 (which I never had ever had...ever)

* the load profile wasn't the same as before coming back from 3.3.3.d, making the system behave more erradic (using the same settings I always do)

* as time pass, it was as if the touch sensitivity deteriorated and became somewhat sluggish

* battery comsumption seemed off and not as before (I ussually get very consistent values, so whenever something is out of the ordinary, that's a give away to me)

* I experienced wifi glitches on 3.3.3.d which I couldn't explain due to any changes made in this version

Some background info to the story:

ever since dual-booting came to life, i've been using the combination superSU onto superuser. This came about after installing my secondary rom (hydrogen), which used superSU instead of superuser. I never gave it much thought then, as it worked ok. Back in those days I never had any problem with none of the version of siyah, and was always surprised when reading about others having it differenttly. I stopped using this combination, after version 3.2.5.2, which forced installed superuser and got rid of all other versions including superSU.

After that I didn't have any problems so I never consider going back to that setup (superSU onto superuser). In the course of time I did notice some fractional differences in respons and battery-life variations, but thought that it was normal (fresh reboot ussually helped).

What did this setup yield?

* charging spike (lockup) eliminated

* touch respons and even unlocking screen is ever so smooth as it used to be and remains consistent

* load profile is back to normal

* my battery consumption is finally back to normal (with little use in the weekends, averaging about 1.25%/hr on 3.2.7.1 , giving me about 3-3.5 days of use per charge - with normal use during the week averaging at least 2 days/charge)

I'm testing it now on 3.3.3.d, and I'm hoping it will give the stability I expect from this kernel version, so I'll know for sure in a few days, but for now it's looking pretty good

I can't provide any hard proof, but as stated, I have a pretty solid impression that superSU (and it's own su binary) is doing a far better job than superuser's version.
[Galaxy S II Original Android Development] Tungstwenty:
You can find a fix here

It's a temporary solution for the video and camera issue until the custom kernels can be updated with the latest sources from Samsung.

---------- Post added at 06:39 PM ---------- Previous post was at 06:26 PM ----------

Personally, I kept using SuperSU the whole time, even after Gokhan included the auto-installation of Superuser in the kernel.

I just installed SuperSU, have it update the binary to its own, and then eliminate the occasional problems that it creates (BBS for instance) by disabling toasts for those apps that do root stuff every now and then.

About the spikes and battery consumption you mention - did you by any change try running top to see if any processes were using the CPU?

We tend to focus so much on wakelocks and alarms, that perhaps actual CPU time burned by the processes' cycles are forgotten :p

The other day I posted a comment on the BBS thread about an experiment I did with a while(true) loop, just to see how deep sleep worked in that situation - user processes, even when demanding CPU, will be put to sleep if there's no KWL active, but if the device is charging and you have one such situation (unlikely, but still...)

Also, I'm not sure I understand your statement about "SuperSU + Superuser combination". You're using each of them in its own ROM, right?

/system/bin/su will be either from SuperSU or from Superuser, and depending on which, when apps start something as root the appropriate control app will pop up asking to grant permissions independently if the other app is installed as well.

So, you can have su in /system of one ROM and another binary in the other /system.

(I'm sure you're aware of this ;), just trying to confirm that it's what you mean by "combination")
[Galaxy S II Original Android Development] Many40:
Hi John,

As you already know I had as also many others, some issues related to the newest version of superuser/su binary, but in my case as long as default kernel's superuser 3.0.7/su 3.0.3.2 gives me more less the same stable configuration as SuperSU, currently I'm using the default ones. Regards
[Galaxy S II Original Android Development] coolstory:
Please help :(
[Galaxy S II Original Android Development] johnbeetee:
Concerning the spike : to be honest I didn't even bother to try to find out what was causing it, having experiencing so many 'mysterious' behaviour the past week, testing 3.3.3c en d. Somewhere in the back of my mind I knew something other than the kernel was behaving naughty, especially going back to an older (proven stable) version and still having weird things happening.

About my description of the setup, you're completely right ; it maybe a liitle bit akwardly formulated - what I mean by that is that superuser, being integrated in the kernel is not easily (completely) removed (by an average user).

By installing superSU, it is sidetracked and rendered inoperable, but users will still be seeing it appearing in their app drawer en aplication manager, so maybe a better decription would just be: "install superSU and just forget about superuser' setup :laugh:
[Galaxy S II Original Android Development] Many40:
When you tried wipe data/cache of 2nd rom did you have enough memory space in sdcard (it should be 2.1 GB)
[Galaxy S II Original Android Development] MistahBungle:
There isn't one. You can read the ExTweaks thread, also the Siyah GB thread has a smattering of posts in it about ExTweaks settings since the app was released. Essentially, if you don't know what the settings are for, don't play with them.

There are also a lot of threads on XDA that go into CPU & GPU settings generally that can be controlled/changed with various other apps & the info in these threads would also apply to settings that can be changed in ExTweaks.
[Galaxy S II Original Android Development] eric-filth:
Same problem here. I had raise voltage for 500mhz

Enviado do meu Galaxy S2 Undervolt usando Tapatalk
[Galaxy S II Original Android Development] hallydamaster:
I am running CM9 22 version, and I definitely have have those settings! :rolleyes:
[Galaxy S II Original Android Development] pulser_g2:
Didn't see anything hotplug related (no sources yet to check, but it didn't seem enabled)

https://github.com/pulser/android_k...mmit/7a35922db6ca874f2e12ff45590a4bf216619674

That allows you to control the CPU hotplug via 2nd core app...
[Galaxy S II Original Android Development] eric-filth:
My phone liked deep sleep likes me :-)
[Galaxy S II Original Android Development] firefox1991:
can i use the script with the same tweaks of gb in the ics kernel
[Galaxy S II Original Android Development] luexi:
my bad, did try to set all value from 0 to 255, backlight still not on..
[Galaxy S II Original Android Development] gabx:
Nothing. For what I can read and experienced, lowering your dpi will let you with an unbootable ROM
[Galaxy S II Original Android Development] droidphile:
No, that is why this post.
[Galaxy S II Original Android Development] seavers11:
I'm using this rom since v5. 0 on 160 dpi and everything is working fine here....

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II Original Android Development] geviron:
Hello, I'm on MIUI V4 2.3.23 and it's based on the latest Samsung LPQ firmware, but still won't boot up after flashing b6 (Black screen)

Any Ideas?

Cheers.
[Galaxy S II Original Android Development] Vaedryn:
This Kernels didn't work with Miui V4

SGS II Cyanogen Mod 9 Tapatalk
[Galaxy S II Original Android Development] Bobblot:
Sorry for a bit of a noob question but can someone please explain to me which bit on the CPU part on extweaks I change so I can have 200/800 thanks :)
[Galaxy S II Original Android Development] Vaedryn:
you need voltage control / setCpu to change 200\800

SGS II Cyanogen Mod 9 Tapatalk
[Galaxy S II Original Android Development] PiCkLeS:
Have you changed your DPI to lower than 240? If so, thats the problem.
[Galaxy S II Original Android Development] mekhonte:
Siyah Kernels Blog app

Just a simple app to check gokhan's blog. It might be useful for lazy ones like me :D:D:p and I hope you like it.

It was the only way that I knew to help somehow.
[Galaxy S II Original Android Development] Lennyuk:
So how does his dual boot roms work then, where does it store the second rom? And I guess it doesn't share data?
[Galaxy S II Original Android Development] Vaedryn:
We dont know. Dual Boot is at the moment a placeholder only. It dosnt work :)
[Galaxy S II Original Android Development] mekhonte:
We don't know yet.i think he will start working on dual boot after first stable ICS release. He might use the hidden partition but i'm sure it doesn't share data
[Galaxy S II Original Android Development] troyjamz:
Thanks a lot man!! :D
[Galaxy S II Original Android Development] cdaarif:
Hay tnx man now i run video n camera by siyth 3.3.3d bt bluetoth cant run :(

Sorry for my bad english

Sent from my GT-I9100 by xda.
[Galaxy S II Original Android Development] johnbeetee:
I did try that for a while last week, but somehow it didn't work out for me

In the long run, I did notice the touch responsiveness become a little bit less, and eventually even the wifi became worse, the infamous "not connecting" problem.

So I went back to 3.2.7.1 (from a clean nandroid backup), but only to notice some of the problems re-occurring, which I found extremely strange....

That made me think back to period I had superSU....and that's why I started this set of tests, and I must say...it made me very happy again.

But you can keep testing your setup if you will and we can compare results ; just keep an eye on those things as touch respons and batterylife and even sudden short freezes (and let's hope not, sudden reboots).

If you do experience those, then it might be worth trying superSU out....
[Galaxy S II Original Android Development] d3l1:
As I'm running MIUI I don't really know how su behaves in my case, I don't have the actual apps Superuser or SuperSu running because MIUI has it's own root manager.

I tested my primary Rom (stock samsung), vbus is still present but at 200Mhz. So I decided to boot my secondary Rom again and for the last 45 minutes, even though vbus is the main wakelock, CpuSpy shows that it's running at 200Mhz and not at 1200Mhz like the day before. So its a really strange behaviour going on here. What I can relate to is the decreased battery life with the new kernels and the touch sensitivity decreasing over time while discharging.

I decided to switch the governor to on demand to see if it changes anything so far the free while charging is back to 200. Hi is a little more sluggish but still better then Pegasusq.

Sent from here using Tapatalk
[Galaxy S II Original Android Development] :
Could someone explain a safe way to switch from latest superuser to supersu to try by myself your theories about it? :) just to be safe!

Sent from my SGS2 - SlimICS Rom & Fluxi Kernel
[Galaxy S II Original Android Development] It_ler:
Install SuperSU app from Play store.

On first start confirm to update/install its binaries.

Done.
[Galaxy S II Original Android Development] johnbeetee:
I'm not familiar with MIUI (yet), but when using stock, you can always try installing superSU, and let it take over the su management, just to try it and compare batterylife. If it helps, than superuser is probably the cause (of some, if not all strange behaviour)
[Galaxy S II Original Android Development] Many40:
And of course deactivate "Auto instal root" option, if you have it ticked because after next reboot you would loose youR SuperSU.
[Galaxy S II Original Android Development] BrandoHD:
That's not necessary, I've never touched that and I've been using SuperSU for some time

Samsung Galaxy S II Tapatalk2
[Galaxy S II Original Android Development] johnbeetee:
That is a good remark!.........but it's not nescessary, strangely enough. (tested and confirmed) (and traced in init scripts)

The kernel tests if a binary called su exists, and in both cases (superuser or superSU) it does.

This option only does something in the case that you have removed root using extweaks, and therefore su binary is not anymore present.
[Galaxy S II Original Android Development] coolstory:
ok thanks now is cool. Thanks bro!
[Galaxy S II Original Android Development] blaex:
i have an issue with my mhl (hdmi connection) when i play a video (flv-format) on my samsung lcd-tv. first the video runs great, but after several minutes the screen turns into white distrortion (3 times) or black-greenish screen then reapears normal, this happens randomly. in the meantime the phone is still playing the video without any distortions.

using 3.3.3d - tested with default/battery/performance extweaks settings.:rolleyes:

i used hard uv on gpu 100 @ 850mw 160@900mw 267@1000mw - but even with standard voltage the distortions appear.
[Galaxy S II Original Android Development] xator91:
Anyone can look this?

http://db.tt/7hr24NVq
[Galaxy S II Original Android Development] CRCinAU:
I'm not sure this would make a difference as the card reader connects to the AUDIO socket. Unless this can be changed to a USB mode somehow, I think the app just uses the mic socket to decode the card info...

Are there any changes to audio between any earlier version and 3.3.3d? Changelog somewhere?
[Galaxy S II Original Android Development] godithisudha:
thanks for the help

thanks mate for the help and explanation on the root cause
[Galaxy S II Original Android Development] timberwolf60:
I used a paid version of superuser. Since I am using dual boot, so only superuser was my choice which came from siyah. I had never facing wifi, 3G problems. I nearly tried all the siyah version without any problems on wifi and 3G data. I only believes GM choose superuser will have a reason for that.

Send from my GT I9100 using Tapatalk2, 1st ROM Paranoid V1.6a, and 2nd ROM XXLPW, Siyah 3.3.3d kernel, jkay 14.1 mode.
[Galaxy S II Original Android Development] kairi_zeroblade:
is anyone having screen freezing issue on the lockscreen when i turn the Touch key light duration to always OFF/ON?i did saw some a few pages back with screen freezing issues..

EDIT: oh btw i am on the 3.3.3d+