yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Ray1:
I post a question at the Q&A, silly me, i've should've posted it here.

http://xdaforums.com/showthread.php?t=1774688

basically the stock battery monitor/history thing doesn work any more on siyah kernal.

tried 3.3.2 and 3.3.3 both also had this issue.

is there a fix for it? it only display 4 items even though i clearly used other apps that drains the battery such as chrome and temple run.
[Galaxy S II Original Android Development] johnbeetee:
Yes, in the sense of the volume level (for music), also configurable in extweaks (audio tab)

If the communication between the cardreader and the controlling app/driver is purely audio-based, than that might be the problem

(I thought internally it might interconnect somehow with the usb driver, for it's serial communication protocol).

---------- Post added at 07:35 AM ---------- Previous post was at 07:31 AM ----------

I think that's a bug somehow in combination with stock-roms. On AOKP it's ok.

Don't know a fix, but if anyone else does, ....

+1
[Galaxy S II Original Android Development] d3l1:
have you tried playing via all-share through your network? in your case, I would think first of a bad connection, maybe the cable is preventing the connection to stay alive correctly, thus forcing new handshakes to validate the hdmi connection which may cause the interruption. hdmi connections rely on a hdcp connection and if it gets interrupted, there is a short blackout of video and audio until the hdcp connection is fine again.

I had this once with an early stage Miui v4 build but it was fixed on the ROM side, so my guess is the issue lies there. maybe it has do to with siyah but my guess would be a faulty ROM. Try wiping cache and dalvik-cache, see if it helps. You can also run Fix Permissions, that's never a wrong move. Besides that, if you are not yet dual booting, you can create a secondary rom (not the same as yours!! preferably stock rom) and see if the problem persists. If it's gone, your rom is to blame, if not maybe it's a bad kernel flash.
[Galaxy S II Original Android Development] johnbeetee:
So you're saying that it's working ok on your stock rom?

In that case I must have a look at mine, and try some of your solutions. On my side it's working ok on Hydrogen (AOKP), but not on stock.....

edit: ...thinking back, now that you've mentioned it, I do remember it working ok on stock LPQ, but since then I've moved to LPD, so it must be rom related like you've said.....
[Galaxy S II Original Android Development] sobirin90:
yeah..me too have this issue. Not sure why though. I like to have my led off all the time and only turn on when have any notification, as Im using pink anymode screen protector now..

Anyone got any idea how to fix this..don't get me wrong the kernel is great, but occasionally freeze and reboot issue really get me on the nerves. :p

Cheers :)
[Galaxy S II Original Android Development] CRCinAU:
Interestingly enough, I just reflashed 3.3.3d, installed ExTweaks, made sure the headphone amplification was set to 0 (ie don't screw with my audio stream), rebooted a couple of times (just cos), and the card reader now seems to work perfectly.

Go figure.
[Galaxy S II Original Android Development] Hawkeye1103:
I was wondering if Siyah kernel 3.3.3d has the feature that disables the second core when phone screen is off??? Read the first post but didn't find anything about this feature. If this is possible and not included it would be a great feature.

Thank you.
[Galaxy S II Original Android Development] #illidan:
There is a script in this thread to do that. Just search for it.
[Galaxy S II Original Android Development] javikiller:
Hello,

I have installed Siyah 3.3.3d on the lastest version of MIUI (2.7.13) and I have some issues. I can't switch on/off auto rotation, flight mode or auto brightness.

How can I fix these issues?

Thank you.
[Galaxy S II Original Android Development] Hawkeye1103:
tried to find it... had no luck...:( sry
[Galaxy S II Original Android Development] blaex:
nope, only hdmi via mhl adapter.try to change the hdmi port.
[Galaxy S II Original Android Development] tlf55:
To many bug with this kernel .. The only pro i can give to 3.3.3d it's his batterylife better than 3.3.2 .. But 3.3.2 is at least very stable ..

back to 3.3.2 for me !
[Galaxy S II Original Android Development] endva3:
Hi.Im using siyan 3.3.2 and 3.3.3d but BLN dont work for me.. :/ when i press BLN test in extweaks BLN some time TEST BLN work. When i have notification-missed call,sms... (BLN ist ON in extweaks) LED dont notifice me.. :(

I have wipe data/factory reset....its siyan kernel bug?

im on CM9 12.7build and tried 15.7 but same problem.

SORRY MY ENGLISH
[Galaxy S II Original Android Development] tzyn:
BLN for missed calls and SMS on CM9 works fine for me with Siyah Kernel (3.3.2 and 3.3.3d). I'm on CM9 since june and switch to current nightly every 3-5 days. Never had problems with BLN.
[Galaxy S II Original Android Development] core_x:
Checked that?

http://xdaforums.com/showpost.php?p=25712328&postcount=7686

and

http://xdaforums.com/showpost.php?p=25713177&postcount=7688
[Galaxy S II Original Android Development] endva3:
You have enabled BLN with extweaks? Works BLN with FB aplication too? in options FB is LED notification.

In extweaks dont work BLN test.
[Galaxy S II Original Android Development] javikiller:
No one can help me?
[Galaxy S II Original Android Development] eskostar:
I use latest MiUI with latest Siyah and all of those work fine for me, seems like a user problem and non kernel related.
[Galaxy S II Original Android Development] Hawkeye1103:
Can someone help me with this script... haven't been able to locate it:) i've been told it's in the thread:)))
[Galaxy S II Original Android Development] johnbeetee:
it's in the other thread siyah Q&A:

http://xdaforums.com/showpost.php?p=28241419&postcount=2066
[Galaxy S II Original Android Development] Sepharite:
I used OTG, plugged my USB stick. I couldn't find it using Root Explorer but the instant I unplugged it, it tells me in the notifications "Removed SD card: SD card removed. Insert new one".

My SDcard and EMMC are both intact. Any ideas?
[Galaxy S II Original Android Development] aceian:
Its named usb storage inside file manager...

Use stick mount app by chainfire from market... It works for me
[Galaxy S II Original Android Development] tzyn:
Yes, i just activated it with extweaks. FB dunno, i dont use FB notifications (battery eater).

BLN Test sometimes doesnt work. But that is not important as long as it works for all notifications. ;-)
[Galaxy S II Original Android Development] carlos67:
@John

Interesting and I'm tempted to try this out because I am using pegasusq governor. But, will this cause wake-up laginness because only 1 core active at moment of waking the phone up.

If you have tried this script, does it cause lag on wake? Has anyone else noticed any issues waking the phone from deep sleep when using a 2nd core off on sleep script?

Thanks :)
[Galaxy S II Original Android Development] #illidan:
No difference at all in wake up times with or without the script. I use widgetlocker as well & its all smooth. The script runs every 1 second so it will get the second core active also immediately after you switch on the screen.
[Galaxy S II Original Android Development] johnbeetee:
The first part of your anwser is correct, and the script should present no problem at all.

The second part (and I think you'll find this interesting information on how it works):

most of the time the script doesn't run at all (else it would cause wakelocks)

it tests the contents of the files

/sys/power/wait_for_fb_wake

/sys/power/wait_for_fb_sleep

using the cat command, but these two files are handled in a special way by the system: they are kept locked and not readable by other processes, until the event (awake or sleep ) occurs, and only then they are given a value (AWAKE or SLEEPING), and unlocked, so they are readable. So at each of the cat commands, the script is just waiting for the file to become unlocked, and as soon as this happens it waits 2 seconds (to give the other file a chance to be locked) while the script itself is performing whatever it should do ( the part behind the &&) and after that it goes on the next cat command, and will be waiting there (doing nothing) until that next event occurs

this goes on endlessly, because of the endless loop (while) construct

or until you kill the process (script) or reboot.
[Galaxy S II Original Android Development] #illidan:
Thanks for the explanation. I didn't actually dwell into the script to understand how it worked but now I do & it is very interesting.
[Galaxy S II Original Android Development] crisgen:
@GM

Is there in your plans an upgrade of recovery touch from v.5 to v.6?

A new format that allows incremental backups to restore and faster backup sounds very good
[Galaxy S II Original Android Development] aviral1990:
Can anyone explain to me what is meant by this statement in extweaks: "In most of the kernels, there are 2 steps for GPU, but in siyah there are 3 and the third step is disabled by default"

So i get it that siyah offers 3 steps for scaling..100,160,267 but what is meant by third step is disabled by default? that means the gpu never goes to 267?

Please do enlighten me, i wasnt able to clarify this doubt in other threads//

thanks
[Galaxy S II Original Android Development] antt00:
Both second n third steps are set to 267 by default and the up threshold to third step is also set to 100%. making it seems like there is no third step.
[Galaxy S II Original Android Development] aviral1990:
In mine itsnt..by default..the steps are 100,160,267

so what does third step disabled by default mean here?

thanks
[Galaxy S II Original Android Development] carlos67:
Very interesting indeed. How have you found the effect of running this script in terms of wake up speed from deep sleep and better/same/worse battery usage? I use widgetlocker too btw (same as #illidan).

Edit: sorry if this should be on discussion thread.
[Galaxy S II Original Android Development] johnbeetee:
No adverse effect whatsoever.....and battery savings: depends on your settings: governor/hotplug settings/thresholds...

performance oriented settings, might yield some more savings than battery oriented ones (which are less dualcore intensive anyway)
[Galaxy S II Original Android Development] carlos67:
Thanks John, may well give that a try later today. In the meantime, I'm off for a swim!
[Galaxy S II Original Android Development] Krendelrus:
In the Galaxy Note forums it appears that hardcore has fixed the bluetooth in 4.0.4 sammy roms

maybe his fix will work for S2 4.0.4 roms too

link to his site/news article

link to the newest hardcore note kernel source code with bluetooth fixed in 4.0.4 sammy roms
[Galaxy S II Original Android Development] xfce4:
Hey guys anyone having trouble with ending a call by headphones' button (on only MIUI maybe)?
[Galaxy S II Original Android Development] Tungstwenty:
Thanks for the info!

Unfortunately, his patches don't touch the BT sources at all, except for the config file which is already the same as Siyah's.

While it's good news for N7000, it still goes in line with what I stated in the Camera/Video Fix thread: it was possible to have a workaround for those on the userspace (replacement of 2 libs), but for bluetooth that solution doesn't seem that simple and probably it will really need changes on the kernel side until it works :(
[Galaxy S II Original Android Development] The Undertakerr:
Hey Tungstwenty, I'm looking at the speedmod topic for the galaxy note here:

http://xdaforums.com/showthread.php?t=1673072

Last update of kernel sources on XDA seem to have been on 2nd July 2012 (speedmodKernel K3-5)...

Maybe he didn't upload the sources with this bluetooth changes yet?

EDIT: Sorry I saw it wrong. He put up the sources here: http://touristinparadise.blogspot.nl/2012/05/samsung-galaxy-note-ics-download.html

So the sources must be correct
[Galaxy S II Original Android Development] Krendelrus:
So, assuming that S2's and Note's hardware is very similar, how is it possible for bluetooth to work on the Note and not on the S2?

hardcore used latest sources from Samsung, maybe that is case?
[Galaxy S II Original Android Development] Tungstwenty:
That would mean fetching a bunch of files from the Note sources (the ones from the driver) and putting them on top of S2's which a) I'm not sure whether it will work and b) it looks a bit too complex for me to handle, as I don't think it's just a matter of replacing files but also messing with the configs, defines, etc.
[Galaxy S II Original Android Development] gokhanmoral:
v3.4 is up

I still have 12-13 pages to read in this thread (I will read them when I am back from holiday)

I could connect to my computer at home and updated the kernel to latest update6 sources (except for the wifi part which is something that I don't want to touch as it works and the current wifi driver is newer than the one in the latest sources)

and updated to linux 3.0.37 (you should not notice any difference but some people like this for some reason that I don't know)

and fixed /vendor->/system/vendor symlink for cm9 based roms.
[Galaxy S II Original Android Development] viscocesco:
Thank you GM!

I'll test on Resurrection Remix 2.6, 3.3.3d works very well so I hope that new version have same performance and battery life.
[Galaxy S II Original Android Development] Tungstwenty:
I was hoping this new update from Samsung would address the camera+video+bluetooth issues in 4.0.4 but ... no, these were not the sources you're looking for :D
[Galaxy S II Original Android Development] xXCorleoneXx:
Thanks GM.

until now works all good.

Also wifi,BLN and so on.

No Sod

im on VK rom.

Very fast and smooth.

no problems yet.

testing this 20 min.
[Galaxy S II Original Android Development] diemadedrei:
What exactly is the updated sources. Just to understand what this might change, because I had SODs with 3.3.3d.
[Galaxy S II Original Android Development] AJ Newkirk:
Any chance of MMC brick bug in these new sources?
[Galaxy S II Original Android Development] :
No. Disabling mmc_cap_erase is the first thing he does.
[Galaxy S II Original Android Development] xXCorleoneXx:
This question is unnecessary, because this is always the first thing that makes gm.

in each kernel.

every kernel he makes is save.
[Galaxy S II Original Android Development] AJ Newkirk:
Understood. Thanks for the info.
[Galaxy S II Original Android Development] carlos67:
For me 3.3.3d is the top of the mountain. It doesn't get any better than this. I've used many,many kernels over the last 2 years but this one is in a league of its own.

Its a masterpiece.

Thank you Gokhan :good:
[Galaxy S II Original Android Development] tlf55:
When i want to put only single core in hotplug mode it come back to dual core .. how do i disable the second core then ?
[Galaxy S II Original Android Development] robertobsc:
Guessing that are many updates, since the 3.3.3d was based in update 4 sources.

I'll take a look in source code, I'm curious.

Edit: also flashed and seems smooth and responsiveness as 3.3.3c / d. Wi-fi seemed with a little worse range, but may be only my imagination ;)

Stock XWLPG
[Galaxy S II Original Android Development] mathsmart:
Im really confident that 3.4 is smoother than 333d right in tapatalk its much smoother and less laggy

THANKS GB we really appreciate the hard work !!

swagga baby
[Galaxy S II Original Android Development] Anfa900:
Someone can share his extweaks configuration for better battery life
[Galaxy S II Original Android Development] #illidan:
Update sources are kernel sources released by samsung from time to time. Flash the latest version to see if you still have SOD.

Which governer are you using? Pegasusq doesn't respect the hotplug pram. You need to use max_cpu_lock for that which is in ExTweaks.

Well based on my tests it seems that using a single core when screen is off does more harm than good but that may depend on how your governer prams are set whether it's towards battery or performance. Mine are set somewhere in the middle for optimal battery & performance. There are very few reasons when you need the screen off but the phone awake & one of which is listening to music. When second core is switched off cpy spy shows 500 MHz to be used consistently but with it on & pegasusq being used to decide hotplug logic I get a constant usage of only 100 MHz which is a huge difference & which shows that two cores are indeed better than one but again these are my tests & your results maybe be different based on different parameters. Just my 2 cents a of input.
[Galaxy S II Original Android Development] tlf55:
I'm using pegasusq .. I want to use only one core what should i do ? When i select "Single core" in settings then i exit extweak it goes back to dual core ..

Edit : Should i use an other governor with CPU Hotplug set to : Second core always-off ?

that's the command "Max CPU lock" that doesn't work in extweaks .. When i put it to single core and then exit normaly extweak, it goes back to dual core .. (i read like you said that this command is only for Pegasusq, so should i use an other governor and leave this command to dual core but put the CPU hotplug command to " second core always-off ?)
[Galaxy S II Original Android Development] MaKTaiL:
New Siyah 3.4 is really smooth. The best so far.

Why isn't it working so good for stock 4.0.4 yet?

I thought new sources were supposed to fix it. I guess Sammy will release another update soon.
[Galaxy S II Original Android Development] #illidan:
Because it didn't have the stuff need to get what wasn't working to a working state.

For the hotplug pram you need to use a governor other than pegasusq as it won't work with that. Max cpu lock pram in ExTweaks is only for pegasusq & it works. You're saying that the setting in ExTweaks doesn't stick to single core mode? Could be a bug. Are you on the latest version?
[Galaxy S II Original Android Development] auto_freak:
flashed 3.4 on Resurrection (1st rom) & WanamLite (2nd rom). Let's hope the battery has improved a bit.
[Galaxy S II Original Android Development] viscocesco:
Flashed now on Resurrection Remix. ATM all work fine.
[Galaxy S II Original Android Development] johnbeetee:
You do have a point there...Settings do play a role in this, and to be honest, I didn't test in a situation where there will be a reasonable amount of actitvity when screen is off (like music playing,as you indicated). So I think (as with all configs and settings you will find on xda) , it's a matter of personal trial and evaluation, and see if it suits you. Something along the lines of : if the shoe fits.....what the heck, buy them already.. ! :laugh:
[Galaxy S II Original Android Development] ehmjay:
can't download .. "too many connections" :) anyone mirror 3.4 pls?
[Galaxy S II Original Android Development] tasirith:
http://www.mediafire.com/?xrb660a1xp6dnmw
[Galaxy S II Original Android Development] ehmjay:
thanks
[Galaxy S II Original Android Development] kem1337:
55min screen 4h uptime 52% battery. Kk....

wanam 12.2 siyah 3.4
[Galaxy S II Original Android Development] tlf55:
Yes i'm on Siyah 3.4 now, and the lastest extweaks from the market .. it don't work with me, it really don't stick to single core.. I put it to single core it says MAX CPU LOCK : 1 then i exit extweaks then when i go back to it, i see it's in Dual core mode .. Can you try ? You put Single Core mode then exit Extweaks then go into it and you will see that il will be on Dual core mode ..
[Galaxy S II Original Android Development] PakkaZA:
Try reboot after changing settings first, as these settings may be applied at boot time. Then check EXtweaks again
[Galaxy S II Original Android Development] tlf55:
Ok i'm will try right now, i have an other issue, since i instal the 3.4 i have a Gtalk Async conn Waterlock in Partial waterlock .. I don't have Google talk or something like that, i've frozen the "Talk" application and auto-sync is off .. how can i kill this waterlock ?

Edit : Still not working .. I've changed to single core, then reboot than go to extweak and it stay on Dual core ..

Edit 2 : before installing 3.4 i used kernel cleaner script to be sure ? maybe i shouldn't ?

Edit 3 : Found the problem with Gtalk async conn waterlock (it come from i had an old Google Maps app, updated it and it's gone) anyway for the single core can't found the answer ..
[Galaxy S II Original Android Development] gokhanmoral:
I have uploaded the files to www.gokhanmoral.com as d-h.st seems to be down now.

links are updated on the blog.
[Galaxy S II Original Android Development] vitoski:
Guys, I have a problem with led fade (breath). Even if the option is disabled in exTweaks still my buttons fade out.

I am on CM9 nightly (17.07). If I disable led timeout and fade effect in exTweaks, then my buttons light up and stay until I turn off the screen.

In fact exTweaks says for led timeout that it should be disabled if ROM has this settings, but according to the above it doesn't work with CM9:-(

Anyone can help?

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[Galaxy S II Original Android Development] k4bbe:
@Gokhanmoral

A small question regarding dual booting... How difficult would it be for you to add an option to boot directly to the 2nd or 1st rom from the recovery menu, or to add an option to increase the 3 second boot countdown? The reason I ask is that I often miss the countdown when flashing stuff and have to go through the boot procedure, shutdown and start over. I've lost count of the hours I've wasted doing that :D.

An option for a longer boot countdown or to boot directly to a specific rom would be a useful feature... Maybe it's something you have already thought of and discussed but couldn't find mention of it in a search of the thread.

Siyah 3.3.3d Dual boot.

Primary Rom-Wanamlite 12. 2

Secondary Rom-Paranoidandroid 1.6a
[Galaxy S II Original Android Development] Evollution:
Hey give and me your tweaks
[Galaxy S II Original Android Development] mierdaseca:
Im using ICS (Slim ICS).Could I boot Jelly Bean as second boot?
[Galaxy S II Original Android Development] kem1337:
No obv... ics is ics jb is jb..

wanam 12.2 siyah 3.4
[Galaxy S II Original Android Development] kem1337:
Default except 100-1200 and a bit UV @cpu$gpu

wanam 12.2 siyah 3.4
[Galaxy S II Original Android Development] yahyoh:
gokh thank a lot for the new update its so smooth and really thank u for fixing vendor thingy :good::good: :highfive:

i'm testing battery now :cool:
[Galaxy S II Original Android Development] tlf55:
Does a kernel change how mobile data network ? it seems that until i'm on 3.4 i don't receive every message instanly in whatsapp
[Galaxy S II Original Android Development] yahyoh:
hmm look good standby in 3 hours didnt loose any battery :victory::victory:
[Galaxy S II Original Android Development] quijote1:
Folks,

I´m on 3.3.3d with SlimRom ICS. Since installing this version, my phone has been turning itself on and off repeatedly. I have tried various tricks to try to tame it - taking out the battery, switching to airplane mode, etc. No cigar! I'm going to upgrade to 3.4 and see if that makes any difference. Obviously, having the screen on repeatedly hurts my deep sleep.....

Any ideas? I'll see if 3.4 helps.....
[Galaxy S II Original Android Development] duff91:
You try to flash ultimate cleaning script and then flash siyah?

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] shubham.dhand:
battery backup is not good with 3.4 version..

1% battery drains in a minute.
[Galaxy S II Original Android Development] Ok_Kaleidoscope5109:
are there plans to include cwm 6.0 touch?

thanks!
[Galaxy S II Original Android Development] pikachu01:
Cannot reproduce. Battery life is fine here with 3.4. Go dump a BetterBatteryStats log and post it in the BetterBatteryStats thread to see what's really draining your battery.
[Galaxy S II Original Android Development] :
Seems like linux .37 is draining a more battery, fluxi updated his kernel to .37 but reverted later.