yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Steven6489:
Ok.. I already uninstall Juice Defender and GoLocker(replace by Widgetlocker)..I will see how much it drain..

Besides that, I search in this thread and google..can't find anything regarding this alarm wake lock..:confused:
[Galaxy S II Original Android Development] MistahBungle:
What count are you getting in BBS for alarm manager wakelock ? When I was using BBS a couple mths ago to get rid of my wakelocks, I found disabling notifications in things like calendar/other apps that issue notifications tended to get the number of wakelocks caused by alarm manager right down.
[Galaxy S II Original Android Development] mariosraptor:
@Gokhan.

Sorry if this has been issued. Can you add the new cwm touch recovery to your next release? Thank you and again sorry if yoh have answered this!
[Galaxy S II Original Android Development] shawnaye:
dont think it's fully compatible for the SGSII AS OF YET.
[Galaxy S II Original Android Development] pikachu01:
Yup, that is correct :)

Hence, to get ICS for SGSII working with a custom kernel, source from Samsung is definitely needed (which we don't have right now). Until that arrives, no Siyah for ICS.
[Galaxy S II Original Android Development] Steven6489:
Count : 5106 :mad:
[Galaxy S II Original Android Development] MistahBungle:
Yep that's a lot. Go thru your apps & try disabling notification on as many as you possibly can & see if that improves things. Failing that, try the BetterBatteryStats thread on here, those guys know their stuff really well & they should be able to help out.
[Galaxy S II Original Android Development] liamR:
According to the developer website it is (scroll down) -

http://www.clockworkmod.com/rommanager

5.8.1.5v for the SGS2 and 5.8.1.3v for the T-Mobile SGS2.
[Galaxy S II Original Android Development] PedroMRP:
gokhanmoral the new clockwork touch recovery for galaxy s2 was released it would be great if were included in the next kernel version.

recovery-clockwork-touch-5.8.1.5-galaxys2.zip

recovery-clockwork-touch-5.8.1.5-galaxys2att.zip

recovery-clockwork-touch-5.8.1.3-hercules.zip
[Galaxy S II Original Android Development] lutanica:
Hi mates,

Correct me if I'm wrong here. Siyah's kernels don't support the new CheckROM V5. Is it right?

http://xdaforums.com/showpost.php?p=21648018&postcount=11777

If that's the case, Gokhan mate, would you include the root for that ROM in your kernel?
[Galaxy S II Original Android Development] ramsheart:
and

Checkrom V5 is :

so ???

what's the problem ?

never had any problem with stock xila2 or even the very new xwla4 combine with latest siyah.
[Galaxy S II Original Android Development] Vaedryn:
SiyahKernel v2.6.13

Posted on February 4, 2012

Changelog:

fixed BTHID issues (thanks to Entropy512)

some wifi driver changes to prevent wlan_rx wakelocks preventing the device to sleep

new cpuidle driver from galaxytab (thanks to Entropy512)

reverted top-off current back to default

generic OTA updater app which is simply a modified version of 89luca89′s version of gingerbread updater (which is based on cm-updater app). the only notable change in the original source code is that the default system updates url is read from /system/update.url file (can be changed from the preferences menu) and kernel updates’ url is read from /res/update.url (static, not configurable). no kernel or rom specific code. any kernel or rom developer can use it as is. they just need to prepare a json file which describes the available files/updates. kernel updates will be listed along with system updates if the installed kernel supports it.

another generic configuration interface (thanks to xan and andreilux for their support and advices). although it is a work in progress, I hope I’ll finish all necessary scripts this weekend. You’ll need voltage control app from the market to be able to use that interface.

not released yet.

Gokhan , you have forget 2.6.12 ? :D
[Galaxy S II Original Android Development] lutanica:
Siyah's 2.6.11 doesn't root the CheckROM v5 (no superuser and the CWM manager doesn't work). The only way to root it, was to flash the supporting cf-kernel first and then reflash Siyah's.

Not important though. I went back to CM7. I don't really fathom why people prefer Samsung-based ROMs. They are so primitive in my opinion. CM7 lacks some function yes, but it's far more intuitive.
[Galaxy S II Original Android Development] It_ler:
IMO it doesn't matter that there is no .12.

I am looking forward to v2.6.13.

Thanks gokhanmoral in advance for the new kernel version with all that improvements.
[Galaxy S II Original Android Development] TecQuality:
+1

10 chars
[Galaxy S II Original Android Development] keiemz:
use "

echo "1" (o)

echo 1 (x)
[Galaxy S II Original Android Development] Lownita:
"some wifi driver changes to prevent wlan_rx wakelocks preventing the device to sleep" that gives me hope, I have this wakelog with samy rom. On cm7 it was gone :)
[Galaxy S II Original Android Development] gokhanmoral:
I tried to integrate cwm recovery 5.8 but I failed.

I have bootloops once I replace the recovery binary.

I am not sure why. maybe it is my kernel's fault or CWM recovery's.

for 2.6.13, I will keep the old touchless recovery.

and I know. I skipped 2.6.12. 13 is my lucky number :)
[Galaxy S II Original Android Development] PedroMRP:
sad news... :\

I was looking forward to test touch recovery :(
[Galaxy S II Original Android Development] MistahBungle:
If you do get around to implementing touch-based recovery, make the layout bigger. Too easy to make a (possibly "fatal") mistake with touch-based recovery with the current layout/fairly small text.
[Galaxy S II Original Android Development] incubus_fr:
How will work the OTA updater?
[Galaxy S II Original Android Development] PedroMRP:
According to this thread netchip was able to get it to work on custom kernels.

[KERNEL][TOUCH CWM][AOSP][TESTED by Paradoxxx] CWM touch recovery
[Galaxy S II Original Android Development] msgfromside3:
Same here. I might go unnamed for i777.
[Galaxy S II Original Android Development] Honusnap:
Agreed, too small to be usefull in touch mode, we not all have small fingers .. :p

---------- Post added at 07:14 PM ---------- Previous post was at 06:53 PM ----------

1 - Do someone know (not just by guessing) what is the most conservative one :

Dual core at 500 or single core at 1000 ?

Than speaking about benchmark, 500(x2) is certainly less powerfull than 1x1000 but by how much ? 500(x2) = 0.9x1000(x1) ? Did someone already do the test ? I know i can do it, but which benchmark is the most accurate for this kind of comparison.

2 - I suppose that when needed the processor go from single core to multi core (when possible) THAN an increase in frequency occured if it's not enought.

I suppose that cause the sample time is shorter to trigger the dual core mode than it is for the increase in frequency...

So, if freq_cpu1on = 500Mhz (supposing governor go up step by step)

200 Mhz single core => 500 Mhz single core => 500 Mhz Dual core => 800 Dual core => 1000 Dual core => 1200 Dual core

am i right ? Than going down (supposing governor go down step by step)

1200 Dual core => 1200 single core => 1000 single .. etc
[Galaxy S II Original Android Development] gGabi:
everytime i want to flash something from OTA tool using hyperdroid rom, it boots into 3e recovery and the mod is not flashed. :(
[Galaxy S II Original Android Development] Entropy512:
WRONG. For ICS, all you need is NOT just a 3.0 kernel - you need a 3.0 kernel which supports EVERY one of Samsung's device drivers, AND has the exact driver interfaces Samsung's closed-source userspace HALs like libaudio expect.

In the case of the Nexus S, being a Nexus device, its kernel was maintained in a public repo that tracked the mainline Linux kernel, AND much of its hardware support was pushed to the mainline Linux tree.

The Galaxy S was able to leverage that, as it has very similar hardware to the Nexus S.

In addition, for the Nexus S, since it was a Nexus, all of the userspace HAL libraries like libaudio were open source - so if the kernel/HAL interfaces changed, it was easy to see what changed.

With the I9100 and I777 - We don't have a Nexus device to pull/track changes from. The state of Exynos support in the mainline Linux kernel tree is utter and complete crap - the cpuidle driver only supports the basic IDLE state for example. In addition, it's a known fact that Samsung changed the kernel/HAL interfaces with ICS and we have no documentation of these changes.

I believe CheckROM has been including CF-Root kernels lately due to the BTHID issue - Some aspects of newer builds were broken with any kernel based off of released I9100 source trees. (Uss_Defiant - this is a perfect example of a situation where Samsung changed an interface without any documentation of that change.)

GM removed the autoroot functions ages ago I believe - flash ChainsDD's CWM packages from within CWM to root your device instead.

And to change topic:

GM, you may want to warn people that the cpuidle patch broke video playback for a very small number of users on I777. Disabling AFTR seems to fix it. I'm trying to figure out a good solution to this that fixes those people without crippling cpuidle too much.
[Galaxy S II Original Android Development] adivorandroid:
This kernel work with android 4.0.3 ???
[Galaxy S II Original Android Development] PedroMRP:
This has been answered many times...but the answer is NO!
[Galaxy S II Original Android Development] stevehkim:
wow it never ceases to amaze me.
[Galaxy S II Original Android Development] stevehkim:
sorry man. i usually dont care for what people post but after reading and seeing it over and over and over again.... well you get the point.
[Galaxy S II Original Android Development] Nescho:
Oh my god new update is almost there. Cant wait any longer! Im sure its gonna be great

But why is there no .12?

SGS2 | Tapatalk
[Galaxy S II Original Android Development] remorema:
hell yeah. now with bthid working...

you guys rule! good job

Tapatalked from "The ICS Killer"
[Galaxy S II Original Android Development] bclark:
http://xdaforums.com/showthread.php?p=22170745

Really? One page back...
[Galaxy S II Original Android Development] Entropy512:
Unnamed 1.3.2 is great. 2.x suffers from UCKK6 suckage.
[Galaxy S II Original Android Development] ZACQ8:
Hi,

Siyah v2.6.11 is running in my SGS2,

could somebody please explain to me what these are :

1) automatic battery calibration.

2) Automatic backup of efs partition.

I have already calibrated my battery using app 'battery calibrator' is there any harm doing so whereas it is not required for this latest siyah kernel.

When is the backed up efs partition in tar file saved to SDcard usfull for me.

thanks in advance
[Galaxy S II Original Android Development] Entropy512:
Automatic battery calibration was removed because it did nothing.

Same for whatever battery calibrator app you ran. It did NOTHING.

If you think your fuel gauge is acting up - here's how to fix it: WAIT. It will converge towards truth after a few hours. It usually only gets thrown off at low battery, so it's probably time to charge it too.
[Galaxy S II Original Android Development] Must2r4h:
Efs backup is useful when you suddenly lost your imei number. If that happen you will lost your phone signal.

If you're into flashing you should have your efs backup.
[Galaxy S II Original Android Development] ZACQ8:
Thanks,

Please answer my these doubts too....

1) Is the backed up efs file "efs_XXX.tar" a flashable file through ODIN?

2) I have ROM manager premium, is this compatible with my current recovery (redpill) of Siyah v2.6.11?

thanks a lot
[Galaxy S II Original Android Development] MistahBungle:
1) No.

2) Rom Manager & CWRecovery do not play nicely with each other on SGS2, I.E Rom Manager tends to break CWRecovery. I would be surprised if it doesn't break RedPill as well. Use one or the other.
[Galaxy S II Original Android Development] sahibunlimited:
For me rom manager always enter stock recovery while flashing a zip
[Galaxy S II Original Android Development] tolis626:
Well,as much as I like RedPill recovery,I wanted to test the new LPB ICS leak(Kinda sucked to be honest,CM9 looks way more complete if you count out the non-working camera) and,as was normal,I made a nandroid backup and wiped.So,when I wiped,the damn thing also wiped my /sdcard/Android folder and I lost all my f*cking save games for MC3,Hot Pursuit and some others.Of course these weren't restored by the nandroid.Still,I wonder why game makers choose to store the game progress there instead of the game's data,but still,I don't think that that folder should be wiped.

I don't know if anyone else gives a poo,but it was annoying.I'll manually copy them over next time.
[Galaxy S II Original Android Development] antt00:
You should use titanium backup to backup apps/game data. It never fails.
[Galaxy S II Original Android Development] tolis626:
Ermm,I do have a backup with titanium,but these games save their data elsewhere,so Titanium did zip and it's not is fault.It has an option to backup /sdcard/Android folder,but my backup with Titanium is already about 1.8 gb big,and it'd be far too big with the other stuff.
[Galaxy S II Original Android Development] thez3ro:
im on vertrema 4.7 and siyah kernel 2.6.11. tried and my phone does not support ntfs usb drives,fat is ok,but ntfs doesn work. in file manager there are no files in usbstorage folder.

abyone had simmilar problem? found a solution maybe?

sry if this question has been asked before...
[Galaxy S II Original Android Development] gokhanmoral:
just a little info: the bandwidth usage of my blog for the last month is 633784MB :) (thanks to godaddy for their real-unlimited hosting).

I am still working on the universal config interface.

If I cannot manage to finalize it today I will release 2.6.12 without the additional apps (only kernel changes) and finish them in the next week. I thought I might not have time to finish them. that is why I skipped .12 because some modifications are important (such as bthid).
[Galaxy S II Original Android Development] MistahBungle:
>633GB in a month ?! *faints* :D

Don't sweat releasing .12 or .13 GM. You're a busy man, you spoil us as it is & we can wait ;-)
[Galaxy S II Original Android Development] veyka:
You should see the kinda data usage when pushing 350meg roms! Its crazy, without unlimited bandwidth hosts no one could afford the kinda bandwidth hosting stuff generates. (100's of $'s with limited bandwith hosts).

@GM If you are in need of a mirror sometime, send us a pm :)
[Galaxy S II Original Android Development] Lownita:
Kim Schmitz might have a solution :D

Today I experienced two hot reboots with 2.6.11 at low battery (around 14%). Don't know if it was kernel related - using it with latest hyperdroid.
[Galaxy S II Original Android Development] tolis626:
If by "Hot reboot" you mean that it rebooted to the boot animation and not the GSII logo,then it's most probably rom related. :)
[Galaxy S II Original Android Development] Lownita:
Yes that's what I mean :)
[Galaxy S II Original Android Development] XDA mark:
I thought Id report that for me 2.6.9 is giving better battery life then 2.6.11. All in all Im very happy with .9 :D

Can't wait for the newest version to be done, it's looking great.
[Galaxy S II Original Android Development] marioh:
Same here!

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] gokhanmoral:
please try 2.6.12

it will be uploaded to the first post in 10 mins.
[Galaxy S II Original Android Development] tolis626:
Gokhan,I can't say whether 2.6.12 is better than 2.6.11 in other aspects,but BTHID devices work flawlessly.I just tried some bluetooth mice and,well,I was surprised at how nice Android can act as a desktop when hooked to a TV. ;)
[Galaxy S II Original Android Development] sadonlyone:
(wipe dalvik cache, flash v 2.6.12, wipe dalvik cache again, reboot. phone boot up than gets a reboot assert on start up. I guess is not an issue 'cause I'm not coming after a fresh rom. will check again and I'll come back)

on v2.6.12 :

finally I can get whatsapp messages working normal (no delay on receiving or sending).
[Galaxy S II Original Android Development] Promsd:
waiting for your kernel for 4.0 :) the best.
[Galaxy S II Original Android Development] Vaedryn:
You must wait a long time, without kernel source no way :o

Thank you for bringing up next release gokhan:thumbup:

SGS II Cyanogen Mod Tapatalk
[Galaxy S II Original Android Development] cmd512:
Excellent, will be trying this over LA4! :)
[Galaxy S II Original Android Development] rebel.charles:
Is this okay? Im on siyah 2.6.9
[Galaxy S II Original Android Development] XDA mark:
Cant really see your pics because they are to small.

I got 11 and a half hours now of standby, 4 hours and 10 min of screen time, wifi all the time, 44% left. Guess today is going to be another 6-7 hours screen time run lol.
[Galaxy S II Original Android Development] Vaedryn:
I think this is the trick :D
[Galaxy S II Original Android Development] keiemz:
What did you do when screen on? And I want to know your setting like rom or other things.

Sorry for my English
[Galaxy S II Original Android Development] rebel.charles:
Nice mate. That is really good. I guess it' s time for me to change the kernel. Will try another version of siyah. I uploaded the pics through phone, maybe that is the reason they are too small?

Well actually it says 12h 35m on battery..wifi on 90% of the time. Screen on 4hours. Wakelocks were download manager and alarm :(
[Galaxy S II Original Android Development] XDA mark:
See my sig for all that info. When the screen was on I did:

-Whatsapp

-Internet browsing

-Facebook

I could upload pictures but I just hope people understand I have no reason to lie. Im now posting for my laptop, phone next to it and again it says: 11h44m49s, display 4h11m51s, 44% left.

Have to say this is not something I reach everyday. I think it's because I have been home all day and only used wifi today instead of also 3g/H+.
[Galaxy S II Original Android Development] gokhanmoral:
well.. there are not big changes except for the changes I got from Entropy512's repository which are bthid and cpuidle from the upstream.

today, I tried to get bln working without activating any wakelocks.

in theory, it should work if we do not shutdown touchleds and regulator etc (requires some gpio changes) while going into sleep. but I could not manage to get it working. I will try to get it working because I sometimes need bln but I hate the drain issue.

anyway.. this release has some merges with samsung's latest sources.

I also removed almost all wifi driver changes and used samsung's latest wifi driver.

it seems that deep sleep issues and wifi wakelocks are gone this time.

we'll see.
[Galaxy S II Original Android Development] keiemz:
Thank you I trust you.

1 more question.

which one is your battery bundle or expended during that time?

UV setting is extreme or stable?
[Galaxy S II Original Android Development] XDA mark:
I am not sure what you mean, but I think you want to know which battery I am using right now (with these results I am getting right now). It's the 2000mAh official Samsung extended battery.

I undervolt very stable. I used Geko's settings (see the general thread, his 'MagicConfig 3.1' should be there) but added +50mV to eacht step he mentioned (both for CPU as for GPU). My device can get a little unstable using his configuration, Im a rare case so I would just try Geko's settings. Further more I use BFQ + Ondemand, 200-1200 MHz.

So in short: Expanded battery, Stable UV setting (Geko's Magic Cfg 3.1)
[Galaxy S II Original Android Development] keiemz:
ok thank you. Sorry for my English. Have a nice day.
[Galaxy S II Original Android Development] tolis626:
I can't commend on deep sleep as of yet as I've been playing with the phone for the past few hours. :p

I'll report tomorrow.I'll leave the wifi turned on overnight and see how it goes.As for BLN,if you make it you're THE man.Not that you haven't proven yourself already,but that'd be something to boast about. ;)
[Galaxy S II Original Android Development] kilian7th:
I don't find the information on the threads. Is siyah kernels compatible with Galaxy Nexus ?

Thanks ...
[Galaxy S II Original Android Development] PedroMRP:
Only one question... are you in the galaxy nexus thread?
[Galaxy S II Original Android Development] XDA mark:
Think this is only for the Galaxy S II. It never hurts to ask though ;)
[Galaxy S II Original Android Development] veyka:
Considering its in the I9100 forum, no way, and flashing it would give you a lovely brick, dont flash anything from outside the Galaxy Nexus forum.

Edit 3 times ninja'ed, teaches me for not refreshing the page.
[Galaxy S II Original Android Development] K Rich:
I hope I don't get shot down for this, but if I wanted to use ondemandx as my governor, how would I go about that? I know it says its available as a module, but I'm not sure what that means. If someone could point me in the right direction, I'd appreciate it.
[Galaxy S II Original Android Development] XDA mark:
It seems to me you just need to open the voltage control app and select gouvener and set it to ondemand.

Edit: or SetCPU.
[Galaxy S II Original Android Development] K Rich:
ondemandX, I don't have it as an option.
[Galaxy S II Original Android Development] XDA mark:
There is no more OndemandX, just Ondemand. If that isn't in the list of gouveners, I have no idea how to help you.
[Galaxy S II Original Android Development] kbnguy:
Great kernel

First off, Thanks GM for your devotion and great kernel.

I've been running your kernel since v1.xx and really love the customization and tons of tweaks that we can play with :D

Since v2.66 onward for some reason whenever I use this app, textPlus gold, I can never connect to their voice network. If I switch to NEAK or Tegrak's Lulzkernel or Redpill then the app just connect fine... Point is that I love your kernel so much and don't wanna switch...

Whenever you ( or anyone knowledgeable of logcat) have time pls look at the logcat. TIA
[Galaxy S II Original Android Development] PedroMRP:
Ondemand is a mix of ondemand with the sleep profile of ondemandx so using ondemand you are using ondemandx
[Galaxy S II Original Android Development] thez3ro:
Anyone?
[Galaxy S II Original Android Development] zoule HCo:
Thank for the 2.6.12 version.. flash the new kernel.. hope it better than previous version..
[Galaxy S II Original Android Development] stevehkim:
2.6.12 is awesome. been 5 hours and i still have 96% batt left. wifi on data on. light texting and cpl of phone calls. of course some xda premium as well.
[Galaxy S II Original Android Development] keiemz:
2.6.12 has more battery life than 2.6.11. I just did flash and sleep.

Wifi off

3g on

Background data & sync on

1 missing call

1 whatsapp msg

1 Gmail

Few second screen on

No OC UV, all other is just default.

After 5 hours, my battery is 96%

Sorry for my English
[Galaxy S II Original Android Development] cmd512:
Agree with above posts. 2.6.12 has good idle battery performance, but even more impressive, battery drain during usage seems much improved compared to 2.6.11. Thanks again gokhan!
[Galaxy S II Original Android Development] jdmcivic:
i am now using the o/c daemon script. have u tried clocking it to 1.6?
[Galaxy S II Original Android Development] :
For those with high Android OS usage try uninstalling/freezing VPN services with titanium.

It was running all the time for some reason since I installed ki3 stock it was running all time.

Maybe just a coincide, but worth a try.
[Galaxy S II Original Android Development] kwerdenker:
Hmm... maybe SetCPU re-enables the write permissions on the stub? I have it currently frozen since the scripts do everything I need but I'll enable it and reboot to test this.
[Galaxy S II Original Android Development] ebliss:
I freezed both setcpu, voltage control. And there is only 1 script in init.d (created by voltage control). The funny thing is, when I use terminal emulator to manually run the script, the scaling_max_freq gets changed. So, the script basically works.