yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] evonet:
IIRC b2 has remedied the wifi toggle issue. Flash it and find out :-)
[Galaxy S II Original Android Development] fusionjack:
just curious, is siyah 3.x create or put scripts to init.d folder? i'm asking this because i don't see init.d folder since i switched to ics.

btw, i manage to have 1 hour screen on by using 10% battery. is it normal for extended baterry or it can be better? currently using miui v4 and siyah 3.1.2 with undervolting.
[Galaxy S II Original Android Development] antt00:
Siyah kernel does not create or put scripts in init.d folder. It is usually the rom you are using that does this. If you want to use init.d scripts, you can just manually make an init.d folder and insert scripts in it.
[Galaxy S II Original Android Development] fusionjack:
ok thanks
[Galaxy S II Original Android Development] hshah:
How do you make then run on boot?

Sent from Samsung Galaxy S II
[Galaxy S II Original Android Development] antt00:
Make folder /system/etc/init.d (if you already got this folder you can skip this)

Make a script using notepad++ on pc OR copy an existing script and modify it.

Fix permission to 777.
[Galaxy S II Original Android Development] Ven0m:
I didn't really care to unmount it and there was no corruption, however I might just get lucky (and there were quite a few restarts). I'm not sure if people would like extra delay if there was any caused by such ntfs-fat32 check maneuver, but for me it would be useful. If there's any risk of data loss, I'll just add un-mount to Tasker's shutdown event handler (I guess it's also possible in kernel, but I'm no Android developer).

There's also an interesting exFAT post - http://xdaforums.com/showthread.php?t=1371621. He managed to get exFAT to work, but vold is said to mess it up if it runs before card is mounted as exFAT.

By default, my SDXC card (SanDisk, and it's class 6, while manufacturer site says 10) was formatted in exFAT. I heard it's a typical way to format them. If you could make exFAT, NTFS, and FAT32 be all recognized and not getting corrupted, it would be sweet. exFAT should offer better performance than NTFS (according to my plain guess).

If it's too much to ask, that's ok. SiyahKernel is sweet even without these features. To be honest, the only major downside that I can think of is that now I keep forgetting where I put my phone charger.

---------- Post added at 02:19 AM ---------- Previous post was at 02:11 AM ----------

I put one script (with .sh extension) there, and to /etc/init.d/ and it didn't get executed (ntfs mount), however maybe it was because it required su.
[Galaxy S II Original Android Development] antt00:
Does it start with

#!/system/bin/sh

And is your permission correct?
[Galaxy S II Original Android Development] omniwolf:
GM has already stated that he has a fix for this in the next beta

10% for 1 hour is pretty good, depending on what you're doing. i will get maybe 40mins for 10% with a mixture of twitter, webpages, and a youtube vid or two on the stock battery.
[Galaxy S II Original Android Development] rlorange:
GM: Have you seen the code for LiveOC? This is the state-of-the-art overclocking method used for the sgs1 and nexus s.

I'm not sure if it can work on the sgs2 but it is amazing

http://xdaforums.com/showthread.php?t=1419274
[Galaxy S II Original Android Development] Appumon123:
How do you fix permissions for a script?

EDIT: nevermind.. got it.. 777 means rwx for all.. :)
[Galaxy S II Original Android Development] akira888:
Hi Guys,

Maybe I am traumatized.. or I am paranoid because I bricked my phone once before......

May I please have your confirmation that the latest rc6 on GM's site is OK to flash? Camera working? there will be no problem of wiping data/factory reset/ dalvik cache before I change to another kernel/ROM?

The reason I stick with rc6 is that it seems the resurrection ROM is still applying the old mount point definition. so rc6 is the only version I can use ATM until the resurrection ROM has been updated so as to avoid apps being not working when using TB to restore.

Please correct me if I am mistaken. Thanks.
[Galaxy S II Original Android Development] Appumon123:
It has been confirmed that rc6 is perfectly ok to flash.. u can search the thread if you want to be sure..
[Galaxy S II Original Android Development] Crescendo Xenomorph:
Set the lower gamma >5 and max gamma 20. Set also gamma shift >5.
[Galaxy S II Original Android Development] rlorange:
Guys I just discovered that if you

echo /sys/class/misc/notification/notification_timeout

Use a value in MILLISECONDS not Seconds. So my example in an earlier post was:

echo 960 > /sys/class/misc/notification/notification_timeout

This will time out in just under 1 second or 960ms.

echo 96000 > /sys/class/misc/notification/notification_timeout

Will timeout in 15 min.

I've made a script which will make a 1.5second soft key time out and 15min bln time out on every boot. You can change them with any text editor.

http://db.tt/FkjM6Rh8

Place in /etc/init.d and change permissions to rw-rx-rx with root explorer.
[Galaxy S II Original Android Development] hshah:
Right, got that working :)

However, that doesn't solve the BLN issue which no longer works with the latest beta :(

---------- Post added at 06:17 AM ---------- Previous post was at 06:14 AM ----------

Do you not need the echo 1 for notification_enabled as well?
[Galaxy S II Original Android Development] shong84:
flased beta5, feel that the color abit yellowish, is this normal?
[Galaxy S II Original Android Development] LNJ:
Reverting back to CF-ROOT from beta 5 messes up the capacitive key lights. Mine is set to always off but after reverting it stays on until screen turns off. Very annoying!
[Galaxy S II Original Android Development] shong84:
same issue for me.

anyone can guide me how to flash back to previous version?
[Galaxy S II Original Android Development] Daemos:
Can confirm recovery is gone.

Used CWM app to flash zimage of beta4 kernel (extracted from beta 4 cwm zip) and recovery is back.
[Galaxy S II Original Android Development] Simongiar:
Works pretty well, but battery drain it's awful. The Android OS it's draining almost the same ammount of battery than the screen. 10hs medium use, and complete depleted
[Galaxy S II Original Android Development] addison8406:
download beta4(for odin) then use darkyota to flash it...
[Galaxy S II Original Android Development] shong84:
thanks,

I have used CWM app to flash zimage of beta4 kernel (extracted from beta 4 cwm zip) and recovery is back.
[Galaxy S II Original Android Development] eric-filth:
Gokhan thanks again. This kernel is pure performace i liked.
[Galaxy S II Original Android Development] bala_gamer:
People having rom manager can use cwm 4 temporarily until the next beta
[Galaxy S II Original Android Development] prommindh:
Thanks for the tip.. confirmed that after flashed beta 5 the recovery just vanished

followed the above advise then you got the recovery back but it brought the phone back to beta4 as well :confused:

tried the same method with extract zimage from beta 5 but the phone stuck at boot logo :mad:

guess have to wait for beta 6 ;)
[Galaxy S II Original Android Development] Auridran:
zImage is the kernel, so it makes sense you went back to Beta4 after you flashed it.
[Galaxy S II Original Android Development] rlorange:
Super fast charge script!

Guys thought I'd share this with you. This script will allow 950mA charging on AC power but leaves USB standard. It's an init.d script but I think extweaks prevents it being executed at boot.

Execute with root explorer or a script runner.

WARNING! Stock Samsung chargers only put out 700mA.... I don't know if trying to draw 950 will damage it however using a 1000ma USB charger is what you should use without issues.

Enjoy!

http://db.tt/JQeZBf3i
[Galaxy S II Original Android Development] gokhanmoral:
I have just woke up and deleted beta5.

I will re-upload it again.

sorry for the loss of recovery. I am trying to fix touchscreen lights problem and add it to beta5 as an excuse of the loss of recovery in the yesterday's release.
[Galaxy S II Original Android Development] sansunggalaxys2:
Does it only work with siyah kernel?
[Galaxy S II Original Android Development] steve_clifton:
Am I the only one then who likes b5? Its working great and batt is good for me!
[Galaxy S II Original Android Development] Qliratu:
Thanks for re-uploading the file. Can u tell us something about the weird collors we are seeing (warm collors?) and is there a way to disable it ourselfs?
[Galaxy S II Original Android Development] rlorange:
Sure does uses the same parameter file. Was made for GB siyah
[Galaxy S II Original Android Development] addison8406:
never mind~~~~:)
[Galaxy S II Original Android Development] rlorange:
edit: misread, not sure check in /sys/misc/charging_current
[Galaxy S II Original Android Development] gokhanmoral:
you can set min_bl to 20 and min_gamma to 1 (or maybe 2) to get higher brightness.

I did not change any screen value. that is because of the lowest brightness is used more with the current autobrightness behavior.

the lowest level looks a little yellowish.
[Galaxy S II Original Android Development] rlorange:
Yes it does. Try activating it with nstools app from the market. Works for me. You can Also tweak governors and undetvolt with this app
[Galaxy S II Original Android Development] hshah:
I'm confused... why do I need to activate it using that? Can't I just add another line to the init.d script with the echo 1? :confused:
[Galaxy S II Original Android Development] rlorange:
Sorry yes. I use nstools app to activate it. Cheers I'll update my script
[Galaxy S II Original Android Development] rlorange:
Nstools will active the new native bln.
[Galaxy S II Original Android Development] Appumon123:
Im on 3.2beta-1

Used nstools but bln timeout i not working.. So i'm guessing it works in b2-2?
[Galaxy S II Original Android Development] hshah:
Whatever I do the BLN just doesn't work as it should on my SGS2 :(

---------- Post added at 06:46 AM ---------- Previous post was at 06:44 AM ----------

This is the line that NsTools uses:

echo 1 > /sys/class/misc/backlightnotification/enabled
[Galaxy S II Original Android Development] rlorange:
The timeout only works with the echo via script in beta2-2 download it in my earlier post and place in init.d change permissions and reboot
[Galaxy S II Original Android Development] rlorange:
Ok then:

echo 1 > /sys/class/misc/notification/notification_enabled

Funny for me nstools seems to activate both.

I have cm9 sensors touch light ticked "off" maybe this is having an effect. I don't know
[Galaxy S II Original Android Development] gokhanmoral:
I forgot to tell you that backlightnotification and notification misc device folders uses same variables and functions.

there is single bln in the kernel.

in GB kernel I was using two seperate implementation in a single file and activating only one of them depending on the rom type.

but now, both of them are active.

since there is no blinking support in the native implementation yet, I wanted to keep cream's bln implementation active for cm9 as well.

if you don't mind your keylights turn off after turning on the screen while there is an active led notification you can use bln control or pro to have blinking.

by the way I fixed blinking problem in cm9 and I will upload it in half an hour.

anyway.. since having two seperate implementation active at a time I merged them.

if you activate bln in one of them, the other one will become active.

but there will be only one notification.

some apps implement timeout in userspace. so, I do not recomment you to use both nstools and blncontrol to configure timeouts.

if you use scripts and use /sys/class/misc/notification folder, you won't need any additional app but there will not be blinking support.
[Galaxy S II Original Android Development] gokhanmoral:
I found customvoltage interface more interesting.

and I saw it in nstools' source code yesterday.

I was searching for such an implementation to make it compatible with an existing tool.

thanks for this post. I will look at them and add internal voltage modification to the kernel.
[Galaxy S II Original Android Development] rlorange:
Sounds great. internal voltage control will make 1500 and 1600 MHz stable on many more devices and save juice on lower frequencies.

If bus freq control can be added as well then many in-between freq can be attained as well as far quicker ram speeds... of course bus OC comes with more danger.
[Galaxy S II Original Android Development] rlorange:
Oh also GM does the native bln implementation cause a wake lock like the original?

Also echoing available frequencies doesn't seem to work it reverts instantly to whatever ex tools has set
[Galaxy S II Original Android Development] coloxim:
I didn't understand one thing...if I use the app it causes more battery drain? Is better use the script?

And in the future is possible set blinking bln by script?

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] gokhanmoral:
yes. there is no implementation without wakelock for now.

you cannot echo anything you want. you have 18 steps to choose. if you echo 350 1350 or any other freq which are not available in the set it won't apply.

and you have to echo them sorted.

the echoed values should contain 1000, 800 and 500. you cannot remove those steps.

see /sbin/ext/post-init.sh for examples.
[Galaxy S II Original Android Development] rlorange:
Yes I tried allowed values I even edited the file directly using root explorer but after saving the file it reverts
[Galaxy S II Original Android Development] gokhanmoral:
no, I didn't say that. for now both of them should be the same.

maybe I will implement blinking or breathing one day. then kernel will hold the wakelock instead of app, or maybe not...

hard to tell what will happen in the future...
[Galaxy S II Original Android Development] gokhanmoral:
I guess you want proof :)

C:\Users\gm\android-sdks\platform-tools>adb shell
~ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
1400000 1200000 1000000 800000 500000 200000
~ # echo 1400 1200 1000 800 500 200 100 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
echo 1400 1200 1000 800 500 200 100 > /sys/devices/system/cpu/cpu0/cpufreq/s
caling_available_frequencies
~ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
1400000 1200000 1000000 800000 500000 200000 100000
~ #

EDIT: this setting should be applied in very early stages of boot or you will have a softboot (UI will restart) when you use a new freq step.
[Galaxy S II Original Android Development] antt00:
I have had no problem echoing values with beta 1, 2 or 2-2. All of them works. Make sure you have 500, 800 and 1000 in the steps.
[Galaxy S II Original Android Development] coloxim:
Breathing???

Wow...cool...;p

Last question, in your next release can you re-add smooth step?

Because I use it set to 0 for use much more the 1000 frequency and a little bit less 1200...with smartass

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] rlorange:
Oh I see I was using 1500000 instead of 1500 as I saw in the file.

Can I add my own to sbin/ext/post-init.sh so it can be accessed via extweaks?
[Galaxy S II Original Android Development] johnbeetee:
just had a glance at /sbin/ext/post-init.sh..

so the values should be entered as Mhz? Having looked at the content of scaling_available_frequencies, these are values in Hz...maybe that's what didn't work...other than that all conditions mentioned above were met...
[Galaxy S II Original Android Development] Appumon123:
GM, is there any advantage to using all the available frequency steps, like better battery life or performance?
[Galaxy S II Original Android Development] rlorange:
Yep that's the mistake I made too. It's working now :)
[Galaxy S II Original Android Development] maczaros:
Hi gokhan!

Can you tell me (us), will my problem by fixed soon or later ?

Link to post #5494
[Galaxy S II Original Android Development] eric-filth:
Gokhan i want say for you thank you.

Last CM9 (29-04) with Siyah Kernel 3.2 Beta2-2 running very smooth with good performace. All my undervolting settings are ok and with good Deep Sleep.
[Galaxy S II Original Android Development] gokhanmoral:
that is something that I cannot reproduce or observe.

since I don't know the reason of that problem I have no idea why you have it.

thus, I cannot answer your question about when it is fixed... for me (on my device), there is no such problem.
[Galaxy S II Original Android Development] gokhanmoral:
your UV settings work in v3.2b2? that is very hard to achieve for a kernel dev! ;)

anyway.. I think I can make bln breathing possible but I will upload v3.2b3 now and implement it in b4.
[Galaxy S II Original Android Development] coloxim:
Iper-super-stra-cool....

Davvero figo!!!

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] gokhanmoral:
v3.2b3 is up.

changes are tiny. just 2 lines...

only touch sensitivity on charge and cm9 bln blinking...
[Galaxy S II Original Android Development] fantom2007:
On HyDrOG3N-ICS (AOKP)

Very smooth and good touch.
[Galaxy S II Original Android Development] Nos_20:
Downloaded and installed... the jitter when on charge is fixed.

GT-I9100

D4 Rom

Siyah Kernel
[Galaxy S II Original Android Development] CandyAndy:
Hmm. After installing this on F1 ROM my phone hasn't gone into deep sleep, the usage went from -90mAh (also not so good) to -120mAh. Always want to try Siyah as it should be one of the best kernels out there but they just don't work with my specific phone. Would be interesting to know why
[Galaxy S II Original Android Development] bencairns:
Is it alright to skip resetting ExTweaks settings in cwm going from b2 to b3
[Galaxy S II Original Android Development] eric-filth:
For God yes, working my undervolt settings.

200 - 1200 ( 850 - 925 - 950 - 1075 - 1150)
[Galaxy S II Original Android Development] Ven0m:
I hadn't got that line, but even adding it didn't help - after reboot the card wasn't mounted. When I opened Terminal Emulator, typed su, then /system/etc/init.d/mount_ntfs_sdcard.sh it kicked in. Permissions were set to 777 (rwxrwxrwx)
[Galaxy S II Original Android Development] ephraim:
Good day GM, thanks for the kernel but unfortunately i can still see the small jittering while charging in v3.2b3. In v3.2b1 all is good. Maybe you can take its values and put it in b3? Just a suggestion. Thanks :)
[Galaxy S II Original Android Development] gokhanmoral:
you don't have to reset extweaks between b2 and b3.

there is no config related change in b3.
[Galaxy S II Original Android Development] pikachu01:
Try running the script in Script Manager and see what error it gets. Also, remove the .sh extension and put a number e.g. s98 in front of the filename.
[Galaxy S II Original Android Development] gokhanmoral:
hmm, maybe it happens on some chargers.

right.. I will revert back to old settings on b4 (already announced)

what about touch sensitivity on battery? honestly I do not feel any difference in scrolling between 3.0 3.1 and new settings... latest one is the same as GB one and I feel that my touches are sometimes missed.
[Galaxy S II Original Android Development] pikachu01:
The latest touchscreen sensitivity on battery has better swipe detection but a lil worse touch (button press) detection. Maybe somewhere in the middle between that is good.
[Galaxy S II Original Android Development] ApriliaM3:
I've noticed on v3.2b2 and also v3.2b3, on every boot, my phone boots normally but then once booted, it does another "hot" boot.

It doesn't boot all the way back to the siyah logo but boot animation runs again, homescreen rebuilds and then it's ok to run.

Anyone else experiencing this issue?
[Galaxy S II Original Android Development] ephraim:
The one on battery is all good. Tge only problem is with the charger plugged in :)
[Galaxy S II Original Android Development] luexi:
Tried the b3

As usual The backlight is still unable to ON after a notification is received. :)
[Galaxy S II Original Android Development] vastac13:
Sir Gokhan is there a possibility to add USB drivers for USB - DAC support? I'm no expert in coding and it does include some ALSA hacksorcery to bypass and redirect the audio signals(digital) to USB and use external/portable to convert that signals to analog(PCM) then out to headphone jack of that unit
[Galaxy S II Original Android Development] rauschkugl:
Yes it's the same for me. Touches don't get recognized pretty often for me.
[Galaxy S II Original Android Development] Gammelgustav:
What about a GUI-Bootloader ;D
[Galaxy S II Original Android Development] jmajuri:
Same thing here. Need to press sometimes multiple times before something happens.
[Galaxy S II Original Android Development] FallenOut:
i think my question was missed >.<

the link

i do like custom bootscreen alot
[Galaxy S II Original Android Development] mr_magreb:
The SK v3.1.2 work on Cyanogen 7.2.0 RC1?
[Galaxy S II Original Android Development] Auridran:
Your question is answered right in the thread title itself. You didn't even have to read the thread to figure this out. "ICS" means "Ice Cream Sandwich" which means, no, this kernel does not work on CM7.
[Galaxy S II Original Android Development] ssauger:
No, only on ICS ROM. Cyanogen 7.2 is Gingerbread.
[Galaxy S II Original Android Development] mr_magreb:
thx. if i need the last SK for my cyanogen, where do i find?
[Galaxy S II Original Android Development] Appumon123:
In GM's website, www.gokhanmoral.com, scroll over to older posts

Hope this clears your doubt, and next time

use the search in xda

. Theres a seperate thread for gingerbread Siyah kernel.
[Galaxy S II Original Android Development] mr_magreb:
Thx!
[Galaxy S II Original Android Development] hawkerpaul:
I'm getting total phone freeze sod's on the latest build when trying to wake the phone after it's been idle for some period of time. All i can do is long press the power key until it comes back to life to reboot.

I'm on andyx v11 lp8 rom (sammy)

I don't think it's rom related as i don't get this on neak.

I'm using the "battery" extweak profile with no undervolting at all, on default governor/scheduler
[Galaxy S II Original Android Development] gokhanmoral:
can you send me /proc/last_kmsg file?
[Galaxy S II Original Android Development] diddsen:
jittering on charger still exists :-(

iam on wanamlite newest clean install.
[Galaxy S II Original Android Development] tolis626:
Would a last_kmsg from a kernel panic help you identify possible problems?Because lately I get a lot of kernel panics.Yes,Sammy had to **** this up too with ICS. :mad:
[Galaxy S II Original Android Development] Lost.soul:
Can't get BLN to work on AOKP

Hello,

I can't seem to get BLN to work on AOKP Roms .. am kind of stumped.

I downloaded the BLN Control App (Free), activated BLN, it activated fine, from there made sure of the below from an ADB shell:

/sys/devices/virtual/misc/notification # pwd
/sys/class/misc/notification
/sys/devices/virtual/misc/notification # cat notification_enabled
1
/sys/devices/virtual/misc/notification #

However, when I try (Through the control app) or having a friend send me a notification nothing happens.

This is not noticeable on Sammy based ROMs though.

I can attach a logcat if anyone things it is worth a look, however I skimmed through it and found nothing (While replicating the problem).

Does anyone have any idea why this is happening? Or maybe advise on how to go about troubleshooting this?

Thanks!

****EDIT****

After flashing siyah 3.2b4 bln started working again! :D
[Galaxy S II Original Android Development] Crescendo Xenomorph:
Wow! Cool! I can't wait to use that feature!

Is it working like in Nokia N8? Showing that our device is alive and standby/deep sleep?

Any plan about bringing back BLNWW?

Thanks big thanks for you.... :cool:

---Sent from my Samsung Galaxy S2 via [ALTIMIT] Network