yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] hwwr:
Hi guys, the brightness settings by jkaymod is not working. I am on brightess setting but doesn't seem to be brighter.
[Galaxy S II Original Android Development] pikachu01:
Have you turned on autobrightness?
[Galaxy S II Original Android Development] UpInTheAir:
Reboot, and new settings will stick ;)
[Galaxy S II Original Android Development] :
Thanks for the kernel finally managing to get results like this again. Using latest version no scripts.
[Galaxy S II Original Android Development] d8389:
Kernel panic after several connecting/disconnecting USB mouse.
[Galaxy S II Original Android Development] KSTu:
if this kernel will suport db louder and tegrak overclock applications,will be the best!
[Galaxy S II Original Android Development] CamoGeko:
It already supports supercurio's louder app and xan's voltage control extensively. Why would you want support for tegrak?

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Death Star.
[Galaxy S II Original Android Development] KSTu:
no,does not support supercurio DB Louder application(see pic attached)! I like Tegrak more than other overclock applications :)
[Galaxy S II Original Android Development] :
It does support it as i am just using it now. Try reflashing the kernel
[Galaxy S II Original Android Development] KSTu:
both work after reflash! thank you!
[Galaxy S II Original Android Development] :
you more than welcome my friend

and let us end this matter here...few people have not said this test that he is doing is pointless...For me personally i do find it pointless as for me the way i test my battery and kernel is by how i use my phone daily and not putting the phone through stretch tests or whatever tests people do to get the scores that they do....i do it through daily usage and how i use my phone daily..that is how i can verify if i have a good battery or not..By watching a film or youtube videos, making a few calls playing a game while i am on the tube things like that...But for other people what It_ler and AMD have started doing it probably is useful...But again there is a place for that to happen...Open a thread post your results there and the attitude that people might not find it interested and people will not go in the thread to check is absolute rubbish..People will go and show interest if you label your thread title and signature correctly...If there is one thing i learned being on the forums is that people care about battery life and they will do anything to make theirs last longer so any tests or any results that people post they will try and copy or tweak around due to what they find out..

Anyway enough of me going on and on just to recap my point opening a thread and posting these results will probably be more beneficial for everyone cause that way it will not get lost in the kernel threads as they kinda move fast and grow fast the threads and will probably end up getting lost..Were in their own specific threads the results will always be in the first pages and people will have more time to read and digest them
[Galaxy S II Original Android Development] stylez:
Exactly and now can we get back to Siyah issues/advances/settings rather than going over things, it's pretty simple if doing benchmarks or tests open up a thread of own.

No one is discrediting what testers benchmarks are it's just that it's not needed to take up a thread, same as themers they open own thread and don't spam ROM threads.

Pretty simple.

Nuff said now lets get on with testing Siyah...........
[Galaxy S II Original Android Development] omniwolf:
i'm getting some SOD's, fortunately most of the time i can bring it back by pressing the power and home button a few times.

would a kmsg log help debug it?

i'm running 200 - 1200, no UC, and i'm running the latest thunderbolt scripts. should i try deleting them first?
[Galaxy S II Original Android Development] CamoGeko:
Try running a kernel cleaning script and reflashing kernel. Or just deleting the scripts and rebooting. See if that helps. :)
[Galaxy S II Original Android Development] droidphile:
it's probably not an SOD if you can bring phone back to life by tap-pressing home/power buttons. Nevertheless, since you're using Thunderbolt!, issue might be deep sleep entering frequency of 800 mhz at 266 mhz bus speed which your device can not handle.

Try setting deep sleep frequency to 1000mhz @ 400 bus freq.

Find S98bolt_siyah in /etc/init.d and edit these two lines (use script manager or any safe editor) which may look like:

echo 4 > /sys/devices/system/cpu/cpu0/cpufreq/deepsleep_cpulevel;
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/deepsleep_buslevel;

TO

echo 3 > /sys/devices/system/cpu/cpu0/cpufreq/deepsleep_cpulevel;
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/deepsleep_buslevel;
[Galaxy S II Original Android Development] pikachu01:
The latest ThunderBolt! no longer tweaks this as some device can't have aggressive (or semi aggressive deep sleep levels). Have you updated to the latest?
[Galaxy S II Original Android Development] droidphile:
Me? The other user has SOD. :)

He didn't mention which version of thunderbolt! he's using. Many devices are stable at deep sleep freq of 800, but it require bus freq of 400. 266 is sometimes not enough. (example: mine).

I guess SODs can be solved @400mhz bus even if cpu freq is 800.
[Galaxy S II Original Android Development] N6666661:
There is something I don't anderstand with deep sleep frequencies :

Why are the default values that high? : 1000 and 400Mhz?

I thought that deepsleep was a state below the lowest CPU step:o

Can someone explain me a litle more?
[Galaxy S II Original Android Development] stephen2529:
HI guys

Ive just started using better battery stats to see if I can improve my battery.

Flicking through the pages I can see lots of wake locks but all are very tiny. Like 1 sec ect. Should I still be concerned about them? Secondly the only one that is pretty large (50 % ish) is one called vbus_present. I looked it up and it says its to do with charging and and not to worry about it. The thing is its says its present while the phone is unplugged and not charging. Again is this something I should look into more?
[Galaxy S II Original Android Development] Simba501:
Only if those wakelocks are causing svnet dormancy wakelocks (which are held when data transfers happen when the screen is off). If svnet dormancy looks fine (mine is typically ~5%), then you should only look into partial wakelocks that are longer than a few minutes. As to the charging wakelock, you can confirm that its not an issue by unplugging your device, setting the reference point to "since unplugged", and waiting a few minutes. You shouldn't see it there anymore.
[Galaxy S II Original Android Development] droidphile:
1000 mhz or 800 mhz is NOT the frequency at which CPU operates during deep sleep. It is the frequency at which CPU need to be statically set just before entering deep sleep.

During deep sleep, CPU is almost completely turned off, except for very few sub-components in Soc like cell radio.

1 second wakelocks can be safely neglected.

Yes, vbus_present is the wakelock held during charging. Present is the suffix name for the wakelock. It doesn't mean device is detecting a charger even when it wasn't connected
[Galaxy S II Original Android Development] stephen2529:
Ok thanks for the reply. I thought it may be the case. I only wanted to check because its set to "since unplugged" and the vbus_present is still there. Made me think that it might be running even when unplugged for some reason?

The svnet is 2m 43 sec and 0.3%.

Apart from that there is a whole list of other ones but they barley leave a dot of red on the bar. Highest one was 2-3 minutes i think.

Dose this sound like what would be expected?

With a few texts, emails and a little internet Ive dropped about 12% battery in about 7 hours.

Thanks again
[Galaxy S II Original Android Development] tomeks:
just one observation

if in ssid of wifi network is space in the name such a network could not be found and setup in wifi settings

do not know if it is kernel related, have no time to check

(update)

stock kl1 kernel can not detect wifi network with spaces in the name as well
[Galaxy S II Original Android Development] mundixx:
my apologies if this has been asked before, but how do you change the frequency rating for deep sleep?
[Galaxy S II Original Android Development] Delacor:
working great! ;)

Send from my SII ;)
[Galaxy S II Original Android Development] tonysac:
Don't..I did that...no problem there...

Sent from Galaxy!
[Galaxy S II Original Android Development] :
You know, stock ki3 is really good kernel and so is 1.7.7. No offense, but to properly test battery life you should do battery calibration and few charhing cycles. So flash 1.7.7 or stock or anything and keep it for a weeek or two and than you'll see how's battery life.

I don't care at this point, I flash every beta and can't wait for bfs version which will be unstable enough to satisfy me. Charger is always around and if there is problem simple reboot fix it.

So really, if you need your phone to be reliable and has nice battery life use stock ki3 kernel or stable version of any other kernel 1.7.7 of Siyah, ninphe 2.0.5, hardcore t40, raven 1.1b, all good kernels, just find the one that suits you most and keep it for some time.

Sorry for long post.
[Galaxy S II Original Android Development] :
Didn't happen yet, you guys use setcpu? I'm not so that's why I'm asking.
[Galaxy S II Original Android Development] galanakop:
I might have to zip the Last BETA;;; Thank
[Galaxy S II Original Android Development] tonysac:
Yes I'm using setcpu..

Sent from Galaxy!
[Galaxy S II Original Android Development] :
Ok, I'll install it to see if it happens, I am using no frills currently (no UV, no profiles).
[Galaxy S II Original Android Development] tonysac:
Lol I just instal nofrills and uninstall setcpu..no problem with nofrills!

Sent from Galaxy!
[Galaxy S II Original Android Development] :
Haha, well I still try to see benefits of undervokting and profiles, we all change kernels and roms too fast to be able to find our perfect setup. I can run smartass 100-800 with no lag in most apps, wonder if it saves more battery than UV or profiles.

Thinking of trying ondemandx 500-800 to see results. Just trying to figure out if screen off will go down to 100, not sure.
[Galaxy S II Original Android Development] tonysac:
Yes that's true..we change kernels too often..I don't use any other governor except ondemand, because any other gives me lag and I hate it ..I think that your settings must be better than any uv anyway

Sent from Galaxy!
[Galaxy S II Original Android Development] Promsd:
Set AC and MISC charging current to 1000mA - CWM flashable - Dont work :( There are people who work? I just 650mA
[Galaxy S II Original Android Development] theory_87:
Guess it time for u to wipe ur rom...

Send from my Samsung Galaxy S II
[Galaxy S II Original Android Development] theory_87:
How do you check?

Send from my Samsung Galaxy S II
[Galaxy S II Original Android Development] idealforyou:
The same here. 1000mA charging don´t work.

I have a question:

Can this Kernel mount microSD formated in NTFS?

My SGS2 don´t do it with this Kernel. The Android System say the card is empty and will format to Fat32.
[Galaxy S II Original Android Development] lupu87:
Automatic battery calibration

For automatic battery calibration must I connect to a charger when it is discharged, or indifferent? Thanks.
[Galaxy S II Original Android Development] iamsmallpang:
let me try v1.7.8 beta4

You GREAT!
[Galaxy S II Original Android Development] cbeckstein:
and must the mobile be switched on during charging for the autocalibration to work?
[Galaxy S II Original Android Development] gokhanmoral:
be a little patient :)

I removed it and will upload it again in 5 mins.

just fixed a little problem with root.

don't flash it yet
[Galaxy S II Original Android Development] gokhanmoral:
ok I have uploaded beta4.

in previous beta versions there was a problem with init.d scripts. they were not running as root.

therefore some custom rom tweaks were not working.

also underclocking/undervolting scripts were not working.

I have increased internal voltage level of 1600mhhz.

1600mhz should be more stable than before.

I reverted some patches that I applied because there were causing some sdcard issues.

therefore I set the minor version back to 7. I thought that would be more appropriate because we are now far from .14.

I am still thinking about reverting the wifi drivers.

is there anyone who still has problems with wifi?

I changed the rooting script once again.

it overwrites su just like cfroot kernel...

let's hope this will fix some application freezes etc.

su is now copied to xbin and /system/bin/su is removed.

I also remove superuser.apk files from system and data and copy the new one to system/app
[Galaxy S II Original Android Development] :
Noooooo :(, there were very little issues with .14 and there are really no problems in beta3, please bring back those patches.
[Galaxy S II Original Android Development] N78006:
Sound delicious!~

using Leo 2.7.1 with Ragemod

let me try urs
[Galaxy S II Original Android Development] rauschkugl:
If you're using lulzactive you can use the corresponding app from the market else you have to do it wirh a script.

Sent from my GT-I9100
[Galaxy S II Original Android Development] cmd512:
Siyah v2.6.7 is absolutely flying with the new LA2 GB F/W that was just released. Not sure if it's the kernel, ROM, or a combination thereof, but the device is even more buttery smooth! :)
[Galaxy S II Original Android Development] cooldfuzion:
This new kernel is excelente, my phone is on for more than 27h, 2h display time, i have talked 75 minutes and wifi for 1h and i still have 28% of battery! :)
[Galaxy S II Original Android Development] seaweeduk:
I've had spaces in my access point name ever since I set it up never had problems picking it up on any of my android phones though stock or otherwise. Unless your access point name consists of nothing but space character(s)?

If you're having problems finding a network which was previously working before flashing the kernel I suggest you try forgetting the network in the settings screen before scanning again, has solved issues for me in the past.
[Galaxy S II Original Android Development] kilian7th:
2.6.7 is nearly perfect !!! Great Thanks !

Hello,

thanks foy your job but the 2.6.7 version of your kernel is incredible.

Better than my previous favourites configurations which were siyah 2.6.4 + thunderbolts scripts 2.3.8 or Xcell-69x Kernel.

If it had more agressive settings for screen-off configuration or in sleeping mode it should be just perfect.

I listen a lot of music but it drain as much battery as bafore but for the rest I love your kernel.

I hope you will read my message.

GOOd GOOD job,

Thanks again !
[Galaxy S II Original Android Development] ziroxs:
There is much more space for improvements. 24h online, 2h display time, 30 min telephone. Still 74% left. Ok i UV my phone :rolleyes:
[Galaxy S II Original Android Development] olifee:
Yes, working fine (there are also several reports in this thread that it is working for several users).

Did you try it and have any problems? If so, can you give us some details?
[Galaxy S II Original Android Development] olifee:
Can you check the file

/data/wifi/bcm_supp.conf

?

It should contain a line

ssid = "name of network"

You may also post that line, just don't post the complete file here because it also contains your wifi-password ;).

In case the parentheses are missing, that might be a reason for a problem with spaces (and a bug in the ROM, I guess).

Did you type in the network name? If so, can you delete the network configuration so the device 'forgets' it, scan for networks and then connect by selecting it, so it grabs the SSID itself?

This is by far the best method, it also does not open the "scan_ssid=1"-security problem, which is active for all hidden SSID networks. So in case your SSID is hidden, please make it visible, it does NOT give you further security but rather make life easier for hackers!

EDIT: If you really mean it is not even found by scanning, you can try "iwlist scan" in terminal to do a manual scan (hope that works on Android, did not try yet). => Doesn't work :(. Now I do not know of a way to force manual wifi-scanning in terminal...

EDIT 2: Corrected filename.
[Galaxy S II Original Android Development] Piretia:
Hello

Can you tell me what is the setting for your UV

thank you
[Galaxy S II Original Android Development] xsycox:
I am not French, too. :)
[Galaxy S II Original Android Development] c0x91:
Thanks to the creator.
[Galaxy S II Original Android Development] ziroxs:
You got both a PM.
[Galaxy S II Original Android Development] cooldfuzion:
O governador que estou a usar é o ondemand (200-1000) e o i/o sio e tenho também o thunderbolts scripts instalados, tudo isto na Miui como é claro :) e super fluido!
[Galaxy S II Original Android Development] Namoi:
Hmm, so far so good.

Maybe it's time now for a specific Siyah app for easy customizing ;-)

Keep up the good work and thanks a lot for this amazing Kernel !
[Galaxy S II Original Android Development] lufc:
Cut this Crap out NOW if you do not have anything to say on the Development of this thread then do not Post

If we have to delete any more Posts of Crap then the persons in Question will find then selves on a Holiday from XDA

Be Warned
[Galaxy S II Original Android Development] ozzyita:
What govener do you advise me?

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] ziroxs:
For me i have good results regarding smoothness with sio and ondemand 200-1200 MHz.
[Galaxy S II Original Android Development] ozzyita:
Battery ok?

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] stevehkim:
battery is spectacular!!
[Galaxy S II Original Android Development] ziroxs:
More than that. Its awesome. With UV i get a stable system and very good battery life like Phenomenal. With Siyah you are able to do anything you want. 2.6.7 is for me perfect.
[Galaxy S II Original Android Development] ozzyita:
Ondemand is best for battery? Thanks guys

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] CamoGeko:
In this version, yes. Followed closely by Conservative.

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Death Star.
[Galaxy S II Original Android Development] cmd512:
I've been tweaking Lulzactive, Conservative, and Ondemand for quite some time. (In fact, I still have 3 sections in my init.d script, just with the ones I'm not currently using commented out with #'s.) While each of them has their benefits, I ultimately found Ondemand had the best combination of all of the following when setup properly:

1) Fast ramp up to max freq to get the performance I need when I need it.

2) Adjustable staggered ramp down so that you minimize lags and still keep frequencies low when phone isn't being pushed, which helps battery.

3) Smooth scaling which sets an intermediate step in case your phone doesn't really need to ramp up to max.

4) None of the other governor's weird behaviors (ie, lulzactive's screen on/incoming phone call lag, etc).
[Galaxy S II Original Android Development] ozzyita:
Thank you all guys

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] EnemyOfGlaDOS:
whats up! hey got a question. Running a i9100 ROM on my i777. I know there is a port for this kernel for the i777. My question is: Since I'm running a i9100 ROM (Illusion-xT) and I want to flash siyah, do I flash the zip for i9100 or i777? :confused:
[Galaxy S II Original Android Development] CamoGeko:
I777 mate because that is your device model. :)

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Death Star.
[Galaxy S II Original Android Development] RotesMeerJogger:
when i set ondemand governor then i can't use lulzactive app. is this right? is there another app to tweak with a gui?

cmd512, what are your tweaks for ondemand governor? can you post it please? thanks!
[Galaxy S II Original Android Development] stevehkim:
always flash att i777 kernel even if you hellraised. you'll be good to go. have fun!
[Galaxy S II Original Android Development] EnemyOfGlaDOS:
cool.. just double checking.

perfect, thank you! :)
[Galaxy S II Original Android Development] cmd512:
Sure:

#L1 = 1400MHz = Max freq = smooth target

echo "1" > /sys/devices/system/cpu/cpu0/cpufreq/smooth_target

#1+3 (smooth offset) = L4 = 800MHz = target smooth scaling midstep

echo "3" > /sys/devices/system/cpu/cpu0/cpufreq/smooth_offset

#6 (lowest frequency = L6 = 200MHz) -2 = L4 = 800MHz = target smooth scaling midstep

echo "2" > /sys/devices/system/cpu/cpu0/cpufreq/smooth_step

#Result = Phone will jump to 800MHz before scaling up to higher frequencies

#ondemand tweaks

#CPU load has to hit 75% before scaling up

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

#Samples CPU load every 25000 microseconds

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

#Waits 25000 x 40 = 1000000 microseconds = 1 second before throttling down from max freq

echo "40" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor

#CPU load has to decrease to 75-35 = 40% to throttle down frequency

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

Results are perfect for me and my usage:

1) Ranges from 200-1400MHz

2) When stepping up from min freq of 200MHz, has to go to 800MHz first. This means the phone will not go above 800MHz and mostly sit at 200MHz with screen on when not doing anything intensive.

3) If doing anything intensive, it will hold at 1400MHz for a full second before really throttling down... this prevents any stuttering, even with a very high sampling rate of 25000 microseconds.

Hope this helps!
[Galaxy S II Original Android Development] omniwolf:
yes i am running the latest thunderbolt and screenstate scaling addons. i realised i hadn't setup the remount scripts for this version, but i can't imagine that would cause partial SODs. if it happens again i'll try removing the thunderbolt and screenstate scaling scripts.
[Galaxy S II Original Android Development] ramsheart:
hmm never had SOD here

using :

- Siyah 2.6.7 (wifi fix version)

- Thunderbolt 2.3.11 + screenstate 1.4.12 addon + Remount Script

- Tested on DXKL3 and XWKL1 rom.

- SIO + OnDemand 200-1000

- Undervolting :

100 - 900

200 - 900

500 - 950

800 - 1000

1000 - 1100

1200 - 1200

and the rest is default using voltage control.

deep sleep run well. phone can wake up normally
[Galaxy S II Original Android Development] xsycox:
thanks for that info. how can I create such an init.d file? standard editor? any special name for the file?
[Galaxy S II Original Android Development] cmd512:
Frankly, I never quite understood the naming nomenclature, and given I've always only used 1 file, I never cared to.

I just created a boot file with Voltage Control and went into /system/etc/init.d to edit it directly. It's just a text file, so be careful when you make edits. Otherwise, use a script editing tool as it's bit "safer."

Good luck!
[Galaxy S II Original Android Development] pikachu01:
Nope. It would not. Best to check your UV/OC to see if any of them are too aggressive for your phone.
[Galaxy S II Original Android Development] omniwolf:
i have no UC or OV, unless the thunderbolt scripts UV..