yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Frozenthunder:
What happened when you wiped the cache and dalvik cache? Did your system also boot like it would if you didn't wipe the cache like in my case? Or did the "optimizing applications" message appear and it took some time (like it normally should)?

I also tried using my 2nd ROM with the newest kernel and it just worked fine (Resurrection Remix ICS 2.0).

If anyone is having the same problem then just reflash v. 3.2.5.2 that's the most recent version which works tried SiyahKernel v3.2.7.2 and had the same problems. Not sure if SiyahKernel v3.2.6.4 works though.

The funny thing is that I used 3.2.7.2 for days and it worked fine all the time. But when going back from newest to 3.2.7.2 the problem remains.
[Galaxy S II Original Android Development] tghandour:
I had the same thing this morning, I reset extweaks, flashed Siyah 3.2.8.2, wiped cache and dalvick and restarted . And Optimizing applications message didn't appear and the phone rebooted as if I didn't wipe both caches although with some delay after the vibration till I got my lock screen.

Else everything was working fine without any freezes or FCs. I am running RR 2.1.
[Galaxy S II Original Android Development] Tungstwenty:
I think the data filesystem (/dev/block/mmcblk0p10) end up becoming corrupt perhaps due to 3.2.8.2(?), and whatever kernel you use afterwards won't fix that.

The secondary rom, whose data partition is a file in the sdcard (/dev/block/mmcblk0p11) is independent of the main data partition and the 2nd ROM can therefore be immune to these problems - unless it gets corrupted as well, but that also won't affect the primary one.

About what happened after wiping dalvik-cache, I really don't remember the 1st boot but I had situations when it got stuck on the boot animation, some others where it generated a bootloop, others where it booted but then gave all the FCs (due to /data being ro).
[Galaxy S II Original Android Development] Frozenthunder:
How can I find out if my data filesystem is corrupted? And how can we fix our broken filesystems? I'm on a stock Rom and setting everything back up would be alot of effort. I got a nandroid backup though.

Also, I just tried to update BusyBox again and it was stuck again at 58%. Now Google play is broken again and it gets force closed all the time. Looks like something really is messed up.

Edit: Also superuser is getting force closed when I start ExTweaks. Got the same problems as before now.

Propably going to restore a nandroid backup. Did you do a wipe before you restored it or anything? Will the old dalvik cache and cache also be restored or do I have to wipe it (because that apperently doesn't work propably even with 3.2.5.2)?

Also, can I do a nandroid backup of my current system which apperently has a broken file system or may this cause big problems (I heard of people bricking their phone just by doing a backup)?
[Galaxy S II Original Android Development] Sm0L:
I really like Siyah Kernal and Gokhan job is wonderfull but these kinds of updates:

should be made in a minor version and not a major version like 3.2.8 or maybe gokhan should inform which version is stable or not, at this rate of updates i find very difficult to have a stable version.

Bottom line, i'm glad i didn't install the latest v3.2.8
[Galaxy S II Original Android Development] Tungstwenty:
Wipe dalvik-cache should work fine with 3.2.8 and below, at least I never had any issues before and I got back on my feet using 3.2.8.

I restored a nandroid backup, but only the /data partition and after that wiped cache again (already running a non-3.2.8.2 kernel) and wiped dalvik-cache, which is inside /data.

If you have a usable nandroid backup, that's the best way for you to solve this. I don't know what fsck-like tools are there under /system so I didn't bother trying to repair the data, as it's quite possible that some of the information is fubar anyway.
[Galaxy S II Original Android Development] Holgott:
I just flashed siyah 3.2.8 yesterday and i was happy... No fcs or smthg. I just read today that a newer Version is available and i flashed 3.2.8.2... After that the fcs began. Tryed flashing 3.2.8 again, but i endet in a bootloop. Thanks god i did a nandroid before flashing siyah :-(
[Galaxy S II Original Android Development] tghandour:
GM I have an observation concerning Siyah with Accelerometer, as the picture shows under AOS the Accelerometer is being used for several hours although I am not using display rotation at all (itvos turned off) !!! This is also observed via Cool Tool graph which usually shows 25-35% CPU usage while idle..

Same behavior was observed on Fluxi kernel xx.01. The only kernel which showed few minutes of Accelerometer usage was Abyss 1.2U (sorry for the comparison). This behavior was noticed on several AOKP ROMs like Omega and Foxhound so I believe it is kernel related and unfortunately leads to high AOS activity and battery drain.

Any explanation for that?
[Galaxy S II Original Android Development] JayXL14:
Is SiyahKernel v3.2.8.2 working now? Because I had to factory reset at 3.2.8 and had some more problems but not sure if it is v3.2.8.2 related (which I flashed after), or something else.
[Galaxy S II Original Android Development] chris2busy:
Guys i have tinkered a bit with gpu clock/voltages and i forgot the stock values for all 3 steps..could any1 please provede them? (e.g step1: x Mhz/x Mv, step 2 : , step3 : )

Also if any1 has any recommended relatively safe values for GPU UV/UC i would be glad to use them :)
[Galaxy S II Original Android Development] tghandour:
Just reboot CWM and select kernel options and select set battery profile ( or Default profile to set everything to default) which sets the frequencies to 44/133/267 with 900/950/100 mV. I always do that and change 44 to 67 MHz and sets the UV values to 850/900/950 mV and never had problems.
[Galaxy S II Original Android Development] sefrcoko:
On 3.2.8.2 and no problems at all. Just flashed latest Ultimate Cleaning Script and then latest Siyah. Was on 3.2.8 before.
[Galaxy S II Original Android Development] JayXL14:
^ http://xdaforums.com/showthread.php?t=1363738

Is this what you were referring to? I am gonna use Odin to try and restart and my phone and all that. Do you use that BEFORE Siyah?
[Galaxy S II Original Android Development] nitinvaid:
I don't want to use mtp.(very slow speed)...

My device always hangs while in USB mass storage. Transfering data

Flashed back to cm stock kernel ans no problems
[Galaxy S II Original Android Development] gokhanmoral:
I have just arrived home.

I am now removing 3.2.8 and compiling a new 3.3, which will be very close to cm9 kernel which is running stable enough for everybody.

there will be no experimental or n7000 based changes.

there will only be i9300 wifi driver, and I will also make some changes in that so that it will use country code lookup from platform specific parts.. that will give you previous signal levels.

then I will start working on i9300 and will be away from this section for a while.
[Galaxy S II Original Android Development] myakove:
same here and I notice that /data mounted as read only and that way all the fc.

/dev/block/mmcblk0p10 on /data type ext4 (ro,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc).
[Galaxy S II Original Android Development] gokhanmoral:
v3.3 is up.

I hope it will make you and my wife happy, or at least not unhappy.

it will wipe your extweak settings after you flash.
[Galaxy S II Original Android Development] crachel:
Another 3+ pages of off topic posts deleted today. I'm sorry for yet another message from me in here but please:

Discussion/questions go here

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

If you have a log or you have other technical expertise to contribute such as code, that goes in this thread.

Thanks
[Galaxy S II Original Android Development] Redsoldier:
I have undated to 3.3.1 this morning and i have had about three random reboots. After the first i did a extweaks reset and removed undervolting of both the cpu and gpu to see if that helped but reboots persisted so i have attached the last_kmsg to see if it is of use to someone to look into the problem. Cheers and sorry if this should be in discussion thread but i assumed it would be best posted here.
[Galaxy S II Original Android Development] voku1987:
boot in recovery, try "adb shell" and use ->

e2fsck -y /dev/block/mmcblk0p10;
[Galaxy S II Original Android Development] Many40:
Sorry for that, we have to follow XDA forum rules. It's not the topic for DEV tread. Use the link above.
[Galaxy S II Original Android Development] Don MC:
http://xdaforums.com/showpost.php?p=27000811&postcount=1289
[Galaxy S II Original Android Development] t00dy:
Hard Brick on SiyahKernel v3.2.5.2

I have a hard-bricked international SGS2 i9100 (stock ICS ROM: I9100XWLPD, upgraded through Kies from GB: I9100XWLA4. I installed SiyahKernel v3.2.5.2 due to the Wifi connection error, which was present in the stock and stock CF rooted kernel.

I loved the dual-boot option, and i mainly used it to test custom ROMs, before really upgrading to it (CM9 nightlies, MIUI v4, HydrogenICS, Ressurection). 1st ROM was always stock LPD. I flashed 2nd ROM through CWM. First I wiped the partition and then installed the 2nd ROM via zip from external card. When I changed from CM9 to MIUI I copied the cache.img and data.img files from /.secondrom folder (while I was in 1st stock ROM) on internal memory to USB stick via original Samsung USB OTG. Then I rebooted to CWM recovery and wiped data and installed new zip (MIUI ROM). When I wanted to revert do previously installed second ROM, I wiped and installed zip, booted to second ROM, and after rebooting again to 1st stock ROM I copied cache.img and data.img to .secondrom folder to preserve the previous settings. This method was working for me flawlessly numerous times, and I was happy that I can restore the 2nd ROM settings just by copying the 2 files.

The bricking procedure: While in stock ROM I was copying cache.img and data.img from USB stick OTG to /.secondrom folder on internal memory of the phone using X-plore file manager. The screen suddenly went black but the light on USB stick was still on (not blinking). I longpressed on power button and the phone rebooted. I could see the SiyahKernel logo, and nothing more (waited for 5 minutes). I turned off the phone and then back on, but it did not want to turn back on!!! NON of the 3 button combos are working (download or recovery), when i put the phone to charge not even the charging battery icon is showing up! The phone just heats up :confused:

Could my hard brick be due to the /data EMMC lockup/corruption bug?? Is SiyahKernel v3.2.5.2 safe?? in the changelog there is: "Patch the firmware of certain Samsung emmc parts to fix a bug in the wear leveling code"but in one version above (SiyahKernel v3.2.6.4) there is: "UPDATE: 29/5 wifi&mmc related fixes."

Thank you for your help
[Galaxy S II Original Android Development] Tungstwenty:
Not the right thread. But since it's a possible hard-brick ...

Try taking the battery out for a couple of minutes.

Then put it back on.

Press the combo for Download mode (Down + Home + Power) for a few seconds, then let go of Power after a few seconds, and finally let go of the other 2 and press VolUp. Just like you would do on a normal situation, and

even if the screen is always black

.

Open Odin on the PC, make sure you've killed all Kies* processes, and check if when connecting the cable the phone is detected (yellow state).

If so, just flash a new kernel and you should be able to turn off and restart in the CWM mode with the VolUp+Home+Power combo. Or flash a complete ROM and check if that works.

Good luck!
[Galaxy S II Original Android Development] sgunf:
Freedom is wonderful, but crachel is right: it's more easier to find solution to problems reading useful posts only, without reading tons of crap (even if it's funny crap ;) ) and some reporting post occasionally. This is valid for users and overall for Gokhan. He spends a lot of time working on his kernel, it would be better not let him waste his precious time.

It's a bit paradoxical but what I said is valid for me and this current post too:rolleyes:

So shut up sgunf! Over and out...

EDIT: wow! Already 3 posts about what posted bleuxeon in the time I was writing
[Galaxy S II Original Android Development] rauschkugl:
I think you missed something and a mod was definitely needed. You should have the same respect for the mods that you have for gm. This wasn't a development thread anymore. Pages of redundant error reports and same dumb questions again and again.
[Galaxy S II Original Android Development] alcurtis93:
works for me on slim ics which is based on cm9. Making he broke something in samsung roms whilst fixing cm9 :S
[Galaxy S II Original Android Development] crachel:
I don't think I made a speech or was being crude. We have had numerous reports in this thread over the last 24 hours about off topic and pointless posts, so obviously some people saw a problem.

Thanks
[Galaxy S II Original Android Development] cheewaca:
Same problem with xwlp2 stock deodex.
[Galaxy S II Original Android Development] almaalma74:
stock xxlpq odexed also... :(

b5 was fine
[Galaxy S II Original Android Development] bleuxeon:
I can't agree more than that.
[Galaxy S II Original Android Development] eric-filth:
If you want more than 1.6ghz just install tegrak ultimate

Enviado do meu Galaxy S2 Undervolt usando Tapatalk
[Galaxy S II Original Android Development] bleuxeon:
Ok, maybe I did not read all those posts since I skip a lot of posts that are not interesting/ask for 1000 time asked question etc... and I m now used to do it : I read EACH page one by one but as I said I skip everything uninteresting.

Thanks anyway for your for answering.:)
[Galaxy S II Original Android Development] It_ler:
-1

I can not confirm this known problem.

With SiyahKernel v3.0beta6, my phone runs smoother than (XXLPQ) stock kernel, and has better results in nearly every benchmark I ran (the only exception was Linpack) - all on complete defaults (no OC).

I updated my test results in non-dev thread => http://xdaforums.com/showpost.php?p=23931031&postcount=871

Thanks Gokhanmoral for the first ICS custom kernel with such excellent features.
[Galaxy S II Original Android Development] bleuxeon:
I have tried to reproduce on CM9+ Siyah the very exact same seetings I was using with CM7+Siyah : CPU/GPU frequencies and voltages, all Ondemand parameters, and use the same scheduler.

And I must say, as you was speaking about benchs, that I have lower results using CM9+Siyah.

Antutu gives me arround 7500 with CM7+Siyah, when CM9+Siyah gives "only" 6200.

I don't know if its CM9 that doesnt perform as CM7 or new beta Siyah.

Anyway in dayly use CM9+Siyah look smother.
[Galaxy S II Original Android Development] Vaedryn:
Wayn benchmarks, the system must work and feel smooth, nothing more.

SGS II Cyanogen Mod 9 Tapatalk
[Galaxy S II Original Android Development] bleuxeon:
Good benchmarks are very good syntetic test tools, whatever you say....or repeat....:p
[Galaxy S II Original Android Development] dee163:
Are the download links down?

Cant download
[Galaxy S II Original Android Development] Nuja:
they seem down, cant download too.
[Galaxy S II Original Android Development] ernest33:
I found this http://www.wuala.com/Turkbey/Turkbey_Box/Kernel/Siyah_Ics/Siyah-v3.0b6.tar/

Just flashed it and it's ok :D
[Galaxy S II Original Android Development] lamedor:
Hello

First, I want to say thank you for all your work gokhanmoral !

I have problems with all bench at 1.6GHz, scores are lower than stock !

Someone else with the same problem?

Thanks

It's with beta 6 and same problem with all others beta.
[Galaxy S II Original Android Development] gabx:
You can try using BLN control from Play market. In the settings, you choose the timeout of Leds.

What I found is that BLN are working ONLY with this app, and usage is fancy and random.
[Galaxy S II Original Android Development] :
Any solution for dpi then mate?

Sent from my SGS2 - Powered by CM9
[Galaxy S II Original Android Development] bleuxeon:
pushing your CPU to this level, even if it looks stable, doesn't mean that it compute things correctly.

That is why you get lower bench results.
[Galaxy S II Original Android Development] t00dy:
sorry, didn't realize i was in the DEV :/ Moderator please move my post to non-DEV section.

@Tungstwenty: i tried following your procedure exactly, but without success. Odin does not recognize the device :/ I hope i get the JIG tomorrow morning, and i will also try with that, but i think it wont work (colcluding from what i read). Also if it has this eMMC bug i also heard that JTAG won't work...i am doomed :S

EDIT: The JIG does NOT work either!! :/
[Galaxy S II Original Android Development] Happy_Jack:
My phone has spontaneously powered itself off a couple of times with v3.3.1. I never saw this with v3.2.7.2 or earlier versions. It seems to happen when plugging in to my car cradle (which appears as a dedicated USB charger). The phone was on (and playing music in one case). Next thing it was off (showing the big green charging battery symbol). In both cases a long press on the power button turned it on again OK. CPU is not under-volted. Anybody else seen this?

Edit 13th June: having reinstalled v3.3.1 and reset exttweaks settings in recovery it no longer seems to happen, so it was presumably due to incompatible data structures between those 2 versions. Thanks for the hint @KennyLegend.
[Galaxy S II Original Android Development] Thenetstriker:
UVC USB webcam support

Hi Gokhan, would it be possible to add the drivers for USB UVC webcams into your kernel? On my ASUS Transformer Prime T201 those drivers are integrated and I am able to grab the picture from any UVC webcam that is connected using this app: http://brain.cc.kogakuin.ac.jp/research/usb-e.html

Would be great to have this on the Galaxy S2!
[Galaxy S II Original Android Development] g00ndu:
I think it is not the eMMC bug. probably a JTAG might be able to revive your phone.
[Galaxy S II Original Android Development] ermacwins:
So it will now work on CM9? And if Im not mistaken, you added NTFS Support?
[Galaxy S II Original Android Development] D4rKn3sSyS:
@gokhanmoral, does this kernel has MMC_CAP_ERASE command removed?. I have read what Daniel Hillebrand said on Google+, and Seems like im not a lucky guy :D. I guess it has, as my phone is still alive, but however I prefer you to say me yourself.

EDIT: Well seems like I didn't read enough. This kernel is always been safe as i9100 update4 sources, wich this kernel is based on, have not MMC_CAP_ERASE, unlike Gnote guys. Sorry about the paranoiac reaction.
[Galaxy S II Original Android Development] CamoGeko:
MMC_CAP_ERASE=0 ;)

Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
[Galaxy S II Original Android Development] vizdak:
I experienced it also during backuping files using titanium backup. And also I experienced SOD, I have to pull the battery and when the battery is put back again my phone boot without pressing the power button. I wipe cache and dalvik and then fixed permissions and I'll observe if it dies again. If gokhan will come back someday, please check the two last_kmsg attached.
[Galaxy S II Original Android Development] pikachu01:
I see from your signature that you're undervolting. Try not undervolting and try again?
[Galaxy S II Original Android Development] vizdak:
Oh crap I forgot to change my sig. I'm not undervolting during the sod and during backuping using tb. I'm on 200 mhz to 800 mhz pegasusq and the rest are defaults as it is.
[Galaxy S II Original Android Development] johnbeetee:
just a suggestion: did you go from 3.2.8.x to 3.3.1 without wiping your data partition?

your first last_kmsg reports some inconsistancies in mmcblkp10, which is your secondary data partition, and maybe this explains why it happens with TB.
[Galaxy S II Original Android Development] vizdak:
Yeah from 3.2.8.2 I flashed 3.3.1. And I never wipe data since I got my phone. Do I have to wipe data before going to 3.3.1 version? I read about data wipe that it can brick my phone.
[Galaxy S II Original Android Development] johnbeetee:
...flashing can brick your phone too, if you have bad luck...

I'm not saying you have to, but your problems could have been caused by 3.2.8.2 since there were some experimental patches included

you can read about in the discussion thread

if this is the case in your situation, it could be the cause of your problems (that's the impression I got from your last_kmsg)

I ran into that problem going from 3.2.8.2 to 3.3.1 and back to 3.2.8.2

the only sure way to solve it is to wipe your data partition (you can find my post and that of others in the discussion thread) and restoring your data from a nandroid backup

So concluding: I'm not pin-pointing that exactly that is your problem, just saying it could be...

and it's your free decision if you want to try and solve it this way, and see if it works

Just trying to help (and assuming your an experienced 'flasher' :))
[Galaxy S II Original Android Development] vizdak:
Thank you very much. I tried wiping cache/dalvik and fixed permissions. So far so good. For now I'm observing if it will happen again. And if it does then I have no choice but to wipe data partition. Thanks for the help.

Edit: I'm having freeze issues in 3.3.1. So, I'm back to 3.2.7.2 for now. From 3.2.7.2 I'm flashing 3.3.1 and no problems anymore. Currently on 3.3.2 and no issues on sod.
[Galaxy S II Original Android Development] johnbeetee:
See and look how it goes...maybe that's just what was needed..

If it is the '3.2.8.2' problem (which somehow partly corrupts data partition), formatting data is the only way...

You don't have to lose any data...like I said, look in the discussion thread for how to do that

for example mine:

http://xdaforums.com/showpost.php?p=27020685&postcount=1324

but you can look for others from other posters
[Galaxy S II Original Android Development] gokhanmoral:
It is not true that I don't develop anymore. It is just I don't have time lately. I am in Istanbul and I will not have any time to develop anything (s3 or s2) for a week or so. I still want to implement BFN for s2 and s3 and also mtp/mass storage mode selection in ExTweaks. Also I may revert back to old wifi drivers based on the feedbacks, or better make it optional.
[Galaxy S II Original Android Development] Phistachio:
Could you tell me, what is BFN?
[Galaxy S II Original Android Development] runedrune:
Just like BLN but instead it uses the camera flash to alert you of notifications.
[Galaxy S II Original Android Development] THE RED BLUR:
Dude. Is your wife really gonna let you use the SG2 since its her phone now.

I don't know a woman that would give up her phone for hours to her other half to experiment on it and she won't be able to talk and text to her friends while all this is going on. :p

Unless u are a Jedi and are using the powers of the force;)

Either why I truly hope u have direct access to the SG2 whenever u need to test. We need u back. U know that sg3 is too heavy and big to use. :D

Using Resurrection Remix AOKP ICS version 2.2 powered RootBOX
[Galaxy S II Original Android Development] werker123:
From what version is the emmc hardbrick bug fixed? I'm now on v3.2.6.4 And want to update my resurrection remix v2.0 to v2.2 but not sure if it's safe to whipe:S Any one knows if it is fixed and i can just wipe it/flash it?
[Galaxy S II Original Android Development] Rawi666:
@werker123

Every versions except 3.1rc6 are safe.

Don't worry and go ahead
[Galaxy S II Original Android Development] johnbeetee:
3.2.6.4 should be safe...

to be a little more exact, the actual emmc patch has been added as of 3.2.5.2

https://github.com/gokhanmoral/siyahkernel3/commits/update4-3.0.y?page=4

(may 22nd)
[Galaxy S II Original Android Development] rauschkugl:
Can you finally go to the general thread with that stuff and leave this thread to developement related things....
[Galaxy S II Original Android Development] gokhanmoral:
v3.3.2 is up.
[Galaxy S II Original Android Development] luisfer21069:
ARCH_POWER? whats the benefit of having it tick?