yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Rampler:
Can anybody test if the function "handy control" in Myphoneexplorer works. In 2.6.7 it doesn't. With NEAK kernel no problem.

Thanks on advance

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II Original Android Development] cmd512:
2.6.8 looks solid so far, thanks gokhan!
[Galaxy S II Original Android Development] burner07:
i just got a soft reboot while listening music? 2.6.8 xila2
[Galaxy S II Original Android Development] CamoGeko:
Kinda pointless post really without a log or some other info like your CPU settings......

Had no instabilities like that here, don't think anyone else has so far either. :)

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Death Star.
[Galaxy S II Original Android Development] stylez:
Running sweet here on usual settings extremely smooth :)

apu gokhan done it again ;) thx

Sent from the valley of the shadows....
[Galaxy S II Original Android Development] legendasboy:
How is 2.6.8 battery usage compared to 2.6.8?

Sent from my Galaxy SII using Taptalk
[Galaxy S II Original Android Development] cmd512:
2.6.8 battery usage is identical compared to 2.6.8.

If you meant 2.6.7, not a whole lot different. Idle battery life does seem a tad bit better, but will need more time to confirm.
[Galaxy S II Original Android Development] remorema:
this last version drained my battery from 100% to 15% in 3h.

default settings no scripts mods or overclock. just 3h of heavy usage.

Tapatalked from "The ICS Killer"
[Galaxy S II Original Android Development] xavihernandez:
If you are running CyanogenMod it's a known issue and it's not related to kernel. Music app used to freeze (randomly?) when listening music and browsing music library or so. It happens when you got lots of music (I guess because it didn't happen when I had a little amount of music). I don't know if this bug happens on other ROMs.

I thought I had fixed this problem with a minimal frequency of 500MHz but it still.freezes sometimes.
[Galaxy S II Original Android Development] legendasboy:
Well had one sod after making a call maybe I should take the uv...don't know why I had this just after flash

Sent from my Galaxy SII using Taptalk
[Galaxy S II Original Android Development] CamoGeko:
Hmm.. before flashing the kernel did you uncheck set on boot in VC and wipe cache and dalvik?

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Death Star.
[Galaxy S II Original Android Development] stevehkim:
after 8 hours on 2.6.8 everything is smooth. no problems. but yes batt is draining unusually quickly. will report back in a few days.
[Galaxy S II Original Android Development] legendasboy:
Yes cleaned the vc boot and wiped caches.

Sent from my Galaxy SII using Taptalk
[Galaxy S II Original Android Development] DAGr8:
lol you stole my quote here buddy :P your just missing sauron ( or saurom ) rom to tun your kernel..
[Galaxy S II Original Android Development] RotesMeerJogger:
siyah 2.6.8 run since a few houers on my s2 and so far so good all work perfect. battery life is very good like 2.6.7. thank you again gokhan for a great kernel :-)
[Galaxy S II Original Android Development] olifee:
A short update on my external sdcard-problem:

As I still experience it with 2.6.8, but also with 2.6.6i, I guess it is not a kernel-problem, but the sdcard itself is broken *sigh*.

It's a pretty 'young' 32 GB Class 10 Samsung card, just a bit older than three weeks, so I did not think it might be the cause of my problems.

I am now testing it with the tool 'F3' (works like h2testw in Windows, i.e. fills the card with files filled with random numbers and reads them back).

The errors I got were really 'interesting': Once I tried to update something in my debian chroot, files in completely unrelated places on my card became corrupt (even outside the loop-file).

However, a check with rsync did not reveal any corruption after restoring my backup and then verifying it with checksums.

As soon as F3 is finished I will update this post with the result ;). In case it does not find problems, I really am at a loss...

EDIT: Yep, it's the sdcard. It's new, and it's broken, first broken sdcard I saw in my life.

Up to now, f3 has found 'only' 132 corrupted sectors, which explains why it became pretty apparent in debian only and not in 'normal' file storage.

Now, I am back to an older class 4 card, but loop devices work fine here => kernel is perfect :).

To anybody also experiencing vague sdcard-problems: Try F3 on linux or h2testw on windows to check whether your card really is ok...
[Galaxy S II Original Android Development] andylhchen:
Reporting a GPS problem. Takes alot longer to lock in 2.6.8, similar to 2.6.7

Wasn't a problem back in 2.3-2.4.

Already tried the GPS fasterfix and GPS status, results same.
[Galaxy S II Original Android Development] CamoGeko:
Tried changing your Modem to see if that makes a difference?

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Death Star.
[Galaxy S II Original Android Development] cmd512:
Zero issues with GPS on 2.6.8. Have you looked into this AGPS patch, works brilliantly:

http://xdaforums.com/showthread.php?t=1447599
[Galaxy S II Original Android Development] legendasboy:
nice patch, by the way i have to say this....i love your car
[Galaxy S II Original Android Development] crazykamui:
^^;;

Happy new year...^^

iam korea M250S user

2.6.8 kernel is Thanks..^^

1problem...;;

witi on/off .. hot reboot...

on -> off

off -> on same reboot..

9100 international not problem...;;

Always Big Thanks...Gokhan..:D
[Galaxy S II Original Android Development] skull7545000:
I've been using siyah for long and find it is the best kernel ever, moving to 2.6.8, its still great, i've got one question, how to change the frequency step by changing freq_table? Where exactly it is? Thanks
[Galaxy S II Original Android Development] Grimmy1st:
Getting a few SODs (reboots) with 2.6.8. coming from 2.6.7 with wiped caches, no changes. UVed, sio, ondemand, no additional scripts. No problem with these settings @ 2.6.7.
[Galaxy S II Original Android Development] pikachu01:
Isn't that normal? If you're playing games, that's considered normal.

What configuration are you in? CM7/MIUI? Try without UVing?
[Galaxy S II Original Android Development] MistahBungle:
Exactly Pika. I would have thought that was pretty normal. Games are normally the heaviest battery drainers. So much CPU/GPU time being used. Nothing to do with the kernel at all IMHO.
[Galaxy S II Original Android Development] Rampler:
First of all thanks for your good kernel..

With your Kernel (2.6.x) i cannot use the function "control Handy" with MyPhoneExplorer. I installed for testing purposes the NEAK Kernel, with NEAK i can this function. MPE (especially "control Handy") works also with the Stock Kernel. In other forums people says the same. It seems that something is wrong with the monkey services in your Kernel.

best regards

Rampler
[Galaxy S II Original Android Development] singingshiver:
I have my touch key light duration set to always on, but occasionally the lights do not light up. If I lock the phone and then unlock they work again. ANy ideas? I am using Siyah Kernel 2.6.7...previously on Speedmod and wasn't an issue, but want to stay with Siyah as smoothness and cwm app compatibility are great.
[Galaxy S II Original Android Development] ziroxs:
Hi. Antutu calculated with 2.6.8 a write speed to my SD Card of ~ 8 MB/sec. I repeat this test i get always this small values.

Can someone confirm that this is a normal value?
[Galaxy S II Original Android Development] mundixx:
That depends on your MicroSD card class.. i only get ~5mbps max write speed from my Class 4 card

Sent from my GT-I9100
[Galaxy S II Original Android Development] ziroxs:
Because with GingerMod 0.8 and Abyss i get over 50 MB/s :confused:

Now only 8 MB/sec
[Galaxy S II Original Android Development] cooldfuzion:
With this new kernel i had one freeze and i think that the battery is draining to fast compared to the 2.6.7!
[Galaxy S II Original Android Development] gokhanmoral:
maybe abyss kernel has filesync disabled, I don't know.

or maybe using some other magical method to get that high writing scores...

filesync is not disabled in my kernel and I will not disable it in the future as it can cause data loss. it is not worth risking to lose data to see some higher numbers in benchmarks.

using different I/O scheduler may get you a little higher numbers in benchmarks but it will not be 500MB/sec.
[Galaxy S II Original Android Development] alferret:
Dont know if anyone has had this prob. Phone wont wake up from sleep, pressing home doesnt do anything keep pressing cap buttons & I get the odd beep & I have to pull the battery to restart the phone.

Any Ideas?

KJ4 & 2.6.8 (had the same issue a couple of times on 2.6.6)
[Galaxy S II Original Android Development] :
No problems here my friend.

@all who concerned regarding benchmarks...benchmarks mean ****....my phone on conservative governor is not only running smoothly but i have no problems regarding connection data, watching youtube videos, porn over the net:D and playing games....i do not mean to be rude to people who love benchmarks but be honest with yourselfs...if they were so accurate you would get the same score or near enough....but you do not as they go all over the place..hence meaning jack.....Gokhan..Your kernel is perfect no complains whatsoever my friend
[Galaxy S II Original Android Development] rizcom:
i flashed 2.6.8 kernel and my external sdcard was corrupt i then fix it by reformatting in phone i also found the gallery app if u have alot of pictures it would freeze and lock,only way out of this was to press the power button or home button force close with task manager i had no problems like this with 2.6.7 which i think is the best kernel i have tried for my phone so i am back with 2.6.7 looks like a keeper thanks:)
[Galaxy S II Original Android Development] mrzax:
Hi.

A question: i modified freq_table but at reboot frequencies are set as default. Is there the possibilty to mantain custom frequencies?

Ty all.
[Galaxy S II Original Android Development] MistahBungle:
*stands and applauds*

Bravo, Sir. Bravo :)

Edit to add - Glad I'm not the only person here who watches porn on their SGS2 :D
[Galaxy S II Original Android Development] :
Well it is true though...Porn on Super Amoled is heaven:D

Anyway to what i wanted to say..Benchmarks are just numbers...If your phone is not lagging, if it is not stuttering, or gives you problems when watching a film or playing games you know that the kernel that you are using is perfect and good enough..When scrolling through homescreens or appscreens the same...What is the fascination about benchmarks i really do not get it?

if you want to have a super fast performance phone then switch over to governor performance overclock the phone and be happy with that...That is why it is called performance after all:D

Ps..Porn on a 50inch Oled tv when that comes out and it will be in 3D to ohhh baby:D:o
[Galaxy S II Original Android Development] alferret:
Only undervolted by 25 on all frequencies but I did have a screen off profile set to 100. Removed the screen off profile & see if it happens again :)

Thanks for the input.
[Galaxy S II Original Android Development] omniwolf:
BLN

gokhan now that you're "running out of things to do" :P i thought i might ask..

does the kernel have access to how the deep sleep functions? I was wondering if you might be able to "fix" the BLN wakelock? IIRC the original SGS had BLN but it didn't cause a wakelock, so i guess it's physically possible..?

not sure if deepsleep is hardcoded into the motherboard or CPU or something, but i thought it might be worth asking :)

Thanks for your great work so far!
[Galaxy S II Original Android Development] CamoGeko:
That was almost definitely the reason. 100Mhz screen-off is outrageously low lol, what on earth possessed you to do that?

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Enterprise.
[Galaxy S II Original Android Development] alferret:
God knows lol! Lower=Better ;)
[Galaxy S II Original Android Development] hallydamaster:
I flashed the 2.6.8 yesterday over .5, and for some reason it reset my 3G watchdog counter. It doesn't really matter as I have a 3 GB monthly plan, and never uses all of it! Maybe someone could explain how it happened, or have an idea?
[Galaxy S II Original Android Development] :
Just some screenshots from using current version of siyah. Everything sync nothing disabled. Could not be more happier. Will post more screenshots when battery nearly dies down. Best kernel in my opinion
[Galaxy S II Original Android Development] incubus_fr:
You are wrong.

Nenamark revealed a bug in the last Siyah, and Antutu pointed out some other issues in the past.

Used for a quick check on a new kernel release they can prove useful.

Anyway, some like porn movies, some other like benchmarking. No need to judge and to be rude about that.
[Galaxy S II Original Android Development] :
Please by all means give me an example of why benchmarks are useful? And apologies if the way i put my previous post offended you but lets face it. If we was to have a poll to see who agrees if benchmarks are pointless and those who agree they are useful i know what the poll would say at the end of the day;)

But hey this is xda this is a community everyone is allowed to their opinions.

But again apologies if my previous post upset you but let's face it benchmarks does not really mean anything if your phone runs smooth as it is
[Galaxy S II Original Android Development] CamoGeko:
Did you wipe caches before flashing Siyah?
[Galaxy S II Original Android Development] ziroxs:
It was only a question that someone can confirm the write speed data values. Thx

I didnt say that i am not happy with the last 2 kernel versions ;)
[Galaxy S II Original Android Development] karlesg:
That's the reason I don't use bln. Wakelock. To my mind this is a "no-go" implementation. And to set a short time out period, this isn't a good solution either. BLN should be enabled for as long as needed. By setting a short time out period, it seriously loses its usability.

But BLN is a very very useful thing to have. I think quite a few have tried a non-wakelock implementation but with no luck so far. And as I see they have quit the efforts. There is nothing new for the SGS2-BLN project for quite some time now. Maybe a non-wakelock implementation isn't possible by any mean, I don't know...

But from all the other to-do things that I've read, this would be THE top to-do thing, if it's actually possible. I think a non-wakelock BLN would be a real evolution in the usability of our phone.
[Galaxy S II Original Android Development] marsexpress:
Hi. I had been using 2.6.7 since a few hours after it was released and had zero issues. I flashed 2.6.8 about 5 hours ago and have just had a sleep of death.

Apologies but I am not near a computer and I am unable to provide any debugging information.

I'm going to flash back to 2.6.7 right now.

For the record I also had SOD with 2.6.6.

Cheers.
[Galaxy S II Original Android Development] pikachu01:
Have you tried QuickPic? Does it still hang if you still QuickPic?
[Galaxy S II Original Android Development] CamoGeko:
Probably due to your SetCPU profile or ultra low voltage settings. :)
[Galaxy S II Original Android Development] pikachu01:
You having no SODs in 2.6.7 could be a coincidence. You might have a UV profile that is too aggressive that could trigger SODs some of the time, and you were lucky enough not to have it in 2.6.7. Try disabling UV and see if you still got SOD, then try not to UV too aggressively the next time around :)
[Galaxy S II Original Android Development] stylez:
I'm actually surprised BLN has been such an under looked thing in the SGSII community only thing to stop most users is the poor implementation to which causes wakelocks and high consumption of battery regardless of waklelocks, same as what call recorder kernel intergration did to HTC Devices in the early days.

A way to know you have a messages but without the issues... Visually would be awesome as often missing messages until screen on.

gokhan,

Well aware you busy with work/edu but when you back on the roll, would be well sweet to have BLN support by that i mean gok tweeks :D
[Galaxy S II Original Android Development] rizcom:
hi pikachu01 i am using 2.6.7 rock solid now but, Thanks :)
[Galaxy S II Original Android Development] pikachu01:
How about 2.6.8?
[Galaxy S II Original Android Development] tolis626:
Well,the reasons this many people say that benchmarks are **** are very specific.Let me explain:

-Most people trust benchmarks such as Quadrant.Quadrant was,is and will be bull****.It hasn't been updated in ages and most of today's devices push its tests to the limit,hence the results are mostly based on I/O scores,while Quadrant's I/O test can be cheated in a bazillion ways.

-It is dumb to compare different phones' capabilities and performance through benchmarks,especially synthetic ones,as results are affected by a great many things.Specific benchmarks like Linpack for CPU and Nenamark for GPU are quite accurate in fact and can be trusted to measure a device's raw power compared to another device.

-Benchmarks,when performed on the same device with similar configurations and only some changes can reveal performance problems introduced by these changes.And problems don't mean 100 points lower score in Antutu,but a 1000 points in Antutu and big decreases in Linpack,Nenamark,you name it.

Bottom line is that,if the concept of benchmarks wasn't as widely adopted by idiots and/or people who don't know what they do but rather choose to watch numbers,they would be a great tool for people who like tweaking their devices.But we all know that,at least to this date,this doesn't happen.Let's hope though...
[Galaxy S II Original Android Development] rajarshi10:
2.6.8 behaves weirdly at times. Don't know whats wrong or the battery drain bug is back. 2.6.7 is still rock solid. Downgraded from 2.6.8. Happy with the prev version :)
[Galaxy S II Original Android Development] stevehkim:
for those that were getting low sd card read/writes. it is due to this.

set readahead cache on sdcard to 256KB (was 1024).

i changed mine back to 2048kb and im getting 50mb read/write again.
[Galaxy S II Original Android Development] :
Nicely put.;)
[Galaxy S II Original Android Development] chadouming:
The real problem with comparing phone with benchmark, imho, is that you compare the highest performance that the phone can push. However, as normal user we dont use the phone to those limits all the times. Ok, my phone can push 8k quadrant score, ok my phone can make 8.2k antutu score, so what ? Does it mean it will not lag while opening the drawer ? No. As I said, those test are done with the phone on the edge of his limits. Pointless to say that it will also not represent the real battery life which is more important than 8k antutu score. Keep the the file integrity is also more important than having 50 mbps I/O. Have you ever tried to run a benchmark stuck on bootloop ? The important thing with a kernel and/or a rom, is how it feels. Does it lag, does it waist battery, does everything work, etc ? Try to find this out before trying to reach the limits of his performance. Every phone is different.
[Galaxy S II Original Android Development] barondebxl:
My battery seems to drain a lot faster with 2.6.8
[Galaxy S II Original Android Development] incubus_fr:
No problem you did not upset me.

I use benchmarks, as tolis said, on the same configuration on a new kernel release or to test some setup changes. I don't really care about big numbers.

Benchmarks, in the simplest form, are devs tools. They are used to see if a code optimization is real.

Without benchmarking you are subject to placebo effect.

And yes, quadrant is a joke and nobody should use it ;)
[Galaxy S II Original Android Development] droidphile:
Only "benchmarking" i do is run linpack single thread and multi-thread runs; that too only once, immediately after flashing a new version. Because i wanna make sure that all the tweaks in my scripts are working fine: like thresholds, sampling and cut-off frequency for second core, etc etc. Even linpack might not be very accurate, but atleast the difference between single and multi thread scores tells me something.

I would say, testing kernel performance should not be through benchmarking tools, but using real time 'benchmarking' usage. For ex: Play HD videos, play HD games, use our navigation app for some time over 3g, etc. Using Maps or any other nav apps could tell a lot because it almost uses everything: CPU, GPU, gps, data connection, interaction with cell towers,... So the stability of gpu uv/uc/oc, cpu uv/oc/uc, modified bus frequencies etc can be easily understood.

Watch these kinda real usage scenario closely and if we find problems, tweak our scripts and other settings like uv, oc, uc, blah blah until it's solved. If we completely fail to solve it, then, Only then report to Gokhan; with kmsg and logcat.
[Galaxy S II Original Android Development] hallydamaster:
I did not! Do you think that would have made the difference? :)

Btw, .8 seems to be rock solid for my use, and definitely no battery drain!
[Galaxy S II Original Android Development] veyka:
I wholeheartedly agree with this, a no wakelock BLN implementation would be great, if the hardware can do it.
[Galaxy S II Original Android Development] marsexpress:
It's a fair point you make, although my UV settings are not aggressive I accept it is a possibility. Seems fairly consistent to me though, 2.6.6 I had multiple SODs in the space of a couple of days, even after returning to stock voltages.

I'm not the only user reporting SODs with this version. I know others are saying it's all good but this version is too young to say that with authority, plus not all issues affect everyone. Personally I have never had any issues with any Siyah kernel besides SODs! Great kernel, I switched from speedmod to this. Speedmod was erratic on the battery life front and worse gave reasonably regular.... Sleeps of death...

Cheers.
[Galaxy S II Original Android Development] pikachu01:
http://xdaforums.com/showthread.php?t=1032317

Benchmark does a contiguous read, hence higher readahead will yield higher benchmark scores. Real life isn't like that. Reads are spurious.

---------- Post added at 02:10 AM ---------- Previous post was at 02:08 AM ----------

True. Hence, more experimentation usually leads to the answer. Try not UVing and see if SODs are still apparent :)
[Galaxy S II Original Android Development] stevehkim:
pika yes i understand what you are saying. but adjusting my values to 2048kb gives me decent read/writes and is fairly consistent. to each their own i guess.

My remix:

MIUI rommed, Siyah kernel synthetics, V6 supercharged, struck by a bolt of Thunder!

SGS2 I777
[Galaxy S II Original Android Development] cmd512:
For me, v2.6.8 is definitely going to deep sleep more frequently than v2.6.7, resulting in awesome standby battery drain. Battery drain during actual usage seems a bit higher, but will need more time to test.
[Galaxy S II Original Android Development] legendasboy:
Well had another sod today, returning to stock voltages, if that doesn't solve it, I'll have to return to 2.6.7

Sent from my Galaxy SII using Taptalk