yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Many40:
If you haven't checked it yet by yourself just to confirm - backed up my rom by CWM recovery 5.5.0.4 touch recovery (from Siyah 3.3.2 kernel) and just restored it by 5.0.2.7 CWM recovery (from CF-root kernel). Regards
[Galaxy S II Original Android Development] pikachu01:
The phone actually does sleep even with the script on. The wait_for_fb_wake/sleep is a function that pauses the script when the screen is on/off.
[Galaxy S II Original Android Development] Sharkssbm:
Thanks Johnbeetee,

I will try this,just another thing which is best Rom you have for your 2nd Boot, it says on your sig. that you have HydrogenICS 27.4 - primary stock LPQ any link for that pls.

Cheers

Sharks
[Galaxy S II Original Android Development] johnbeetee:
calling a rom 'best' is more or less a personal opinion ; I happen to like HydrogenICS,

but there countless of other roms out there you might like...

for Hydrogen you can go to:

http://xdaforums.com/showthread.php?t=1530179
[Galaxy S II Original Android Development] ec95:
I have the same problem. Came from Checkrom6 with siyah 2.3.6 and loaded the new kernel 3.3.2. Now phone wont boot. It just dies after boot loader screen is shown. any tips on how to solve?
[Galaxy S II Original Android Development] Many40:
Sorry, but you used GingerBread based rom with older Siyah kernel. Kernel above ver. 3.x.x are design for ICS based roms only (not compatible with GB roms).
[Galaxy S II Original Android Development] robertobsc:
I just runned build_kernel.sh. Is there anything else that I must do to include payload.tar?
[Galaxy S II Original Android Development] Sharkssbm:
Thanks Johbeetee, apprecaite your input in Rom department. Its a personal choice like girls isn't it? I like big Ar** women then Big Ti***one so it's a matter of choice friend.

Ciao

Sharks
[Galaxy S II Original Android Development] sinancetinkaya:
I think you don't have initramfs.

You have to set up its path through Make Config
[Galaxy S II Original Android Development] johnbeetee:
..just went through build_kernel.sh and payload.tar should be included, so if you didn't get any errors, it must be there (was just an impression I got judging from the size you're missing)

then maybe sinancetinkaya has the right solution : did you download the initramfs structure and have it included (although I would expect an error message if it couldn't be found, but then again I'm not that experienced in building kernels..)

edit: I do see a reference to initramfs3 at the start of build_kernel.sh ; wouldn't this generate an error message if you didn't download it?
[Galaxy S II Original Android Development] robertobsc:
When I get home I'll take a look. Probably something is missing.
[Galaxy S II Original Android Development] gravityz3r0:
Hmm, the Vibration Level setting in Extweaks doesn't have effect in my RR 2.5.2 + Siyah 3.3.2 combo. I changed from 6 all the way to 0 and the vibration intensity does not change at all even after reboot. Am i doing something wrong? Can anyone help me?
[Galaxy S II Original Android Development] johnbeetee:
If you have root explorer, have a look at the content of:

/sys/devices/platform/tspdrv/vibrator_level

and see if it's equal to your setting level ( I suppose 0)

there's also a file vibrator_level_max (siyah this should be 6)

you can try editting this last one and put it to 0 also

if it still doesn't behave (not vibrating) like you would expect then something is screwing things up (maybe the rom-control? There could also be a setting in your rom's settings controlling this in some other way?))
[Galaxy S II Original Android Development] Many40:
I personnaly didn't use this but I red in droidphile thread that it is vibration intensity for notifications and it is most likely noticable in AOSP/AOKP roms. The options for vibration I checked you can also find in phone settings/sound/vibration intensity. Regards
[Galaxy S II Original Android Development] robertobsc:
Just saw what i missed. I just looked in the wrong place.

I looked in kernel_dir/arch/arm/boot, but the kernel + payload + recovery was in kernel_dir

I installed in my cel, my wi-fi is also not working. :crying:

Now i must look.... would be some patch that we must apply before building the kernel ? Or maybe the module wasn't loaded?
[Galaxy S II Original Android Development] Tungstwenty:
Yes, the file under /arch/arm/boot is the kernel only, you need the one on the root which also has the rest of the stuff.

I compiled and flashed it successfully from the latest sources. No problems with the WiFi driver here.

I'll share my build in just a moment.
[Galaxy S II Original Android Development] mobilio:
I have an overheating issue with my phone when it is charging with WiFi on.....going up to 51°c....sometime 54°c....

Currently on 3.3.2, using the LPD Foxhound and CM9 nightly....same situation.

Any suggestion for me?

Thanks!
[Galaxy S II Original Android Development] robertobsc:
Have you just exported CROSS_COMPILE and runned build_kernel.sh or did u also runned make config or done some more config?
[Galaxy S II Original Android Development] Tungstwenty:
I previously exported CROSS_COMPILE, ARCH=arm, SUBARCH=arm

Recently there was a change in build_kernel.sh that hard-codes the CROSS_COMPILE var, so I just went to the parent folder and created a symlink named "android_prebuilt" pointing to the prebuild folder of my aosp sources repository.
[Galaxy S II Original Android Development] kairi_zeroblade:
could the source be compiled using Linaro??i heard there are many ARM optimizations with Linaro..:confused:
[Galaxy S II Original Android Development] sinancetinkaya:
Wrong post....
[Galaxy S II Original Android Development] Tungstwenty:
Actually, that's exactly why I ended up not posting it. I'm using the build, which was my goal in the first place. I'll send my source patches to him and he'll decide whether it's worth including or not.
[Galaxy S II Original Android Development] robertobsc:
can you share yout toolchain? i cant download the toolchain from CM, the android_prebuilt is to heavy, it hangs alll the time.
[Galaxy S II Original Android Development] Tungstwenty:
Here you go: https://www.dropbox.com/s/izdtyhc6buhywa1/toolchain_linux-x86_arm-eabi-4.4.3.tar.gz

To compile, you should create a folder with these 3 contents:

- siyahkernel3 (clone of repository)

- initramfs3 (same)

- android_prebuilt/linux-x86/toolchain (unpack here the downloaded archive to obtain a "arm-eabi-4.4.3" subdir with the files)

Then go to siyahkernel3 and run ./build_kernel.sh.

If you do this with the sources as of today, the build_kernel script will define the CROSS_COMPILE variable to point to the correct place.
[Galaxy S II Original Android Development] robertobsc:
It's just perfect now! The problem was really the toolchain.

Really happy now. Starting to update sources today!
[Galaxy S II Original Android Development] cheewaca:
Try with Siyah 3.2.7.1 and LPS modem.
[Galaxy S II Original Android Development] Sharkssbm:
Would appreciate any help as my WiFi is not working either, what's wrong it was ok this morning and all of a sudden it does not connect? is this a kernel fault or Rom fault.:fingers-crossed:
[Galaxy S II Original Android Development] CamoGeko:
Tried restarting your router? Or changing its channel?

Sent from my HTC One X using Xparent Red Tapatalk 2
[Galaxy S II Original Android Development] Sharkssbm:
Thanks Geko, so its not anything to do with my Kernel then mate, its to do with my Router I will try bit later and will report, what do you think of my phone running hot as well as battery is very poor. Could that be Kernel fault? I have just changed the Modem LPS and downgraded the Siyah kernel to 3.3.1 as I was on latest 3.3.2, have I done the wise move? I had read somewhere in the thread regarding the overheat situation?

:confused:
[Galaxy S II Original Android Development] Sharkssbm:
Done it doh why didn't I think of that, thanks anyway:victory:
[Galaxy S II Original Android Development] tlf55:
Does "SCHED_MC" really help to save more battery ?

Thanks
[Galaxy S II Original Android Development] nitinvaid:
GM please just one update with working dsp manager
[Galaxy S II Original Android Development] Many40:
I am not using this option (SHED_MC=0) because in my opinion if CPU hotplug is set enabling SHED_MC doesn't make really sense, especially for battery saving. See below opinion of droiphille which supported my thinking:

"Let's say enabling sched_mc on Galaxy S2 Exynos 4210 is completely pointless. Hotplugging is well handled by stand hotplug/legacy hotplug. Two logics trying to do same thing is always bad. It's like having two antivirus software on PC or like freq_step and smooth scaling trying to do similar stuff in ondemand based governors.

Sched_mc = 1 = Assymmetrical loading of cores. This can hinder race to idle (talking about AFTR here).

sched_mc = 2 = load balancing. When hotplugging knows when and how to hotplug In and Out second core, there's no need of another logic to do the same and cause conflicts. If you're using forced dual core mode, this may have some benefits. I never tested myself.

conclusion: let shed_mc=0 as long as you're using hotplugging. If you're on dual core mode (remember aftr/lpa can not be hit when second core is On), try sched_mc=2. However i don't think load balancing can save battery. It may utilize both cores effectively."

Regards
[Galaxy S II Original Android Development] tlf55:
Thanks ! So i put the Hotplug mode " CPU Hotplug (default) " but in governor i have to put pegasusq or hotplug ?

Thanks again ! :)
[Galaxy S II Original Android Development] Many40:
This is subjective. I am using pegasusq which is most tweakable. Others use lulzactive, SmartassV2 etc. You have to read more about governors choose one which is most suitable for you and test it. BTW enable also GENTLE_FAIR_SLEEPERS and ARCH_POWER in ExTweaks.

Edit: You can see my settings in my signature, but of course what wotks for me will not necessarilly work for others

Cheers
[Galaxy S II Original Android Development] tlf55:
I don't want to use SCHED_MC so i use Hotplug like you told me.. but is pegasusq use hotplug mode ? or just hotplug governor use cpu hotplug ?

Thanks (by the way i'm using same settings of you, i just didn't undervolted my phone)
[Galaxy S II Original Android Development] Many40:
I am using pegasusq because works fine for me and is recommended by kernel dev. Both kernels are multi-core aware but hotplug is less popular. You can set also SMOOTH SCALING LEVEL to 800 Mhz.

Regards
[Galaxy S II Original Android Development] TheStigx:
EDIT NWM
[Galaxy S II Original Android Development] Thenetstriker:
I've managed it to compile the asix network drivers for the Siyahkernel 3.3.2 myself. Just install the files in the attached zip file using these commands:

insmod mii.ko

insmod asix.ko

I've successfully tested the driver under Cyanogenmod 9 with my Trendnet TU2-ETG USB to Ethernet adapter.
[Galaxy S II Original Android Development] b2rdetor:
exfat

is it possible to add exfat support to siyah???
[Galaxy S II Original Android Development] killian32:
I've using 3.3.2 kernel with XWLPF ROM. I did a "clean" install of ICS (wiped data, cache, reset to factory, formatted SD) but it seems to be less responsive than GB. Anyone got the same configuration ?
[Galaxy S II Original Android Development] Matt3333:
Definitely not whinning about no updates from gok, couldn't ask for more on the latest version. He does have a life.. and an S3, I suppose. However, I shall be whinning for a JellyBean update!
[Galaxy S II Original Android Development] moneyover:
Does anyone know what the best version of this kernal is ?
[Galaxy S II Original Android Development] CamoGeko:
Its kernel btw.

Yes, either 3.3.2 or 3.2.7.1.

Sent from my HTC One X using Xparent Red Tapatalk 2
[Galaxy S II Original Android Development] nihilista:
Hi,

is it possible and secure to flash siyah kernel with mobile odin or cwm app on stock ics rom (SGS2)? To get rid of yellow triangle on boot? Didnt found anything about this, so i asked here...

thx
[Galaxy S II Original Android Development] Many40:
As far as I understood you, you have already preinstalled and rooted stock rom on your phone. In this case you can either install kernel from preinstalled custom CWM recovery (what I usually do) or from mobile odin.

But remember, if you would like to flash rom and kernel together, don't flash Siyah in mobile Odin at the same time with a rom- I did it and got soft brick.

In this case I recommend (to avoid yellow triangle) to do as follows: flash stock rom via mobile odin together with CF-root kernel, (replace in mobile odin stock kernel with CF-root - suitable to rom version) and flash all together. Then afterwords flash Siyah from CWM recovery.

It is theoreticaly not required but I wipe cache and dalvik before flashing Siyah and also tick these options in mobile odin. You don't need to tick ever-root option in mobile odin when flashing with CF-root. Regards

If you don't have yellow triangle on boot my method ensures that you don't get it. But if you have it already use at the end triangle away.
[Galaxy S II Original Android Development] Oso Polar:
Yes.

You'll not get rid of yellow triangle just by flashing Siyah kernel - you need TriangleAway app or flash stock kernel.

I'm always using stock Samsung ROM (with Siyah kernel, ICS Domination and other tweaks). I'm upgrading from one firmware to another using Mobile ODIN Pro with "Enable EverRoot" + "Inject Superuser" + Inject Mobile ODIN" + "Wipe data and cache" - this gives you clean stock firmware with stock kernel (already rooted with SuperSU and Mobile ODIN Pro installed). And then using the same Mobile ODIN Pro I'm flashing Siyah kernel. And then it is time to restore things from TitaniumBackup etc. Never had problems so far...
[Galaxy S II Original Android Development] tlf55:
Do it will be available for 4.0.4 ? Flashed 4.0.4 then Siyah 3.3.2 but i had some problem..
[Galaxy S II Original Android Development] #illidan:
It does work on 4.0.4. What were the steps that you took to flash?
[Galaxy S II Original Android Development] ore616:
I find 3.2.7.2 to be the best for battery life and general day to day use.

3.3.1 and 3.3.2 chewed up my battery.
[Galaxy S II Original Android Development] nihilista:
Ah, thx. And i flash only the correct zimage file from my stock kernel, then flash siyah kernel zimage file (and then triangle is away), right?
[Galaxy S II Original Android Development] johnbeetee:
I was curious about that too, what #illidan asked

and are you perhaps talking about the most recent samsung stock 4.0.4 ?

If so, I was eager to try that one too, but saw that it came with a .pit file

which usually means it needs to resize the partitions differently, and I wasn't sure how heavily siyah relies on the sizes being what they are now....
[Galaxy S II Original Android Development] killian32:
I'm on 3.3.2. Could I downgrade to 3.2.7.2 just flashing the old kernel?
[Galaxy S II Original Android Development] Many40:
Have you red my answer and Oso Polar's answer carefuly? If you have got already yellow triangle, flashing kernel will not remove it. One of the methods to remove it (I thing easiest one) is to use Triangle Away app.

If you don't have yellow triangle, our methods for flashing kernel will protect you from geting it. You will get it only if you flash from PC version of Odin.

BTW: You shouldn't post here this kinda questions, because this is DEV thread. The best place is hare:

http://xdaforums.com/showthread.php?p=28308849#post28308849

---------- Post added at 08:32 AM ---------- Previous post was at 08:25 AM ----------

Yes, wipe cache and dalvik is not required but you can do that.
[Galaxy S II Original Android Development] killian32:
Sorry to bother again. I've recently upgrade to ICS 4.0.3 (XWLPF) with Siyah 3.3.2 and I've noticed that touch screen is less responsive. Is this a know problem or should it be my problem ? (I've already increased touchmove to the max).
[Galaxy S II Original Android Development] nihilista:
Yes, sorry, didnt find the general thread for this ;-)

But what i mean was first flashing stock rom with mobile or pc odin, then rebooting and flashing kernel zimage with mobile odin or cwm app. I asked this cause i am new on sgs2, but flashed kernel and other stuff many times on sga. but im not sure if its a good way, cause if first install stock rom, i have no root for mobile odin or cwm and maybe cant install kernel this way....

btw, thx for answer, next time i ask in other thread.
[Galaxy S II Original Android Development] Many40:
No problem. As me and Oso Polar said:

1. To not have yellow triangle flash stock rom (.tar) from Mobile Odin,

2. To not loose root either flash it with stock kernel replaced by CF-root kernel or (Mobile Odin Pro is required) check ever root option in the app.

3. Then you can flash .zip version of Siyah kernel from CWM recovery (what I do and recommend) or .tar version from mobile odin afterwords (what Oso Polar recommends.) That's all.
[Galaxy S II Original Android Development] timberwolf60:
It was a nature of ICS. Use

Extweats to fine tune the touch respond.

Send from my GT I9100 using Tapatalk2, 1st ROM Paranoid V1.5a, and 2nd ROM XXLPW with Jkay theme V14, Siyah 3.3.2 kernel
[Galaxy S II Original Android Development] minidou-77:
Set touchmove to minimum ;-)
[Galaxy S II Original Android Development] killian32:
Thanks I've just found a guide. I was in the wrong direction !
[Galaxy S II Original Android Development] SoLoR1:
yes they are issues with siyah kernel and 4.0.4 samsung stock rom. One is camera app is not working properly there is no picture of what you want to take picture (just black screen), but when you press button to take picture it works... its same with instagram integrated camera... reverted back to XXLQ5 stock kernel and it works again....

edit: what i got from other posts it also breaks bluetooth... didnt try this my self....
[Galaxy S II Original Android Development] gokhanmoral:
new kernel release from samsung will have a lot of differences especially in fimd part.

and that one will not work on 4.0.3 as the one for 4.0.3 doesn't work for 4.0.4

I will try to build a kernel for 4.0.4 as soon as I can finish the current beta in S3.

it is hard to work on both devices while having some other things to do in life...
[Galaxy S II Original Android Development] SPBoss:
Thanks for continuing support on the S2 even though you bought the S3! :)
[Galaxy S II Original Android Development] yhrn:
Thank you for all your efforts! Especially now when you've moved on from this device.

Confirmation number: 29193364CM780223Y
[Galaxy S II Original Android Development] :
I hope you add support for jelly bean as its almost fully booting ;)

only starting applications and its gets stuck there :D
[Galaxy S II Original Android Development] anaweb:
Loss of 6% of the battery time of inactivity for 5 hours
[Galaxy S II Original Android Development] chiggah:
anyone know the default settings for Siyah 3.3.2 ?

CPU and GPU

tryign to switch back to default.. but have to buy paid version
[Galaxy S II Original Android Development] Many40:
Go to CWM recovery, Kernel specific options/Reset ExTweaks profiles and reboot. Afterwords open ExTweaks app and you will see all default settings, except CPU voltages (for this you can use for example Voltage Control app).
[Galaxy S II Original Android Development] Jamirobe:
Is there a way to install Apps on both Roms. For example if i install XDA app on my primary rom, thst id is also installed on secundary?? Or must i always install each app on both roms. I copyed the apks of the apps by using root explorer but it takes long, and i ofen change the secundary rom so i always have to install my apps again and again
[Galaxy S II Original Android Development] ephraim:
You can always backup your app using Titanium Backup and restore it to your primary or secondary rom :)
[Galaxy S II Original Android Development] Many40:
The way Gokhanmoral developped his kernel is that for 1st rom apps are stored in a separated partition located in rootfs in /data folder but for 2nd rom data partition is located in /sdcards/.secondrom folder as mountable image "data.img". So, you have to install apps separately for both roms. Probably the reason for that may be that some apps can be compatible with one rom but not with the second, moreover app's settings may be different for different roms.

What you can do - backup apps by Titanium Backup in the 1st rom and simply restore them in the 2nd one (under condition that apps are compatible with both roms). But you have to keep in mind that as default settings Titanium Backup uses /sdcard/TitaniumBackup directory to backup apps. But later on when you use apps on both roms and from time to time backup them - the last backup will be valid (doesn't matter from which rom they were made) - apps database will be overwritten by each backup. So if you accept this situation it's ok.

I personnally prefer to maintain separated backups for each rom to keep uniqueness of apps settings of each rom. You can set different folder in TB of 2nd rom in TB settings / Backup folder location.

Regards
[Galaxy S II Original Android Development] *Decimus*:
Can confirm... breaks bluetooth
[Galaxy S II Original Android Development] wpmike:
I can confirm it does break bluetooth which is extremely annoying especially while driving.
[Galaxy S II Original Android Development] timberwolf60:
You need to install programs in each rom and can share the same data. I have two set on titanium backup set first rom(Sammy rom) on ext sd card and second rom(paranoid android) on the int SD card. Some programs not compatible on both rom like CSC select as I was using. paranoid rom was my daily rom.

Send from my GT I9100 using Tapatalk2, 1st ROM Paranoid V1.5a, and 2nd ROM XXLPW with Jkay theme V14, Siyah 3.3.2 kernel
[Galaxy S II Original Android Development] timberwolf60:
LQ5 in stock kernel was working very well with better touch respond. But not with siyah kernel. Bluetooth can't turned on, video, camera and video recording black screen. Siyah kernel need to update. Enjoying siyah kernel for dual booting.

I will put 4.0.4 on hold until GM updated this excellent kernel. Thank.

Send from my GT I9100 using Tapatalk2, 1st ROM Paranoid V1.5a, and 2nd ROM XXLPW with Jkay theme V14, Siyah 3.3.2 kernel
[Galaxy S II Original Android Development] Many40:
Thanks for supporting my answer :)
[Galaxy S II Original Android Development] robertobsc:
Hi guys,

Someone knows how can I download 3.2.7.1 sources from gokhan's github?
[Galaxy S II Original Android Development] Gammelgustav:
What about 4.0.4?

LQ5 won't boot with Siyah...

What changes are needed?

Sent from my Galaxy S2
[Galaxy S II Original Android Development] johnbeetee:
http://xdaforums.com/showpost.php?p=28324460&postcount=10136
[Galaxy S II Original Android Development] gokhanmoral:
actually working on it right now.

got a nandroid backup and now I have 4.0.4 on my wife's phone.

I have 4 hours, counting down :)

it works on 4.0.4 (flashed without pit & data partition)

but I have the camera problem.

the first thing I tried was sgs3 sources and update7 sources unmodified but they don't seem to fix it.
[Galaxy S II Original Android Development] pikachu01:
I'm guessing that a new source code drop is needed to fix this. Can't really do anything until the official ROM is released, then the updated source is dropped. :/
[Galaxy S II Original Android Development] ROHIT345:
GM,

Don't brick your wife's phone...this lq5 has the same brick bug...and few users have already hard bricked there devices doing data wipe.
[Galaxy S II Original Android Development] timberwolf60:
I run got brickbug and shown on my phone. Wipe on xxlq5 and my s2 still alive. This may only applied to s3.

Send from my GT I9100 using Tapatalk2, 1st ROM Paranoid V1.5a, and 2nd ROM XXLPW with Jkay theme V14, Siyah 3.3.2 kernel
[Galaxy S II Original Android Development] minidou-77:
It's not the same brick bug but an incompatibility between the new pit provided with lq5 and the old one

When you try to restore an old CWM backup made on the old pit on the new one -> brick