yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] giorgosaero:
I think that k2-18 test 2 is the best....thanks hardcore for the amazing kernel
[Galaxy S II Original Android Development] SupraN0va:
Since when does speedmod support setcpu?
[Galaxy S II Original Android Development] CamoGeko:
It doesn't AFAIK.

Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
[Galaxy S II Original Android Development] SupraN0va:
What means AFAIK?
[Galaxy S II Original Android Development] beaver2233:
"As far as I know"
[Galaxy S II Original Android Development] SupraN0va:
Yes it does.
[Galaxy S II Original Android Development] CamoGeko:
So hardcore finally has given in? :eek:

Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
[Galaxy S II Original Android Development] bungknees:
He hasnt given in, it just allows you to change governors, thats pretty much it, maybe underclock, but definitely not overclock.
[Galaxy S II Original Android Development] CamoGeko:
Hmm... well underclocking yes. Since hes done a very good job at making this kernel battery efficient, without having the option to undervolt obviously.

Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
[Galaxy S II Original Android Development] qureyoon:
I'm using 18test3. After doing a drain and full charge, this morning I've experienced 2 times my screen went blue all of a sudden.

I can still see something, it seems like there is a blue layer on top of it. Hope this make sense.

Does anybody experienced this?
[Galaxy S II Original Android Development] mariotme:
Nope sorry. Never experienced such thing running 18 test3
[Galaxy S II Original Android Development] AMDPOWERFIST:
wipe cache & davlik before and after flashing the kernel?
[Galaxy S II Original Android Development] awojtas:
Yes! but mine seemed green. Like a transparent layer was added on top for a split second!

On K2-18-Test3, coming from K2-15.
[Galaxy S II Original Android Development] planetf1:
Not seen here..with test 3
[Galaxy S II Original Android Development] bervin:
I had a blue layer with test 1, had to reboot my phone to get rid of it
[Galaxy S II Original Android Development] coolfire:
No problems with test 3 so far, running it for the past 15hours, and all seems good. :)

Sent from my SGSII
[Galaxy S II Original Android Development] coolfire:
Bro, I get that too with both KI3 and KI4...

Sent from my SGSII
[Galaxy S II Original Android Development] hongkongtom:
Guys, what Wi-Fi policy do you use?( default/ on when plugged/ always on) I used wifi-keepalive app and chose "always on " with work around 1 and it drain like hack over night, it drained 4% for 1hr screen off idle, I'm on k 18test2, any idea?
[Galaxy S II Original Android Development] fidorulz:
Had that but with 18test1 running test3 now and no issues so far.

For me issue only occurred 2 times and would only occur if the phone had been asleep for maybe a few hours without the screen coming on

Upon waking the whole screen it would be blue (BSOD blue color) and the softkeys would be lit. I wouldn't be able to do anything unless I turn the screen off and on again and it was fine for a while again
[Galaxy S II Original Android Development] FrenchSparda:
For me my screen went red 1 times yesterday o_O ....i go back to test 17
[Galaxy S II Original Android Development] BrandoHD:
In your opinion, but mostly because of your location, KI4 was very poor on signal for me, because of my location(s), but it has nothing to do with it being newer...

I use "always on" and I have never gotten more than 8% drain overnight (8-10 Hours), and if I do get any drain, I can usually identify the app that caused it, I believe Wifi is the better option for me since my data connection is pretty slow.

Also I don't turn anything off, I don't disable the syncing of anything (two email accounts, two twitter accounts, weather app among other things), the phone runs the same way in the night as it does in the day, My advice to you is to use Better Battery stats and set a custom Reference Point before you go to sleep, set the app to display the partial Wakelocks from the custom reference point and go to bed, if you awake to heavy battery drain, check the app and see why the phone was awake......
[Galaxy S II Original Android Development] rajaspidey:
don't remove apps freeze it!!
[Galaxy S II Original Android Development] RobinRichard:
Wow! Now that's an extensive review of the kernel's battery life! Thanks man!
[Galaxy S II Original Android Development] rajaspidey:
Tankee ll lost an zip file of all screenshots soon!! I only posted some to reduce thread size!!
[Galaxy S II Original Android Development] Seifer1975:
Can share why? I always remove.
[Galaxy S II Original Android Development] eranyanay:
With 6:40 hours of sleep, where's data is on (as always) I lost 14% with 18-test3. Device had no wakelocks at all and was at deep sleep all the time.

With my former kernel (ver. 13) I lose 1-2% for this time period.
[Galaxy S II Original Android Development] ssuukk:
Mine ate whole juice during the night with latest speed mod. never happened before.
[Galaxy S II Original Android Development] shahulvm:
Battery life with k18-test3

I had changed the base rom from ki4 to kj3 and then installed k18-test3 kernel with baseband xxki4..now the battery life seems to be better...

I had cleaned the files from lost.dir folder.

Also, by default the kernel has conservative governor which lags the phone while unlocking, hence changed it to ondemand..(using setcpu)

Now battery life seems better with snappier performance :)
[Galaxy S II Original Android Development] lrcquest:
Try KI3 modem as it is said to be lesser battery intensive than KI4.
[Galaxy S II Original Android Development] hardcore:
no, default governor is ondemand. It's because you installed setcpu which changed the governor to conservative.

I recommend not using setcpu to change anything for this kernel.
[Galaxy S II Original Android Development] lokhor:
Anyone know why Android os process is so high?
[Galaxy S II Original Android Development] hardcore:
It's just a reporting problem. I just ignore it.
[Galaxy S II Original Android Development] lokhor:
Ok cool. How much screen time do you get? I'm at 13% with only 3hrs screen time :( and I have a 2000mah battery.
[Galaxy S II Original Android Development] eranyanay:
I dont know if its related, but ever since I changed from k2-13 to k2-16/18t1/18t3 I notice a big volume change - the sounds are very weak comparing to before..
[Galaxy S II Original Android Development] darkmessiah:
WHile moving from kernels do we have to wipe cache partition and wipe dalvik cache also ?

or jus install the other new kernel thro cwm ?

please advice ..
[Galaxy S II Original Android Development] mariosraptor:
It is highly recommended.
[Galaxy S II Original Android Development] shahulvm:
K18-test3 is all fine..

Hi Hardcore...finally all issues has been sorted and am sticking with k18-test3..rock solid battery life and performance..kudos to you..

Cleared the files from lost.dir and then wiped cache and dalvik cache..and proceeded with the installation..so far, its going great

Kernel : Ofcourse, Speedmod k18-test3 :p

ROM : WanamLite KJ3 v5.7

Theme : ICE CREAM SANDWICH v1.3 DOMINATION*TOTAL OVERHAUL*(KJ3)

Keyboard : [MOD][08/11][v1.4]Samsung Galaxy S II Keyboard|Comma, layout edit, popup shortcuts

Launcher : ][MOD][08/11][v1.2/v2.3/v3.2]Euro & 4G TouchWiz Launcher|Change Home|5 Columns|DP
[Galaxy S II Original Android Development] hardcore:
Sounds good.

I'm interested to hear feedback about how battery life for k18-test3 compares to k17 or k16.
[Galaxy S II Original Android Development] jsompis:
With one cycle and little usage(~2h screen on), i don't significantly see difference of battery usage on 16,17,18t3.
[Galaxy S II Original Android Development] shahulvm:
Figured out how the governor changed from "ondemand" to "conservative".

It was tweak put in by the ROM..modified the script in init.d and its all fine now :)
[Galaxy S II Original Android Development] richyy74:
My typical use is somewhere around 15 hours 3,5-4 screen on, one hour on phone. Stock gets to around 10-15% at the end of the day. K18test3 was over 30% at the same time. At 16.00 stock usually hits 50%, k18test3 was 65.

Improvement is quite noticable in my case.

Stock kj3 rom, 3g all day, fast dormancy disabled, syncs on.

Sent from my GT-I9100
[Galaxy S II Original Android Development] hongkongtom:
Dear achillies400 , thanks for the advice, but could you tell me how to set custom reference point?
[Galaxy S II Original Android Development] amitoberoi:
Open betterbatterystats, click on left soft button which brings up the menu, click on actions and then click on Set custom ref. Your custom reference point will be the time when you click on the Set Custom Ref. After that let it run and in the morning if there is more than normal battery drain, you can check what is draining the battery. Remember, dont close betterbatterystats as on closing the custom ref point will be lost.
[Galaxy S II Original Android Development] gtda:
K18 t3 going great, 21hrs and still on 31% first cycle. pretty average use I guess, lots of txts, a few phone calls, music playing and always on auto brightness, auto gsm/cdma mode. Very happy with this one hardcore. Thanks heaps. had issues on t2 tho, screen also went green, and wouldn't wake some times.
[Galaxy S II Original Android Development] eranyanay:
ever since i upgraded from k2-13 to k2-16 Im having weird issues with sound.

Its noticeably lower than usual..I can barely hear it..its like 20% of what it was.

After I wipe dalvik and cache it got back to 100% performance but after a while (idle) it got back to 20%

Anyone know if its kernel related or how to fix?
[Galaxy S II Original Android Development] Molitro:
On a related topic, I'm curious if there's a particular reason for not updating the kernel version to .14.

I mean... Yeah, is irrelevant having high or low percentage of AOS if it's going to drain the same, but there isn't any improvements at all in the newer versions?

I like the simplicity and good performance no-questions-asked of speedmod, but I keep getting forced back to Siyah because under the same circumstances it always maintains a low idle battery drain, while speedmod often goes a little crazy and eates twice as much as it should an things like that, to show then an unusually high AOS and too many suspend and events/0 wakes (tested lately with most versions, 16, 17 and 18 test1). This just doesn't happen with Siyah and I wonder if it has anything to do with the newer versions of the kernel, or they introduce just minor changes that have nothing to do with this.
[Galaxy S II Original Android Development] Pfeffernuss:
With Test3 I'm again having micro-stutters. Test2 is completely smooth. Smoothest kernel (for me) so far. Will undoubtedly be the cause of the edited governor but so be it.

I find absurdly smooth scrolling more important than a somewhat better battery-life. Will charge the phone at the end of the day anyway ;)
[Galaxy S II Original Android Development] hongkongtom:
Thx a lot, I'll try.
[Galaxy S II Original Android Development] Mustoura:
Same i found 18.2 smother with better battery life than 18.3 retesting 3 again just incase. I'm on 32% after 17 hrs. I was getting 1day 14hrs 32% on 18.2.

Rebooting , charging & flashing just incase something went astray i don't believe its speedmod .

Lol 19 will probably be released by the time i finish testing. The way Hardcore works .

What a gun.
[Galaxy S II Original Android Development] nickporwal:
Cant say different. I am also getting stutters while scrolling through settings UI and other apps. Even contacts app scrolling is just stutturing very slightly. its a minor problem but noticeable. I would go for better UX than a slightly better battery life. Test 2 was smooth though.

Anyway thanks to the Hardcore for such a great work. Its not easy to dedicate such a long time to Development for community.
[Galaxy S II Original Android Development] doongoo:
Hy richyy74!

Did you check with hungarian t-mobile the fast dormancy-question if they use it or no? Or just disabled at your own? I did not disable and get great battery time so. I am only curious
[Galaxy S II Original Android Development] ludester:
So far its been good.
[Galaxy S II Original Android Development] richyy74:
/OFFTOPIC

I did a few tests. Battery is a bit worse, but not much, browser page loading and 3g speeds are noticeably higher while disabled.

The T-mobile csc contains the following:

<Network>

<NbFastDormancy>2</NbFastDormancy>

<FastDormancy>

<NetworkName>T-Mobile H</NetworkName>

<FastDormancyEnableStatus>off</FastDormancyEnableStatus>

<LCDStatus>off</LCDStatus>

</FastDormancy>

<FastDormancy>

<NetworkName>T-Mobile H</NetworkName>

<FastDormancyEnableStatus>off</FastDormancyEnableStatus>

<LCDStatus>on</LCDStatus>

</FastDormancy>

/OFFTOPIC
[Galaxy S II Original Android Development] planetf1:
@militro for the sake of comparison what was your siyah configuration and what was your usage profile like?
[Galaxy S II Original Android Development] AndroidGX:
Ok, 18-test3 has now exactly same performance as 18-test1, is was predictable but I can confirm this after testing.

I guess it's a good idea to continue with this base. :)
[Galaxy S II Original Android Development] spirt:
strange, but after playing with 17test1 and 18test(1-3) CPUspy says that my device doesn't use 1000Mhz state anymore. every time before kernel flash i cleared both caches. and now even on other kernels (previous speedmods, cfroots or syiah) 1000Mhz is not in use.
[Galaxy S II Original Android Development] shahulvm:
Check if any scripts are there in /system/etc/init.d folder..scripts would typically start with S***

some roms put in scripts for tweaks...atleast was the case for me...

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

Siyah has lot of choices(oc/uv/governors)...i had used lulz governor and got excellent battery life and performance. in Siyah, the battery life was taken away by the display..I switched boats because in speedmod it has lower display battery consumption...otherwise for a normal user both kernels are just fine..
[Galaxy S II Original Android Development] Seifer1975:
The slight SOD issue happened to me twice today. Switched to XXKI3 modem to see if it's better.
[Galaxy S II Original Android Development] hongkongtom:
I'm used BBS to monitor, there is no major partial wakelock which drains battery, I saw in "Wifi On" in ranks #1 in Other having as long as I set custom ref., (cause I tried using wifi-keepalive (with workaround 1), still can't figure if keeping wifi always on is the reason for battery drain even in deep sleep, but I observe this didn't happen when I'm using 3G data.
[Galaxy S II Original Android Development] Molitro:
I use a very little undervolting, exynos' settings, to be more precise. I usually use ondemand governor, though in the last versions lulzactive just works better, smoother, whiout having an impact on battery. And 100 mhz min frecuency.

Mi usage is generally light, two-three days between charges, an hour-hour and a half of screen per day, so a lot of deep sleep. And that's where using siyah makes a difference. Not always there's a charger available, and it can very well be the difference between reaching the end of a charger-free weekend or not.
[Galaxy S II Original Android Development] planetf1:
Thanks. I did try a few Siyah builds and tbh it was pretty much as I expected

* loads of choice (clocking, voltages, governors etc) -- but never enough time ....

* Seemed to be a little better on sleep that speedmod (I also used the lulz governor initially)

* occasional lag

* worse on-time battery performance

* back to the more vivid colours & brighter auto-brightness (which I now really prefer with speedmod)

Probably going to stick with speedmod for now. I like the principle of keeping it simple. It may never offer the ultimate battery life or performance for some, but will offer the best for most. IMO.

currently seeing a fair amount of wakelocks (relatively) from my corporate email client/antivirus, as well as a BT survey app I'm running

Yet even with that over 4hr10 with sync etc running as usual (facebook,ebay.messenger,twitter,gmail,gtalk,foursquare,corporate email, junos,tasker etc) battery only dropped 3 (could be 4) %. Albeit not fully calibrated.

That was with 37 mins non-sleep time (but only 1-2 mins screen time) and a few mins cpu for antivirus etc.

Not al all bad.

Some constant use (browser/twitter) over 40 mins (screen on) after 7hr 50 on has left me at 83%

17test3
[Galaxy S II Original Android Development] hansation:
cpuspy shows my phone does not sit at 1ghz anymore after installing k2-17.1 and k2-18.1. still after flashing k2-16 same problem.. any idea how to fix?
[Galaxy S II Original Android Development] planetf1:
thans - I never tried undervolt and didn't get around to 100 Mhz - think it wasa little better

Ah I'm probably a heavier user. I'd expect 1.5-3 hours/day at a guess which I think is getting into where speedmod helps

Good to have the choice!
[Galaxy S II Original Android Development] pacc:
I'm actually wondering which way this kernel should go for the next version, Test2 or Test3?

Probably a decision between better performance against saving battery, I have preference for the first (Test2).
[Galaxy S II Original Android Development] planetf1:
I'll vote the other way - *sensible* battery saving whilst maintaining "stock" performance levels would be my preferred direction
[Galaxy S II Original Android Development] apeiron6:
Same here
[Galaxy S II Original Android Development] hansation:
+2 for battery saving
[Galaxy S II Original Android Development] mariotme:
Hardcore may i ask what does (stats 0 error) means while trying to flash a cwm zip?
[Galaxy S II Original Android Development] pedrolopes665:
Im with 18test1 for 4 cycles and can affirm that battery life is better than my previous kernel, 16.

As the difference between test1 and 3 is only the CWM version, I think you can release a stable version of 18.
[Galaxy S II Original Android Development] crash_194:
I'm totally miffed as to why everyone is making out k18 test 2 hammers battery because i've been using it for days and hardly notice any difference, only a snappier smoother device? It definitely doesn't cause any excessive drain and everything is working just how it should for me with zero issues. I'm running a stock kj3 rom by the way guys.
[Galaxy S II Original Android Development] mariotme:
Sorry for quoting myself but can somone please comment? :s
[Galaxy S II Original Android Development] carlos67:
Agree 100%. 18 test 2 is very fluid with good battery for me. Its a keeper I think. Running Leomar 2.7.1 xxki3.
[Galaxy S II Original Android Development] john291:
Does anybody has gps problems with version 18?

I cant get a lock.

Or would it be rom related?
[Galaxy S II Original Android Development] celeritykid:
on ki4, sleep of death occured on both 18 test2 and test3. was perfectly well without any SOD on 17test1. any fix for this?
[Galaxy S II Original Android Development] fidorulz:
Would be more modem/rom
[Galaxy S II Original Android Development] AndroidGX:
Try "FasterFix" from Market.
[Galaxy S II Original Android Development] pjdona:
+1...but with Test 2 and Test 3 I had a problem. In a couple of times, my device has not awakened from deep sleep immediately, but after 5/6 seconds.

PJ
[Galaxy S II Original Android Development] lrcquest:
Installed K2-18 test 3, boot into recovery to wipe dalvik / wipe cache. Powered off from recovery option. When connected to the charger the system again enters the cwm recovery mode !!

Had to reboot & power down, again connected to charger & now it was normal.
[Galaxy S II Original Android Development] akbarhash:
Shifted back to k2 18-2 there is some stuttering in k2 18-3 in whatsapp Reddit app and xda app. Mostly while scrolling.

2 is smooth as butter.

Sent from my GT-I9100
[Galaxy S II Original Android Development] stylez:
Same here and compared with 17 test 1 to which isn't showing the same scroll lag when using File Explorer etc and also noticed on comparison Sense preview Go Launcher.

Switched between in as fair test as could do no additions and with bed in.

Battery life not an issue on either thou.

Didn't try 18 test 2 will flash...
[Galaxy S II Original Android Development] alexkno:
Happened with 17 too
[Galaxy S II Original Android Development] Nucleardwarf:
Am i the only one that actually has much worse battery life with Speedmod compared to Siyah kernel?
[Galaxy S II Original Android Development] pepe2909:
no..me too :)
[Galaxy S II Original Android Development] giorgosaero:
Hardcore when we will have a final kernel....like k2-16?
[Galaxy S II Original Android Development] CamoGeko:
Same here.

Very expectable though, since Siyah is a rather more agressive development plus it includes more tweaks and allows undervolting which helps battery life.

Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
[Galaxy S II Original Android Development] netjunkie51:
I've had problems with bluetooth headset ... many disconnects... With 16 everything's working well again...

Sent from my GT-I9100
[Galaxy S II Original Android Development] planetf1:
Liking 18test3.

18 hours on, 2:45 screen on (browsing etc, no games), sync etc. 42% remaining.stock battery

Though this is with perfect 3G (femtocell) and wifi for all except 2+ hrs
[Galaxy S II Original Android Development] shahulvm:
Its ROM related, I had gps problem with checkrom..but no issues with wanamrom
[Galaxy S II Original Android Development] dragon135:
I also experience stuttering in XDA app when scrolling with K2-18 test 3,

My only issue with K2-18 test 2 is frequency 1GHz is rarely used (using CPU spy).
[Galaxy S II Original Android Development] jlevy73:
Yeah I've noticed a bit of lag there as well.
[Galaxy S II Original Android Development] lrcquest:
good deepsleep with k2-18-3.

& just noticed that the screen got a blue tint for a fraction of a second! Probably will be back to 17...
[Galaxy S II Original Android Development] nickporwal:
@Hardcore:-- Please put back the optimizations you used in Test2 as that was more smooth while scrolling in apps. Test3 is stuttering more. Thanks for the hard work. Appreciate your dedication.
[Galaxy S II Original Android Development] andro6600:
+1 for that! Also test2 resolved youtube choppy playback issues.
[Galaxy S II Original Android Development] hardcore:
I'm testing it out again, with some other combinations of changes too.
[Galaxy S II Original Android Development] lrcquest:
can someone post a link to k2-18 test 1 odin???
[Galaxy S II Original Android Development] bungknees:
I agree, test 2 is very smooth, thanks for the great kernel yet again.
[Galaxy S II Original Android Development] alexkno:
K2-18 test3 is much better now while using phone compared to test2 for battery

At night I loose with test 3 about 1% per hour with data and Wi-Fi off.

With k17 I had 3 to 5% for 10 hours. No remarkable wakelock in bbs

On ki8 deodexed stock rom
[Galaxy S II Original Android Development] alexkno:
Going back to 17 now
[Galaxy S II Original Android Development] kartalgurhan:
friends,

Please don't yell at me but,

instead of just unmotivating the hard work here, why don't you at least try to present your findings/thoughts with some evidence and/or documentation?

thank you for your understanding

best regards,
[Galaxy S II Original Android Development] rzat:
Something not right. With WiFi, data and sync on ive never had more than 0.8%/h. Tested with CheckROM 2 and various kernels. Best i had was 0.7%/h on CheckRom 2 and speedmod 17.

Currently testing CheckRom 3.1.1 with default kernel (stock i belive) and also 0.7%/h. Flashing speedmod 18t2 today.
[Galaxy S II Original Android Development] hardcore:
Thanks for that info. In K18 there are drastic changes to the way power management is handled, so I need feedback to see how much better/worse it is than K17.

For example, I might implement cpu hotplugging again if it does save battery life.