yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Crescendo Xenomorph:
idk why ppl always complaint about battery. What do you ppl expect with modern high tech super fast phone with SMALL CUTE BATTERY?

Grow up ppl, don't put your battery problem to Gokhan. Instead why don't you buy BIGGER BATTERY (2000mah is more than enough)?

Quit saying about battery and let Gokhan focus on more feature.

You all blocking Gokhan from putting more feature and make him drain all his mind and brain on small thing (battery) over a long time. You all made him to revert back to older kernel version coz you all complaining and whining about battery too much.

Siyah Kernel is famous for its feature and stability. Don't just focus on small thing and let him put more feature and evolve this kernel to next level.

C'mon, lets see the BIG PLAN (more feature and stability), not only a SMALL PLAN over a long time (battery). Grow up ppl.
[Galaxy S II Original Android Development] Rawi666:
I'm sure with the same apps in background I had 3-4% overnight.

If gokh doesn't release any new kernel this evening :) I'll check battery on stock XWLP7 kernel just to be sure.

Maybe should I try Reset Fuel-Gauge Chip in extweaks?
[Galaxy S II Original Android Development] tuilalnvinh:
I'm on latest CM9, with stock kernel, lost only 2% over night (about 7hours, with wifi off, data packet off, sync off). But when changing to rc5, i lost up to 6%, even though CPU Spy stated that i had 96% deep sleep, so weird :confused:
[Galaxy S II Original Android Development] ep0ch2:
Because the battery life with Siyah kernel used to be much better. With recent builds battery life has now regressed significantly and it affects many users.
[Galaxy S II Original Android Development] pikachu01:
Gokhan, setting up an issues list in Github will be a jiffy. It'll reduce the number of incoherent posts and counter-flaming like the posts above that in reality doesn't contribute much except for fanning the flame.
[Galaxy S II Original Android Development] hshah:
My issue is very similar to that...
[Galaxy S II Original Android Development] feydakin:
Sorry, but what the f***? People complain about the battery because with an older version of this kernel or with another kernel they hadnt this problem and the battery drain was fine. With the new versions they have a higher drain and posting in this thead. This have nothing to do with "Ohh dear Gokhan, pls fix the small Battery in the S2. I want to use my Phone a week without to recharge! Cmon, do it!!!!"

Btw. I have the 2000mah Battery and I think (not sure) it all started with RC2. Atm I can be really lucky if my Battery is about 30% when im coming home from university/work. Thats much worser than with the Samsung ROMs/Kernel I had before.
[Galaxy S II Original Android Development] Rawi666:
Actually it's 17% per 7,5h so it's about 2,26% per hour
[Galaxy S II Original Android Development] Crescendo Xenomorph:
I'm not flaming. I used to use stock kernel ,then Tegrak kernel before moving to Siyah. I know how it used to be.

But, this S2 is really got a small battery and die a lot of faster than S1.

But I know why it's like that, this device got the same 1650mah battery as S1 but with double cappability and processing power. That's why its power-drainer.

But with 10hours of battery life its still reasonable compared to the capability provided.

Sorry if you all feel offended by my post, but I don't meant to offend anybody.

I just want to tell.
[Galaxy S II Original Android Development] paryav:
I notice than have a WI-FI switching problem.

When I first flash kernel. Phone not turning ON wifi on first boot.

It's telling "switching on"... but not switching.

After reboot all switching work's good. But after long period when i not switching WI-FI it's not turning on.

For example after 1 day, 1 nignt problem repeat's.

Interesting, when phone in this situation go to sleep, it's hang.

After reboot all working good for some times.

This problem reprodused in 3.0.1 kernel and 3.1.rc3.

3.1.rc4 i am testing now.

My phone flash Omega 9.0. No init.d folder.
[Galaxy S II Original Android Development] windowsxelvis:
Of course we can't expect too much for this phone. However, we experience a better battery usage before! We are just asking why the battery is comparatively bad.
[Galaxy S II Original Android Development] AvRS:
This was a known bug in older versions and then fixed in the last few so there's no need to report bugs if there's a newer version released. The only useful bug reports are those for the latest version.

On an unrelated note I'm still happily using 3.1b3 and got 14 and a half hours use with 5 hours screen on with 20% left so have not seen the need to update. If you're happy with something stick with it is what I say but if you want to join in with all the people who like flashing the latest do it but always check if the issue has been logged, the changelog for the next version and if there's a newer version already. This will at least stop the repeated reports which aren't needed, make life harder for Gok to follow his own thread and won't halt progress of future versions because he has to spend a day reading all the posts to see what else needs fixing.
[Galaxy S II Original Android Development] chubby65:
If battery drain concerns that much do as I have and buy a spare battery :D
[Galaxy S II Original Android Development] MistahBungle:
I tend to make minimal posts to this thread (as opposed to people who post absolute nonsense here constantly, obviously forgetting this is a dev thread), but that's probably the most ignorant post I've seen in this thread.

In case you've been asleep with your head up your backside for the past few days (being a betting man, I'd say that's odds on), there has clearly been a battery drain issue for many people with the past couple of rc's.

Gokhan has rolled back many of the changes he's made recently in an effort to see if that fixes the battery drain problem. And then I imagine he will start adding the changes back one by one (or a few at a time) so he can nail down exactly what change caused the battery issues.

Short of spending 95% of his time doing testing, the best way for him to do this is to get feedback from us firstly around whether rolling back the changes fixes the battery drain issue, and again whether the problem stays fixed as he 'adds back' the recent changes.
[Galaxy S II Original Android Development] ndnesh:
Hi

I am not taking this offensively! there is no need to ! I can understand that we all want excellent battery life.

For your 1st point- I have stated in a previous post that i did connect my phone to the USB to transfer movies etc. During that time, the phone did get charged. Totally the charge may have been increased by around 10 to 20 percent.

I understand that this does question the screen-shots i have posted, and i will do another test soon with the same kernel and similar usage with additional screen-shots :)

2- I can certainly understand about processes being closed after a reboot, however, since i was experiencing drain with 3.1rc4, i did check for any misbehaving processes and apps with bbs and such. Since i couldn't find anything, i reverted to the older kernel and then again checked for any changes. I did not find any. I did compare it instead of clearing the previous battery stats because i wanted to compare it to see if it was just placebo or actually happening with my phone. Now that i have compared it, i know its not placebo :)

I do have good battery life, and i did just share it. Its just not with the 3.1rc4. I am having it with 3.0rc3. I did not test 3.0rc4. I jumped to 3.0.1 and then to 3.1rc4. The best battery life i have is with 3.0rc3. Stock settings, no tweaking of any kind.

Long live Siyah!

CHeers :)
[Galaxy S II Original Android Development] confusedmuse:
After a few days without Siyah, i'm trying 3.1rc5 since yesterday.

Smoothness and performance is awesome.

With some of the betas i had huge lags on homescreen, when calling up the sense like preview.

(ADW Launcher & CM9)

With 3.1rc5 it's almost lag-free.

Even with CM9 stock kernel i've had 0.5 second lags, every 3rd to 5th time calling up the previews. (lots of widgets on the screens)

Now it's barely noticable. Maybe 0.2 seconds and less frequently.

Scrolling is just great. Back to GB feel finally. Seriously... this elastic scrolling is a joke.

With GB the scrolling is even as comfortable as the iPhone scrolling.

When using ICS with elastic scrolling and after that an iPhone, you want to

smash your phone to pieces... :(

Luckily there are developers like Gokhan fixing things like that for us.

Just one thing: i think the sensitivity is reduced a bit too much when charging...

Don't want to say anything about the battery after less than a day.

Thanks heaven for having you having this hobby. :confused: :D
[Galaxy S II Original Android Development] ndnesh:
Check the changelog. GM made a few changes in RC4 to have gingerbread-esque touch responsiveness in the kernel :)

---------- Post added at 02:26 PM ---------- Previous post was at 02:25 PM ----------

Very true!!

Cheers GM! Keep up the great work!
[Galaxy S II Original Android Development] jack_p75:
Whit rc5 deep sleep 95% :D

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] aussiebum:
RC5 is definitely waking the phone up less compared to RC4.

I'm still getting consistent wakes at regular intervals and BetterBatteryStats isn't giving me much clues as to what's causing it (seeing as background data is disabled and I hadn't touched the phone the entire day since rebooting), but this should be solvable if once I systematically go thru and check each running process.
[Galaxy S II Original Android Development] windowsxelvis:
I discovered that Wi-Fi drains me more...

I just turned on 3G connection and put it aside. After 30 mins (I didn't count it but it should be <45 mins), no change on the battery percentage.

Weird...

---------- Post added at 06:10 PM ---------- Previous post was at 06:07 PM ----------

I agree "RC5 is definitely waking the phone up less compared to RC4."

but seems the battery drain still exist.
[Galaxy S II Original Android Development] tuvi123:
gokhanmoral

You have done a great job with this kernal bust still it does not has a very wanted feature which many developers tried to implement but failed - which is NTFS support for external SDCARD, a lot of users want this feature

please add this feature.. many users don't know how to compile the modules (fuse and ntfs3g) from the latest samsung source (and even they sometimes does not load with insmod with an error - also for some users it's beyond their knowledge to use terminal and commands).

and lets be honest most users will want the external sdcard to be used as ntfs for movies etc and it just not convenient to take the usb stick with you..

I really wish there was some settting in ExTweaks app to support it (and the kernal will automatically load the modules)

I know there is some problem with unmounting the external sdcard, and even if there is not solution for this you can still add this feature in ExTweaks appilication and add buttons to mount/unmount the sdcard...

please think about it and I guess a lot of user will be happy if you implement this feature.

for a lot of users the external sdcard is only for movies/tv series and storage and ntfs will surely help and be a great feature..
[Galaxy S II Original Android Development] dee163:
No Drain so far
[Galaxy S II Original Android Development] tolis626:
I'll agree that using GB's touch sensitivity settings is actually okay.I don't know why the hell some people complain.I mean,come on.You have two cores humming at an average of 1.2GHz(mine is at 1.4GHz :D ),a pretty damn powerful GPU,a properly hardware accelerated UI and 1Gb of ram.Isn't it a shame when the phone loses its smooth feel because of "bad" screen sensitivity settings?I can live with a slight trembling of the screen once in a while,when it's connected to a charger and when the planets align and when the birds fly low.This issue is next to zip,Nada!A smooth feel is infinitely more important than that-user experience actually matters as much as battery life,if not more than it.

Anyway,only thing I'd suggest is trying the touch sensitivity from 3.0.1.It has been the best one in my opinion.Not that it's not good now,but that one's better.And it didn't exhibit any extreme elastic effect.That's just a suggestion though... :)
[Galaxy S II Original Android Development] Tuqano:
Hi Guys...Any of You know how to remove siyah kernel's boot logo that appears when the phone starts?? TNX :);)
[Galaxy S II Original Android Development] snark_be:
It's in the Changelog for rc4:
[Galaxy S II Original Android Development] AndreiLux:
So I've been running idle drain tests and jumping around kernels for the last 24h; RC5 still has the drain bug. It's not Wifi, Data, or modem related since it happens without those too. I am sure now that something in the device is not being put into sleep because the battery graph showed me a several hour long period of the device being awake while I was sleeping this night, even though the processor itself is 99% in deep sleep and there are almost no wakelocks. I've had the experience before that one should maybe trust the awake-bar in the battery consumption more, even I don't know how it collects its data.

I've been reverting back and found no drain up until beta3. Some people said it got introduced from RC2 => RC3 so I'll try to confirm that, but it's slow testing.

Other than the drain: RC5 is extremely nice in terms of responsiveness and screen sensitivity, please keep it as such!
[Galaxy S II Original Android Development] Tuqano:
TNX mate...I tried this but I did not succeed...I mean that the boot logo still appears after I created .nobootlogo
[Galaxy S II Original Android Development] snark_be:
I have also a quite big battery drain with RC5.

When I check with BetterBatteryStats, I see a partial wakelock for something called "*overflow* (the "*" are part of the name), taking 93,6% (6h45 out of 7h12).
[Galaxy S II Original Android Development] fasst:
Works for me.

.noobootlogo in /sdcard.
[Galaxy S II Original Android Development] Tuqano:
sorry if I ask you this: .nobootlogo should be a folder or a file? :confused:

TNX friend :)
[Galaxy S II Original Android Development] Draak22:
File. Make sure there's no folder or else it won't work.
[Galaxy S II Original Android Development] Tuqano:
TNX 4 you!!! ;)
[Galaxy S II Original Android Development] gokhanmoral:
see the link in the third post which has all the answers for all questions.

I have already spent enough time on the drain issue.

FYI, I noticed some drain on rc4 (probably related with blnww problem) and I don't have that in rc5 and rc6...

maybe I don't notice the difference with my heavy usage pattern.

but people talk about having 1-2% overnight (8 hours?) with other kernels having all kind of sync enabled...

I never had that and I don't think it is even possible unless that report is wrong.

even with 2% loss in 8 hours it makes 400 hours and I don't think it is possible.

anyway... I won't try to make the kernel any battery efficient until there is a serious problem which I will notice anyway and from now on, please consider siyahkernel as the most battery inefficient kernel.

oh, and there is undervolting...

I will never answer your questions about your device's instability problems with your previous undervolting values.

there were some questions about why reverting back to 3.0.15.

we had a task manager "active tasks now showing" problem before, remember?

it was because of a merge conflict with upstream and we have resolved it in a wrong way.

there were some other conflicts and I wanted to make sure that we didn't make any other mistake similar to that one.

I also read speedmod thread and I didn't see anybody complaining about any instability issues (except for a known underclocking problem)

it won't be a problem to patch to 3.0.28 if I find any bugs. I will make that merging with more care next time.
[Galaxy S II Original Android Development] AndreiLux:
Idle with Wifi and no unusual traffic will get you down to 0.4-0.6% usage per hour while idling, there's no point in discussing or denying that as it is possible and I've repeatedly done in for extended periods of time for even a week over the 10 months I've had the phone. I hope you're not too serious or consider it a change of direction for the kernel with that last sentence.
[Galaxy S II Original Android Development] puccini:
what is the point of keep talking about idle states all the time. Surely as long as it's not losing ridiculous amounts overnight that's all that matters. i don't see the point in having a phone like this and NOT using it.
[Galaxy S II Original Android Development] jim-bo:
But Gokhan is referencing people who are citing 1-2% in 8 hours, which is 0.12-0.25% per hour, which is massively better than even your figures (which are impressive, but achievable). His last sentence is basically telling people not to expect 0% drains, and to stop moaning about tiny deltas in overnight drops.

I seriously doubt that he is going to start actively coding the kernel to burn power, he's just fed up with the people whining on about what may no longer even be a problem, and certainly many / most of the people posting complaints are not backing their position up with anything other than anecdotal data on the actual drain they are seeing.

To be taken seriously, a complaint about drain should ideally be backed up with screenshots, BBS stats, and comparative data for a specific kernel that acted differently, not just "it drains faster on RC(x)" when that RC has only been out for an hour.

Because most people don't use their phone overnight, so it is a pretty good baseline for how the phone behaves when it is idling, which is the only time that you can really make changes to battery life. With this phone, once the screen is lit, anything else you do is basically like bailing out the titanic with a teacup.
[Galaxy S II Original Android Development] puccini:
Because most people don't use their phone overnight, so it is a pretty good baseline for how the phone behaves when it is idling, which is the only time that you can really make changes to battery life. With this phone, once the screen is lit, anything else you do is basically like bailing out the titanic with a teacup.[/QUOTE]

But that's when i charge mine. I seriously can't believe people don't have access to a power socket or USB port for charging. Also people pick ROMs based on various factors like performance, battery, etc so why not kernels.

Here's a quote from the Hydrogen thread:

"i got bad battery life with neak too. You can try siyah kernel"

I just think people are expecting too much that's all. if you've EVER owned a portable device in your life then you must realise a performance increase means less battery life. as a former owner of one of the first iPhone 3gs where i charged it twice a day maybe i've just been conditioned to expect to have to charge it regularly.
[Galaxy S II Original Android Development] fifa_king:
I think all he is saying is that theres nothing much more he can do without any concrete proof (bbs stats, cpuspy, logcat etc.) regarding battery drain.

Ive been doing some testing with my phone Just idling with most latest RCs and I do get that kind of drain when idling with siyah.

flashed rc5 and was a bit concerned because i had huge batt drain for the first time overnight.

So I went into extweaks and activated blnww cos i realized that I had it unchecked in rc4 but it was actually being activated afaik,

I have been getting excellent idle drain again like rc1 throughout the day at work with all sync enabled on (3g/h+). 1% per hour. The battery bar has been horizontal after I have enabled blnww in extweaks even tho I dont use bln (weird and maybe placebo).

But I recommend some others facing drain to do the same.

Also in RC2 when edit: 100mhz and 1600 mhz was removed, the uv tables will be messed up If you undervolted (1400mhz voltages will be used for 1200mhz and 1200mhz voltages will be used for 1000mhz and so on) SO plz make sure you reset your uv settings after rc1 which may be the cause for the battery drain because of excess voltage. Battery settings for extweaks should also be activated in cwm after you have installed extweaks from market.

I hope this helps a bit for those with battery drain and lastly apologies for messing up the thread last week especially to tolis and gokhan.
[Galaxy S II Original Android Development] AndreiLux:
Excuse me for my following tone but this type of reasoning is utter nonsense and I'm sick of hearing it. There are people, including myself who sit in front of a PC most of the day, be it at work or home, when all communication is then redirected towards the computer instead of the phone, and the phone is idling. When I'm not on my PC then I want to use my phone and the whole point of a smartphone is to replace or mimic the media functionalities of the PC. I'm not going to use my phone if I have a big screen in front of me available most of the time.

Well those people are dumb and he's referencing to the worst examples, but there's plenty of other people here posting credible data which matches what I've been measuring. I've worked/helped/talked to Gökhan enough before to hopefully have enough credibility about the things I'm saying. We're not talking about tiny deltas, but around 5 times the idle consumption. I swear I'm going to pack out the amperemeter out and make a battery circumvention circuit to measure the current draw from the phone, the only thing preventing me doing from that until now is that I have a too sensible of a measuring device with a 200mA fuse that might blow up if I hook it up to the phone.

Edit: And I also confirm that it is introduced in RC3. Which makes me wonder if it's not related to BLNWW. I don't know what changes you did to it as I can't see it on the repository (Or I'm blind). But enabling a LED would require to keep some of the bus active.
[Galaxy S II Original Android Development] gokhanmoral:
that response was for those who disable wifi to save battery and leave "I have battery drain issue" without any scientific data and information.

I am not changing direction and I will not start making every battery consuming change in the kernel.

but if people know that they won't get the best battery life with default settings it will save my time and lots of other's who read this thread. "siyahkernel is the most battery inefficient kernel" statement will make it easier for them to understand. yes, it is a bold statement, but what they claim and defend is bolder.
[Galaxy S II Original Android Development] puccini:
I'd just like to add, constructively, with regards to this release that i have had no kworker process alerts on watchdog since flashing this Kernel last night. My threshold is set to 30% and it was quite regular through all the RC reeases until this one.
[Galaxy S II Original Android Development] ZonyX:
i get great life with this kernel, and always have.

love the dual booting, but a quick question..

do any changes i make in primary rom to kernel via extweaks, still apply when i boot into secodary?

im hoping i dont have to get reseting my set up everytime i boot either rom
[Galaxy S II Original Android Development] :
http://xdaforums.com/showpost.php?p=24233085&postcount=2

25) "Are init.d scripts and extweaks profiles shared across the roms so that i can make changes by booting into any rom and the other rom automatically inherits the settings?"

A. NO. Roms have differet /system partitions so different init.d directories. Roms uses different /data partitions and extweaks profiles are stored under /data/.siyah. So you gotta configure both separately. Initramfs scripts are shared anyway since both rom uses the same kernel.

please read op my friend