yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] d3l1:
is nandroid backup of the second rom anywhere in your to-do list, gokhan?
[Galaxy S II Original Android Development] gokhanmoral:
yes. I have just finished with 3.2.5 and want to test it at least for a day.

if I have time meanwhile I will fix that as well.

I will be very busy this week, so no promises.
[Galaxy S II Original Android Development] d3l1:
great news! no need to rush, was just a question out of curiosity :)
[Galaxy S II Original Android Development] djdeeles:
I've too much battery drain when bln active phone doesnt sleep stays awake is this problem or its bln's behavior ?
[Galaxy S II Original Android Development] coloxim:
Is the bln!!!

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] Cyceroxxx:
I did that before but didn't work. Anyways I just figured out what happened... There were ~1,8 GB file in lost.dir that happened to be remainings of my failed "wipe 2ndROM data/cache"

Problem solved :)
[Galaxy S II Original Android Development] maczaros:
Kernel Panic

I'v got next kernel panic.

I'm on 3.2.4 and this is also wifi related - last_kmsg in attachment.
[Galaxy S II Original Android Development] Jigen90:
Hi Gokhanmoral, probably you know that btw I read here http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/ about a big kernel bug in leaked samsung kernels, it could cause brick.

I know you build from Samsung source, I'm not an expert of kernel..but is Siyah bug-free? I mean, is Siyah NOT related to that issue? Thank u!
[Galaxy S II Original Android Development] androidkid311:
He fixed the bricking issues agggggges ago! Its fine! Flash away! :D.
[Galaxy S II Original Android Development] Visentinel:
Pls pls gokhan release the new krnl we know the risks no need to test anymore :D
[Galaxy S II Original Android Development] Phistachio:
Gokhan, could you tell me if you're planning to switch from GCC linaro 4.3 to 4.7?
[Galaxy S II Original Android Development] paryav:
I am waiting too. :D
[Galaxy S II Original Android Development] gokhanmoral:
If it has an advantage i will. But i could not find any measurable advantage. Is there any benchmark result that you can point me for the advantages?

I am now using the one that Samsung and CM9 use which is 4.4.3
[Galaxy S II Original Android Development] sinancetinkaya:
Your issue is not kernel related. May be permissions but not kernel.

Try to install a stock alike rom as 2nd rom and try to log in again.

I use 2 roms, I can log in to google play in both roms without any problem.

Can you please use this thread for such problems?
[Galaxy S II Original Android Development] rlorange:
GM do you expect that the the changes made to BLN will fix the slow-down bug.

Rephrased: Do you think what you've found is the the only cause?
[Galaxy S II Original Android Development] crachel:
*MOD POST*

I've subscribed to this thread to keep a closer watch as we are getting lots and lots of reports.

So, if you notice your post mysteriously disappears, try asking/posting it again in the Discussion thread.

http://xdaforums.com/showthread.php?t=1658647

Thanks
[Galaxy S II Original Android Development] gokhanmoral:
there is no way of being so sure about that being the only cause.

but I am sure that it is one of the main cause if it is not the only cause...

and I hope I could manage to guard all those turning on/off while touchkey regulator is not active.

I also remember that I had exactly the same problem when I was trying to make BLNWW work in gingerbread days.

if you have already downloaded the repo and willing to reproduce that slowmotion bug easily, just comment out wake_lock related parts from cypress and try to do something related with BLN while the screen is off.

it can happen even if you don't use BLN because we have some other features related with leds and that problem happens when you enter deep sleep with regulators enabled or modify led status when touch regulators are not enabled.
[Galaxy S II Original Android Development] salvopetrucci:
please gokhan don't remove gpu undervolting in 3.2.5...

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] gokhanmoral:
gpu undervolting is not removed.

it will not be undervolted by default.

you can always undervolt and underclock it using ExTweaks.

I have just removed undervolted defaults and used voltages which are closer to stock voltages.
[Galaxy S II Original Android Development] astrogambit78:
Mr. Gokhan

is it necessary that after installing Siyah while still in CWM, i go to Kernel specific settings and change it?

i used to set 'battery mode'.
[Galaxy S II Original Android Development] gokhanmoral:
no, but I think I can keep /data/.siyah/.active.profile file so that you won't need to set battery profile again, but your profile modifications will be overwritten after installing a new kernel.

EDIT: done
[Galaxy S II Original Android Development] Tungstwenty:
Got 2 kernel panics this morning, the last of which logged the same stuff in last_kmsg - NULL pointer deference, process "wpa_supplicant", same PC, LR, backtrace functions and offsets.

This happened with wifi turned on and while driving to work, it just rebooted twice in a 30m period. After that I turned off wifi and haven't experienced these symptoms since.
[Galaxy S II Original Android Development] gokhanmoral:
I have updated wifi drivers once again. wifi related problems will decrease dramatically with the additional checks in new wifi driver.
[Galaxy S II Original Android Development] gokhanmoral:
there will be a new binary in 3.2.5, which is very useful I think...

it is "kmemhelper"

we have /dev/kmem interface enabled to support some apps, such as voodoo louder.

I decided to implement a script to make some simple modifications without modifying the kernel code, such as enabling/disabling some features, change bus voltages or even frequencies just like tegrak's application...

of course it will require some knowledge... but here are some examples:

it takes at least 3 arguments: variable name and type

such as:

kmemhelper -n smooth_level -t int

and then it will echo smooth_level back.

if you provide a value to the same command such as

kmemhelper -n smooth_level -t int 4

it will set smooth scaling level to L4, which is 1200MHz.

this is already added to ExTweaks using the same command as above.

another interesting example is this:

LVL=`cat /proc/kallsyms|grep " level\."|awk '{print $3}'`;kmemhelper -n $LVL -t int

this one is a bit more tricky.. but we have a static variable named "level" and it has a suffix because there are some more variables named level in the kernel.

it will show you the touch locking freq level, 11 in siyahkernel, which is the level of 500MHz.

and if you set it using the following command, it will become 400:

LVL=`cat /proc/kallsyms|grep " level\."|awk '{print $3}'`;kmemhelper -n $LVL -t int 12

you can also set touch sensitivity values using the same method, as in the following script (but it will only work in siyahkernel as it needed some tiny modifications on the kernel part):

# offset 59: MXT224_THRESHOLD_BATT_INIT
kmemhelper -n mxt224_data -t char -o 59 50
# offset 60: MXT224_THRESHOLD_CHRG
kmemhelper -n mxt224_data -t char -o 60 55
# offset 61: MXT224_NOISE_THRESHOLD_BATT
kmemhelper -n mxt224_data -t char -o 61 30
# offset 62: MXT224_NOISE_THRESHOLD_CHRG
kmemhelper -n mxt224_data -t char -o 62 40
# offset 63: MXT224_MOVFILTER_BATT
kmemhelper -n mxt224_data -t char -o 63 11
# offset 64: MXT224_MOVFILTER_CHRG
kmemhelper -n mxt224_data -t char -o 64 46
# offset 67: MXT224E_THRESHOLD_BATT
kmemhelper -n mxt224_data -t char -o 67 50
# offset 77: MXT224E_MOVFILTER_BATT
kmemhelper -n mxt224_data -t char -o 77 46

I wish I could implement it using a shell script which will make it easier to understand and also modify... but for now, it is binary. I will publish the source after making some indentations and cleaning. although it is very trivial it will be a simple example for kmem interface...

until droidphile writes a decent post about it, I hope this will be enough :)
[Galaxy S II Original Android Development] kehinde:
You are right on both accounts. i eventually realise the problem came from google. After waiting for another 24hrs it's all cleared up by itself. Now i can log in into both gtalk and play store with both my wifi and cellular network. Before it was sporadically only thru the cellular network.

i guess was i was getting frustrated b4 posting here. won't happen next time.

To the guy/s that made this siyah kernel possible, especially for you Gokhanmoral, i say a gazillions thanks.

Halycon
[Galaxy S II Original Android Development] Napalm Candy:
Possibly discussed before but...

With default settings of Pegasusq CPU Spy reveal that CPU is working at 1200Mhz when you are doing "nothing" (browsing web for example), so I see that are in deep sleep or 1200Mhz, and a very few seconds on interval freqs after hours of use.

Also... lulzactive give me random big slow downs (freezes), I never activated or use BLN, I'm in default profile
[Galaxy S II Original Android Development] Phistachio:
I have tried to find, but was unable to. The 4.7 release should bring a few optimizations according to my research, so I'd guess that it'd be a good idea to update to the newest?
[Galaxy S II Original Android Development] confusedmuse:
For me it uses more frequenzies... but 500MHz is used too much.
[Galaxy S II Original Android Development] gokhanmoral:
v3.2.5 is released.

http://www.gokhanmoral.com/
[Galaxy S II Original Android Development] Phistachio:
Nice!

I only have one more question, are you thinking of including DSPManager support?

Also, 3.4 kernel is officially released : http://www.kernel.org/
[Galaxy S II Original Android Development] confusedmuse:
Immediately impressed.

Great work Gökhan!

Thanks.

Edit: picture wasn't applied for some reason...
[Galaxy S II Original Android Development] marcosxd:
Downloading from gm site is painfully slow atm... would anyone upload the newest using mediafire or dropbox? Thanks
[Galaxy S II Original Android Development] kehinde:
While i await this, i will like to ask is it possible/ok to do it manually? i mean boot into first ROM, do a Nandroid backup, THEN reboot into 2ND ROM, and do ANOTHER Nandroid backup. will this work??(its what i was planning to do b4 seeing ur post)
[Galaxy S II Original Android Development] MaKTaiL:
Ice Cream Sandwich does not support it, only latest 3.0.X.X releases.

---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------

It's fast here. It's only 7mb, you can wait a couple of minutes longer. Don't rush. :)
[Galaxy S II Original Android Development] marcosxd:
I have downloaded 23% in 30 mins :) please reupload :(

NVM. Gokhan mirrored himself :)
[Galaxy S II Original Android Development] gokhanmoral:
look in the other thread for a mirror.
[Galaxy S II Original Android Development] grozni:
Same here,
[Galaxy S II Original Android Development] razor 116:
I'm using 209dpi with B6 on latest HyDrOG3N ROM, scrolling is fine.
[Galaxy S II Original Android Development] troffers:
That's really odd. Seems to be random.

Don't think it's to do with the bootloader - I'm using the latest CM9 nightly just fine. Haven't tried on AOKP yet as I can't backup that ROM - CWM ain't working with that one :rolleyes:
[Galaxy S II Original Android Development] itsme12345:
gokahn, b6 seems to be best working on latest lp2, but i found one other issue after installing this b6 kernel, i usually use script to get things backed up and this time universal script got failed due to memory error, so i had to go back to b5 and run the script and it worked, so there seems to be some issue in memory allotment in recovery. below is the error message i could not get the scrn shot.

Free Ram available : 0KB

Free Ram Required : 190852kb

Error There not enough Ram to work!

Exit This zip is too big!
[Galaxy S II Original Android Development] sam razzy:
This is the second time I'm asking but I dint find my answer...

Is this working on MIUI v4 Samsung ics base?
[Galaxy S II Original Android Development] MistahBungle:
Because this question has been answered 18,742 times in this thread over the past week.

No.
[Galaxy S II Original Android Development] jim-bo:
That question has been asked and answered many times.

This kernel works on ROMs based on Samsung LPQ or later, or on CM9 320 or later, not on anything else.

MIUI is based on a leaked ICS beta, older than LPQ, so until the update their base, it will not work.
[Galaxy S II Original Android Development] razor 116:
It should work fine on that ROM
[Galaxy S II Original Android Development] MistahBungle:
*coughs* Ahem :rolleyes:
[Galaxy S II Original Android Development] markjh:
MIUI 2.3.23 is based on LPQ ;-)

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II Original Android Development] razor 116:
LOL thought I'd give him the answer he wanted, clearly he was waiting for it.
[Galaxy S II Original Android Development] MistahBungle:
Haha ;) Nice psych.

---------- Post added at 03:28 AM ---------- Previous post was at 03:27 AM ----------

Looks like someone running 2.3.23 is going to be a guinea pig then, doesn't it ? I know who it won't be tho (Gokhan).
[Galaxy S II Original Android Development] Dirk2007:
Works fine here (B6a on ICS 2.1). Did you deselect USB debugging before connecting?
[Galaxy S II Original Android Development] shanume:
Hi Gokhan,

after I flash this b6 I just found out in about phone they still show in 3.0b5? if there anyone else has the same as me?
[Galaxy S II Original Android Development] PedroMRP:
gokhanmoral will you update the kernel to 3.0.25?

I notice that beta6 don't have last_kmsg enabled.
[Galaxy S II Original Android Development] danielsf:
Hi, I have a problem with beta 6, I use set cpu as i like to have a profile where when my screen is on my min frequency is 500mhhz (I find scrolling a lot smoother at 500mhz min), and when screen is off it is 200mhz and it worked like a charm on stock cm9. But with your kernel I get SOD, as in the second my screen turns off I have to pull the battery to start it again, or press the power button for a long time to get it started. Please, would you see if this is fixable, as i really like set cpu, with all the profiles :) Thanks for this kernel :)
[Galaxy S II Original Android Development] shanume:
setcpu is very bugged in ICS so there better to wait for a new update from setcpu instead.
[Galaxy S II Original Android Development] pro.aggro:
Yes i did...

I plug it in and the usb massstorage-message opens. I click on "connect" and the then it unmounts the sd cards.
[Galaxy S II Original Android Development] danielsf:
Just out of curiosity, what is your lowest stable voltage you can run 1.6ghz at on your phone? Just to compare :)

I run 1.6ghz at 1350mV, when I try 1325mV it freezes after about 3-4 minuets of intensive gaming. :)
[Galaxy S II Original Android Development] desean:
Gokhanmoral, a (bug???) report with the USB storage.

Under MTP mode, everything seems alright but if you try to transfer an unsupported file (a mkv file in my testing), my explorer will crash (I am running on Win7 x64). Normally under MTP it will ask you to confirm if you wish to copy/move the file as the phone doesn't support the file that you are transferring.

Under USB mass storage mode, pressing "Turn on USB storage" will simply unmount the internal storage and external sdcard. It will not be available in Explorer as a mounted drive (as it normally does) and in the notification bar it will indicate the sdcard is safe for removal (which normally isn't shown).

on a side note, I personally prefer USB mass storage mode over MTP because it is faster (noticeable on large files) and it does not ask me questions on unsupported files (like the mkv which is playable by MX Video player but not supported by the phone "out of the box") :D

... end of report :p

edit: oh btw this is for beta6 on WanamLite ICS 9.5 LP7 and tried with USB debugging enabled and disabled (although it shouldn't matter)
[Galaxy S II Original Android Development] AndreiLux:
I'm of the opinion that we need to remove smooth scaling for pegasus; reason we had smooth scaling in gingerbread was of course ondemand scaling to max frequency to often, this continued on in ICS but there ondemand gained freq_step functionality which does what smooth scaling is supposed to. It was still ok since the default value was 100 so it wasn't being used. But now pegasus has a default of 40 so what smooth scaling does now is only to interfere with the governor logic.I don't see the point of having two mechanisms trying to do the same thing and one hampering the other in doing so.
[Galaxy S II Original Android Development] zaphod777:
WIFI Driver seams pretty awesome!

Further testing is required but it feels a lot faster :D

Test Date: May 22, 2012 9:29:03 am

Connection Type: Wifi

Server: Tokyo

Download: 18975 kbps

Upload: 24714 kbps

Ping: 15 ms
[Galaxy S II Original Android Development] mekhonte:
Hey gokhan

For mine after flasHing 3.2.5 wifi bricks!

It does turn on but won't see any AP. I went back to 3.2.4 and wifi works again. It should be related to new wifi driver.

I dunno which log i can produce to solve the issue.

AOKP ROM
[Galaxy S II Original Android Development] shawnaye:
Yep GM, wifi driver on 3.2.5 taking too long to connect.

3.2.3 was the last i was on and it was working fine.

Edit: ok, it's working fine after a reboot now, like 3-5 secs to connect.
[Galaxy S II Original Android Development] ggogolewski:
WiFi works without problems :-) 3 sec to be connected...

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[Galaxy S II Original Android Development] kilian7th:
Hi Gokhan, wifi driver give a poor signal and take long to have signal.

Battery profile make that my original miui rom freezes after starting and many problem of sd mount, in musik.apk. it seems now to see three times all songs but just one is ok ... :-(

Default profile seems ok but always the wifi problem and the sd card mount bug...

Thanks for all ...:)
[Galaxy S II Original Android Development] pilgrim011:
Wifi works just fine here.
[Galaxy S II Original Android Development] gokhanmoral:
aBYssplug will never be added because I have added hotplug governor, which is the original and true name of it.

I inspected aBYsplug governor code and found it to be exactly the same with original hotplug with one threshold setting exception and not-so-necessary workqueue usage during hotplug which is very doubtful that it is developed by angelom.

if you use hotplug governor with your AbySSPLUG governor settings you will have the same experience and maybe better. because abysplug governor was not disabling the other hotplugging mechanisms.. I hope Angelom will also fix the governor name while he is fixing the problem of having two independent hotplug logic enabled.
[Galaxy S II Original Android Development] pikachu01:
Got a sudden reboot (my guess is a zero-timer kernel panic?) after opening Tapatalk.

Last_kmsg attached. Let me know which part is the culprit, and I can probably analyze this better in the future :)

Thanks!
[Galaxy S II Original Android Development] AU_IT01:
Weatherzone+ is crashing with v3.2.5

Gokhan, since I flashed v3.2.5, my Weatherzone+ is crashing each time I start it.

If I flash the older v3.2.4, all is ok again...

Flashed v3.2.5 again, Weatherzone+ crashes again.

I deleted the cache, it does not help.

Is this related to your kernel?
[Galaxy S II Original Android Development] gokhanmoral:
the board is acting weird.. attachments are not working. can you send me a dropbox link?
[Galaxy S II Original Android Development] pikachu01:
Here it is:

http://db.tt/NvRtXypy
[Galaxy S II Original Android Development] pikachu01:
As per reported on the general thread, I found some of my apps force closing as well after flashing 3.2.5. Dalvik Cache/Cache wipe didn't solve it. A factory reset/restore from Titanium Backup solved it somewhat, though the Setup Wizard did FC when first startup was done. After that no problems with FCs except for a crash from Tapatalk (log uploaded in a post before this).
[Galaxy S II Original Android Development] Markox89:
After flashing 3.2.5 TWLauncher can't stop crashing, I've also flashed back 3.2.3 and 3.2.4 but didn't solved. Wiped cache and dalvik cache with no results. Factory reset can't be the solution :(

EDIT: Thank you for 3.2.5.1 but for me the bug is still here.

EDIT2: I've read the GM's post in the general thread, thank you GM :)
[Galaxy S II Original Android Development] pikachu01:
If flashing back didn't solve it, you have to wipe the data in twlauncher (probably twlauncher got corrupted). Try going to Titanium Backup - wipe data or in System - Apps - Wipe Data
[Galaxy S II Original Android Development] gokhanmoral:
did you try clearing data of twlauncher or restoring an older data over?

I suspect that a crash (probably because of forced gpu rendering) result its settings to be corrupted and the later forcecloses are related with that settings corruption.

clearing it's data should fix it.

EDIT: I was slow :)
[Galaxy S II Original Android Development] Markox89:
As said in the last edit of my previous post I've read your post in the general thread suggesting to turn off forced gpu rendering in system->developer options, and it fixed, once again thank you, and not only for this fix ;)
[Galaxy S II Original Android Development] gokhanmoral:
did disabling forced gpu rendering fix the problem?

EDIT: damn.. I was slow again :)

ok.. nice to find another reason of crash.

I didn't have any problem with that option enabled for 2 days but it seems that it is just another benchmark-boosting-but-problem-introducing setting...
[Galaxy S II Original Android Development] rlorange:
I noticed this setting was enabled after flashing 3.2.5... however I've had no FC problems (or problems of any other kind).
[Galaxy S II Original Android Development] kilian7th:
Hi gokhan,

I had to make a wipe factory and everything i was able to,

Came back to 2.3.4, everything was buggy and frozed on both roms ... :(

This is the rule of the game ... :)
[Galaxy S II Original Android Development] pikachu01:
Might be an app specific thing (or a particular app that causes other apps to FC).

You probably have init.d scripts that tweaks voltage that were leftover from the previous flash and it mismatched with the governor (the older pegasusq).

It's 3.2.4 right, not 2.3.4?
[Galaxy S II Original Android Development] SPBoss:
GM just thought i would say thanks for this amazing kernel im currently using 3.2.4 and i have no crash issues with forced gpu rendering. im using chainfire 3d in 32bit mode aswell :)
[Galaxy S II Original Android Development] gokhanmoral:
neither do I... I used my device with that setting for 2 days.

but not all the settings/apps/devices are the same.

I have no luxury of saying "it works on my device" :)
[Galaxy S II Original Android Development] Ankit Tulsian:
@Gokhan:Just reporting that there is no hot plug governor in ex tweaks.I am using NS tools to set it.Hot plug governor is so smooth.

Thanks again for your hard work.
[Galaxy S II Original Android Development] kilian7th:
nothing in init.d, alway remove all files in this folder and reset tweaks profile , wipe cache and dalvik cache before upgrading siyah ...

3.2.4 exactly sorry ...
[Galaxy S II Original Android Development] SPBoss:
i just disabled the second core and clocked down to 600mhz. UV the gpu and cpu.. still runs smooth and my battery life is reaching 8-9 hours screen on time!
[Galaxy S II Original Android Development] coloxim:
GM...

Great kernel really...your are closer to perfect...

Just one think...I've tried simple idle instead lftr+lpa....and the battery in standby seems much better..

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] maczaros:
Kernel Panic

Still having kernel panic (2.3.5) sometimes - and still wifi related

kmsg in attachment.
[Galaxy S II Original Android Development] pilgrim011:
I've had problems with Apex launcher immediately after flashing 3.2.5 (crashing, force closing), but after I disabled "force GPU rendering" everything is fine.:)