yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] nicola1989:
3.3.3d is out
[Galaxy S II Original Android Development] SPBoss:
WOW! I have well over 5 hours screen on time with 3.3.3c on 30% brightness with wifi and data on!

Using Pegasus usq, sio, thunderbolt cfs tweaks, smooth scaling to 800 and a mild undervolt and also disabled the logging.

Thanks GM I'm so glad u didn't leave the s2 even though you have an s3. Top guy!
[Galaxy S II Original Android Development] MemoryController:
@gokhanmoral implement sense4all dual booting?
[Galaxy S II Original Android Development] cool-face:
It's possible to port sgs3 usb dac audio support to siyah sgs2 kernel?
[Galaxy S II Original Android Development] MistahBungle:
No. Been asked lots of times, very unlikely to see USB DAC support on SGS2. Ever.
[Galaxy S II Original Android Development] xkovi:
It would be nice but still doesn't work for me too...just tried "Kingston DT101 G2 8GB" formatted to NTFS (currently used as a bootable Win7 installation image) and it's recognized as a "blank USB storage" same as my 2TB WD external drive...

Another USB flashdisk formatted to FAT32 (Sandisk U3 Contour) is recognized correctly...

However, I've tried - just for fun - hp optical usb mouse, hp usb keyboard and wireless logitech mx620 mouse and all devices worked like a charm :laugh:
[Galaxy S II Original Android Development] powerover:
Chinese 4.0.4

There is an official 4.0.4 out there I9100ZCLPL

Is it safer then Russian one?

Can GM work on it?

I would very much like to see the speed and smoothness of 4.0.4 inside the already close to perfect WANAM release

but to bring it to perfection WE all need Siyah

The Best Kernel EVER

period

:cool:
[Galaxy S II Original Android Development] Tungstwenty:
:confused::confused::confused:

My comment was about 3.3.3c including a change to ignore multicast traffic, thus potentially reducing wifi wakelocks.
[Galaxy S II Original Android Development] Joseiyo:
Can you link those thunderbolt tweaks, please?

Enviado desde mi GT-I9100 usando Tapatalk 2
[Galaxy S II Original Android Development] carlos67:
Sorry, wrong thread.
[Galaxy S II Original Android Development] Marcel899:
Anyone else here experiencing whatsapp messages being delayed with Siyah? I've had no push notification, when I randomly started whatsapp I had 50 new messages... Anything to solve this?
[Galaxy S II Original Android Development] xXCorleoneXx:
the cfs tweaks are found in the extweaks app.

there you can adjust everything.
[Galaxy S II Original Android Development] :
ThunderBolt! remount scripts were causing random reboots and some problems? Firstly, I saw a new line remounting /system, and now, data, cache and system were removed.
[Galaxy S II Original Android Development] xkovi:
Sorry bro,

IDK why but I supposed your post is related to NTFS feature :) My post already corrected, thx for notification... ;)
[Galaxy S II Original Android Development] triplex76:
Default + cfq
[Galaxy S II Original Android Development] crypticc:
+1. Went to shun because of this
[Galaxy S II Original Android Development] BrandoHD:
The delayed messages only occur if you kill the app, when you kill the app, you kill the service, if you kill the service, only opening the app restarts service

Either way this belongs in the discussion thread not the dev thread

Samsung Galaxy S II Tapatalk2
[Galaxy S II Original Android Development] pikachu01:
No, I mean, what is the conservative setting?

Up_threshold, down_threshold etc?

ThunderBolt! remount scripts are NOT the ones causing random reboots. It was the culmination of how BBS was calling su in the new superuser binary by ChainsDD.
[Galaxy S II Original Android Development] robertobsc:
Probably they are using the default tweaks for conservative.

For me pegasusq is just fine. No lags, smooth, nice responsiveness... That's is not only because of the governor, but certainly he's not causing problems.
[Galaxy S II Original Android Development] red_brindle:
Poweramp + Soundgasm = Powerhouse Combination.

Thanks GK :)
[Galaxy S II Original Android Development] bervin:
do you have whatsapp? because i have to agree with thoe guys saying that there isn't an notification. i made sure i didn't kill app i even left it locked the screen on the whatsapp page and it still didn't notify me..
[Galaxy S II Original Android Development] pikachu01:
It might be an aggressive LMK killing background apps? Are you running any LMK scripts?
[Galaxy S II Original Android Development] marcusjt:
v3.3.3d WiFi issues

I've been having WiFi problems with SiyahKernel-S2-v3.3.3d (poor signal, disconnections, WiFi disabling itself, etc) so have reverted to v3.3.2 which works fine.

Is this a known issue / anyone else experiencing this?
[Galaxy S II Original Android Development] johnbeetee:
+1

(just glad to know i'm not the only one....)
[Galaxy S II Original Android Development] bervin:
Nope,I don't. That's the weird thing.
[Galaxy S II Original Android Development] marcusjt:
Unfortunately the problem I have with v3.3.2 is that the screen sometimes goes off and won't come back on, requiring a reset... I didn't experience this with 3.3.3d but I didn't run it for long so I'm not sure whether it was fixed (there's no mention of the issue in the notes)... so I'm hoping Gokhanmoral will release a v3.3.3e which nails both...?!
[Galaxy S II Original Android Development] Many40:
I thought I have no preblems with 3.3.3d but I was wrong. After disconnecting from a charger BBS keeps KWL vbus_present and freezes and soft reboot. Everything is stable after "hard" reboot.
[Galaxy S II Original Android Development] BonnyBedlamBoy:
everything is working fine here with 3.3.3x and paranoid rom. thanks.
[Galaxy S II Original Android Development] Lownita:
What exactly does this wakelock option for bbs do? I don't see any difference in bbs! Does it cost performance enabling it?
[Galaxy S II Original Android Development] andreivibefm:
on stock XXLQ5 4.0.4 version.. camera doesn't work. just a black screen.

any idea?
[Galaxy S II Original Android Development] lyndonguti:
this is not compatible on lq5 ...you my brick your device..sorry:o
[Galaxy S II Original Android Development] duff91:
the phone read my kingston 16gb NTFS, but i ca't write on Pendrive, says operation failed... i try with different pendrive but is the same
[Galaxy S II Original Android Development] andreivibefm:
isn't bricked.. I put stock kernel back and now is ok, camera works.
[Galaxy S II Original Android Development] yhrn:
It only changes how wakelocks are reported so it should not introduce any noticeable overhead. It is not directly related to BBS but rather how kernel wakelocks are reported in /proc/wakelocks (which is where BBS looks to provide its kernel wakelocks view).

I think the basic idea of this new model for reporting wakelocks is that if multiple wakelocks are taken at any time only the first one taken will be reported, i.e. no overlapping is reported.

For example, if wakelock w1 is taken at time 0s and released at time 10s and wakelock w2 is taken at time 2s and released at time 5s only w1 would be reported (for 10s). Using the standard way of reporting kernel wakelocks both w1 and w2 would be reported (for 10s and 3s respectively) even though it really made no difference that w2 was taken.

Please correct me if I've got this wrong. I know that kernel wakelock reporting its more complex than this (wake count vs count, total time vs sleep time) but I hope that this describes the basic idea with the new feature.
[Galaxy S II Original Android Development] santi666:
Hello.

What is soundgasm?

Enviado desde mi GT-I9100 usando Tapatalk 2
[Galaxy S II Original Android Development] Tungstwenty:
There are a couple of posts I previously made explaining it, but perhaps the most direct one for you to have an idea would this post from chamonix with a quote to my initial explanation.

Simply put, lock times, power consumption, etc. remain exactly the same; what changes it that there's an alternate set of statistics exposed to BBS (or other tools) that might be helpful for troubleshooting battery use, as a complement to the current set of stats.

This is being discussed with chamonix as you can see on that thread.

From a user's perspective, as I said, there's no battery impact either positive nor negative related with this change.

PS: yhrn's explanation is spot on; that example is an excellent way to put it
[Galaxy S II Original Android Development] MistahBungle:
Like Voodoo Louder; you can increase volume with headphones/headset, only better ;-) You can adjust the volume increase in ExTweaks (0, +1.5dB, +3dB, +6dB).
[Galaxy S II Original Android Development] duff91:
same problem with 3.3.3d - i can't write on pendrive NTFS
[Galaxy S II Original Android Development] switchgott:
Thanks for best kernel!

But with AOKP M6, we have a big problem!

The LED from buttons, wen cant disable it!!

Every time the went to on.

Any idea, or fix??
[Galaxy S II Original Android Development] johnbeetee:
This has been in the siyah changelog as of version 3.2.6.4:

"fixed ntfs mounting and added ntfs-3g binary back. it will not be used if “ntfs mounter” app is installed. otherwise, ntfs sticks will be mounted read-only in /mnt/ntfs folder."

..and I haven't found any mention later on that it has changed.
[Galaxy S II Original Android Development] MyLifeRocks10:
Set led timeout in extweaks app.
[Galaxy S II Original Android Development] lyndonguti:
mine is always off...its not a bug....

go to extweaks bln disable led timeout unchek led on touch and led fade out....if you are on cm9 base ....do this another setting go to settings...advance(galaxy s2 settings) go to sensors and unchek enable keys backlight
[Galaxy S II Original Android Development] baza14:
I think so. This problem is still here on CM9. I wonder if GM will ever fix it. There are few kernels that have this problem solved (DorinmaX, CM stock, Fluxi).
[Galaxy S II Original Android Development] maxobelix:
As few people here, too many wifi issues, have to go back to 3.3.2...
[Galaxy S II Original Android Development] marcusjt:
FWIW I've since found that 3.3.3c has neither the WiFi issue I mentioned (and other people seem to be having) nor the screen issue that 3.3.2 has...
[Galaxy S II Original Android Development] TTLucian:
Hi. NTFS works just as described but notification bar says that the USB is blank or has unsupported file system. Also there's no way to umount... except console maybe. No R/W access, only R/O. NTFS Mounter app is working nicely but still the USB is blank message is displayed when connecting.
[Galaxy S II Original Android Development] Frozenthunder:
I'm also having issues with 3.3.3d. Somehow my Emails won't refresh when phone is in deep sleep even though wifi is turned on. it worked fine on 3.3.3c but now it seems to not update anymore because I don't get notified even though there are new emails.
[Galaxy S II Original Android Development] miedy12:
help where i can download 3.3.3c instead of 3.3.3d
[Galaxy S II Original Android Development] carlos67:
Great explanation! Thanks because I was wondering about this too.
[Galaxy S II Original Android Development] Lonzo_SGS2_506:
3.3.3c

here bro....
[Galaxy S II Original Android Development] SPBoss:
I swear some people on this threat dont even bother to try and fix an issue themselves first. It would save other user trawlig through pages of unrelated crap. Eg the last two pages of 'led always on' complaints!

Simple fix is to enable and then disable led in gs2 settings. Problem solved!
[Galaxy S II Original Android Development] carlos67:
Has anyone managed to get rid of the wlan_rx_wake wakelock yet? If so, how?
[Galaxy S II Original Android Development] tlf55:
I'm still on 3.3.2 .. does it worth to pass to 3.3.3d ?

Thanks
[Galaxy S II Original Android Development] Many40:
Why not. TBH still testing but up to now - no FCs, no freezes, and no reboots. Not sure yet about battery usage but seems to be not worse than 3.3.2. I had some problems with:

1. Newest Superuser/su binary but after shifting to kernel defaults it's stable now.

2. BBS ver 1.8.1 (soft reboots after disconnection of a charger). Newest version solved it for me.
[Galaxy S II Original Android Development] prbassplayer:
Thread cleaned. Please stay on topic.

Cheers
[Galaxy S II Original Android Development] sefrcoko:
Anyone having problems with Droidwall on Siyah 3.3.3d and Wanam 12.2? Used to work fine with 3.3.2 but now it's not blocking apps from connecting to internet (firewall works on wifi but not 3G). Everything works with 3.3.3d and Rootbox 1.6 though. Tried reinstalling droidwall, clearing cache, etc. Posting here because maybe a Siyah issue related to Sammy roms...? Any help is appreciated, thanks.
[Galaxy S II Original Android Development] Many40:
Sorry, I am on stock XXLPW and 3.3.3d and DroidWall works still well both on WiFi and 3G. I've just checked it (ticked 3G for stock browser, applied rules and now access for this app is forbidden on mobile data network). Regards
[Galaxy S II Original Android Development] Many40:
Maybe I shoudn't have answered previous post - all of us should follow the guidance above. No doubts, it's the DEV thread.
[Galaxy S II Original Android Development] SignalX:
sorry for question

can any one please tell me what is "Soundgasm" ?

cheers,
[Galaxy S II Original Android Development] Phistachio:
Headphone audio boost. It's a new category named "Audio" in ExTweaks.
[Galaxy S II Original Android Development] cool-face:
There is Android Open Accessory Protocol 2.0 with usb audio output support (http://developer.android.com/tools/adk/aoa2.html#audio-support) but i think is requires jelly bean... GSII have usb host it's only no driver for usbaudio.
[Galaxy S II Original Android Development] MistahBungle:
Whether Android supports it or not is irrelevant. The devs who have been asked to have a look at getting this working have said it's simply too difficult due to proprietary drivers/Samsung code. Nobody is prepared to put in/has the time to get this working. There's about a 1% chance of this ever working on SGS2 (regardless of any nonsense on HeadFi).

If Gokhan doesn't have time to hardly work on the S2 at all anymore (and who can blame him ? He's working on S3 & he does have a job/life/family, n00b users tend to forget this in their selfishness), you can be fairly sure getting something like this working isn't even remotely on his radar (he doesn't even have time to get DSP Manager working; again something that's a pain in the arse for various reasons).
[Galaxy S II Original Android Development] d3l1:
Is that supposed to be in 3.3.3d while charging the phone, running at 1200Mhz the whole time due to the vbus_present wake lock?

Sent from here using Tapatalk
[Galaxy S II Original Android Development] erew1:
i'm using 3.3.3d and i found that sometimes when I unlock the phone and go to the home screen, the home screen freezes and I have to press the hardware button like back or home in order to unfreeze it. It is not a complete freeze, the live wallpaper is still moving and the clock widget is still functioning... just the touch has no response, but i could still drag the notification bar down. Any solution?
[Galaxy S II Original Android Development] johnbeetee:
did notice that, and i'm still looking for the problem and a solution ; i just have a suspiscion at the moment (as all latest version seem to have some problem, even the older ones, so i think it's not siyah related)

maybe you are willing to try 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

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

Try this setup for a while and see if it helps

i'm running some duration tests at the moment on 3.2.7.1 (which also started showing up these problems and this seems to help ; will be moving to 3.3.3.d after that and test that one).

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] pikachu01:
The wake lock is not the problem. It's the app that is requesting the traffic that is the problem. Check alarms or partial wake lock to see what apps are there that use Yee internet.

Nope. Something is running in the background causing the cpu spike.

Your launcher or widget is causing this.
[Galaxy S II Original Android Development] vizdak:
If you're using a Screen Off apps try not to use it and see what happens. Sometimes Screen Off apps freezes the phone and it will mimicked the SOD effect.
[Galaxy S II Original Android Development] Ok_Kaleidoscope5109:
Does BLN still cause wakelock? Just wondering....
[Galaxy S II Original Android Development] MistahBungle:
Yes.
[Galaxy S II Original Android Development] kairi_zeroblade:
oh darn..when i turn the BLN on i get no friggin weird wakelocks..when i turn it OFF all hell is loose..

either ways still a good release.. :D

me wants to compile this with linaro..is it possible?
[Galaxy S II Original Android Development] d3l1:
I checked my system with the task manager, none of the programs is reporting what could cause the vbus_present wake lock. Can you help me identify the source or tell me how to find it?

Only real info I could find on that special wake lock:

https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/vbus_present

Sent from here using Tapatalk
[Galaxy S II Original Android Development] BrandoHD:
Reboot your phone

Samsung Galaxy S II Tapatalk2
[Galaxy S II Original Android Development] cool-face:
Hope usbaudio works on cm10 ;-)
[Galaxy S II Original Android Development] lambstone:
vbus is simply wakelock from charging. When you are charging your phone, it doesn't go into deepsleep.
[Galaxy S II Original Android Development] d3l1:
Tried that already, rebooted a few times but it's still behaving like that while charging.

Yes but it's running the whole time @ 1200Mhz and can't be right. Before it started to behave like that it was constantly at the lowest frequency (200Mhz und my case).

Sent from here using Tapatalk
[Galaxy S II Original Android Development] It_ler:
Have you got that issue on bith ROMs?

Maybe you should reflash the kernel, wipe cache partition and Dalvik cache after flashing in recovery mode.
[Galaxy S II Original Android Development] WindGhost:
SiyahKernel 3.3.3d

Phone : GT-I9100, PDA : JPLPF, Phone : XXLPX, CSC : JPLPC, Android : 4.0.3

I just installed it now on my device. WiFi connects as stock kernel (Fast), no difference in battery, on ExTweaks just enabled the BLN and worked for me, no lags, no FCs, on CPUspy all freqs works fine (even deep sleep). No camera issue.

I'm using SGS II for a month. This is the first time I'm using custom things on my device. What can I say, really good kernel, no issues till now.

I'm going to try now a dual boot.

Regards,,,
[Galaxy S II Original Android Development] BrandoHD:
Also check your governer settings and the min/max frequency

Samsung Galaxy S II Tapatalk2
[Galaxy S II Original Android Development] sydknee:
Great kernel. Love ex tweaks. Wi-Fi signal constantly showing no signal in status bar when getting a decent Wi-Fi connection. The bars seem to have a poor correlation with actual signal strength. Is not happening with stock kernel or Neak. Not complaining, just wondering if this needs a tweak in your next release.
[Galaxy S II Original Android Development] fusionjack:
You are using Miui V4 right? If yes, it is a known locksreen heat problem. Change the lockscreen. I also have this problem before and the keyboard was eating the most battery during charging.
[Galaxy S II Original Android Development] Tungstwenty:
While Samsung doesn't release the needed source updates to be incorporated in Siyah, here's a fix that will make Camera preview and Video playback work in the meantime: http://xdaforums.com/showthread.php?t=1772931

Haven't found a way to make Bluetooth work, though.
[Galaxy S II Original Android Development] yahyoh:
gokh please please when u have time if u can fix dsp manager don't work with ur kernel :cowboy: its only work with cm kernel + fluxi
[Galaxy S II Original Android Development] :
I think it's because CM moved /vendor folder to the ROM, so gokhan needs to symlink /vendor to /system/vendor, which may never happen, because it will break some stuff on other ROMs, like on Samsung ROMs.
[Galaxy S II Original Android Development] yahyoh:
can i make it manually ? :D
[Galaxy S II Original Android Development] powerover:
symlink

use terminal emulator:

su (enter)

mount -o bind /vendor /system/vendor (enter)

or if the folder is located elsewhere just replace "/vendor/" with whatever...
[Galaxy S II Original Android Development] yahyoh:
didnt work after copying what inside system/vendor to /vendor and reboot the files that i've copied will gone :(:(
[Galaxy S II Original Android Development] d3l1:
I haven't used the stock Rom in months, the issue started with flashing siyah 3.3.3 and didn't go away by flashing 3.3.2 again, it kind of stuck.

Gov is conservative, min freq is 200, max freq is 1200. Changing Gov back to Pegasus doesn't solve the problem either, it just makes my ui laggy.

Yes I'm using Miui v4 but I use the lock screen for weeks now and the issue started a few days ago with flashing siyah 3.3.3 and couldn't be reversed/solved by flashing 3.3.2 again.

Wiping cashes didn't make a change either and I can't point out an app that could be causing this wakelock.

Sent from here using Tapatalk
[Galaxy S II Original Android Development] BlackRainX:
Is there way to push GPU over 400MHz like on SGS III (440)? ;)
[Galaxy S II Original Android Development] #illidan:
Not possible afaik. We already have oc it to 400MHz. What could you possibly do with an extra 40MHz?
[Galaxy S II Original Android Development] Phistachio:
Fry eggs.
[Galaxy S II Original Android Development] crypticc:
Just a reminder, if your post has a how, can, will, need, or any other question in it, and especially if you do not have a logcat, Dmesg, etc you should be posting here.

http://xdaforums.com/showthread.php?t=1658647
[Galaxy S II Original Android Development] crypticc:
I also suggest answers are directed here too.

http://xdaforums.com/showthread.php?t=1658647
[Galaxy S II Original Android Development] crypticc:
And if you don't know if your question is dev or q&a it should probably go here.

Just for good measure

http://xdaforums.com/showthread.php?t=1658647
[Galaxy S II Original Android Development] crypticc:
I believe genuine bugs with logs is okay. I also think maybe a question on which logs would be helpful and how to grab them is generally agreed as acceptable.

So sorry for cluttering the thread for everyone else myself; but I just ploughed through several pages and the same posts keep creeping in.

Cheers
[Galaxy S II Original Android Development] crypticc:
Normal protocol for wake lock questions is to use the bbs thread I believe, until a kernel issue is pinned down at least. Wake lock specialists lurk here, lol.

http://xdaforums.com/showthread.php?t=1179809
[Galaxy S II Original Android Development] fifthelement:
Hey Guys,

Where can I get the latest version of extweaks ? I am asking because I see extweaks is modified in change log recently but the version in play store is dated 8 April.
[Galaxy S II Original Android Development] bland.life:
I think ExTweaks finds the options in the kernel and builds the option pages in the app.

Don't think theres an 'Audio' option page before until recent kernel builds.

So just update the kernel, the new options will pop up in ExTweaks automatically.
[Galaxy S II Original Android Development] fifthelement:
cool, so in fact Extweaks options are being updated with kernel updates without the original app being touched. it is a brilliant idea :)