yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Gustavo_s:
well i did exactly that :D guess what, missing drivers fixed after applying r3p1 mali drivers update to my source, im getting another error now about the missing mali_r3p0_lsi folder, used to load 2 mali drivers in the same kernel i think, im copying that folder and ump_r3p0 folder to my source again, last try for tonight i need to sleep. I started to play with linux and building this week btw :D
[Galaxy S II Original Android Development] It_ler:
Yes, kind of workaround. You can use the live thumbnail video player of the Galaxy Note (available as mod), or alternatively use another video player (e.g. MX Player from Play store).
[Galaxy S II Original Android Development] Tungstwenty:
IIRC you need to do 2 things in order to compile b5 from the github sources:

- don't use arch/arm/configs/siyah_s2_defconfig but rather updated settings which GM used when compiling b5 and that aren't committed to github

- the same for initramfs contents

You can obtain the actual config used by running "gzip -cd /proc/config.gz" from a running b5 kernel. Here's the diff .../siyah_s2_defconfig .config:

40c40
< CONFIG_LOCALVERSION="-Siyah-s2-v6.0b3"
---
> CONFIG_LOCALVERSION="-Siyah-s2-v6.0b5"
164c164
< # CONFIG_MODVERSIONS is not set
---
> CONFIG_MODVERSIONS=y
418d417
< # CONFIG_COMPACTION_RETRY is not set
554c553
< # CONFIG_USB_CDFS_SUPPORT is not set
---
> CONFIG_USB_CDFS_SUPPORT=y
649c648
< CONFIG_OABI_COMPAT=y
---
> # CONFIG_OABI_COMPAT is not set
663,664c662
< CONFIG_COMPACTION=y
< CONFIG_MIGRATION=y
---
> # CONFIG_COMPACTION is not set
745,746d742
< # CONFIG_FPE_NWFPE is not set
< # CONFIG_FPE_FASTFPE is not set
1394d1389
< # CONFIG_BCM4334 is not set
1395a1391
> # CONFIG_BCM4334 is not set
1396a1393,1394
> CONFIG_BCMDHD_FW_PATH="/system/etc/firmware/fw_bcmdhd.bin"
> CONFIG_BCMDHD_NVRAM_PATH="/system/etc/wifi/bcmdhd.cal"
1398d1395
< # CONFIG_WLAN_COUNTRY_CODE is not set
1949a1947
> # CONFIG_VIDEOBUF2_ION is not set
2154c2152,2155
< # CONFIG_ION is not set
---
> CONFIG_ION=y
> CONFIG_ION_EXYNOS=y
> CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE=45056
> # CONFIG_ION_EXYNOS_CONTIGHEAP_DEBUG is not set
2185a2187
> CONFIG_FB_S5P_VSYNC_SYSFS=y

As for the right initramfs contents, you can use one of the existing unpack scripts to grab them from zImage and replace the contents you fetched from github.

For my personal build, I have done this plus I did a few changes to better match the ones in the stock kernel, although the differences don't look very relevant (minor init.rc changes, different mfc_fw.bin, etc)

But from the error you mention, it looks to me that the real problem is that you're ignoring build_s2_kernel.sh entirely and calling make yourself. You forgot the "export ARCH=arm" :)

Here's what you can do to quickly have it compiling:

- Fetch the 2 repos to base_dir/siyahkernel3 and base_dir/initramfs (sibling folders)

- Create base_dir/siyahkernel3/.config with the same contents as /proc/config.gz, or apply the patch I posted

- Replace the initramfs with the contents of b5 zImage and adjust whatever you need

- Edit siyahkernel3/build_s2_config.sh and add "export CROSS_COMPILE=~/android/aosp/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/arm-eabi-" (or whatever) to the top. Also edit the strip line to become "${CROSS_COMPILE}strip --strip-unneeded ..."

That's it, calling ./build_s2_config.sh should create a good build.
[Galaxy S II Original Android Development] Gustavo_s:
@Tungstwenty

Thanks that will help a lot

Here is what i have in mind:

- compile a working kernel

- after the first sucessful build try to add the r3p1 mali drivers to my source (which i already did but i dont know if it will work the way i want to)
[Galaxy S II Original Android Development] Tungstwenty:
Just remember to check if the initramfs scripts that write to /proc/sys/kernel/rom_feature_set still hold (detection of CM roms) and the rom_feature_set_sysctl function in kernel/sysctl.c, which should load your alternate driver instead of .../mali_r3p0_lsi/... : new_late_mali_driver_init()
[Galaxy S II Original Android Development] Gustavo_s:
i started from scratch following your steps, its building with default configs right now.

about /mali_r3p0_lsi, what if i replace its content with r3p1 drivers? so the kernel will detect cyanogenmod and call r3p0 drivers but it will actually load r3p1 drivers
[Galaxy S II Original Android Development] Tungstwenty:
It should work, yes, as long as your replacement compiles.

You might need to do some changes on the makefiles, depending on whether they mention r3p1 explicitly, and perhaps even need to add the new_late_mali_driver_init() function in the main source file with the module init code, as that might have been created by GM to support bundling the 2 drivers simultaneously in a single kernel. And if so, perhaps more changes exist. Try diff'ing your r3p1 folder agains the one on Siyah and checking which differences are part of the driver changes, and which ones are more likely to have been introduced by GM for that dual support.
[Galaxy S II Original Android Development] Gustavo_s:
im getting this error now, it goes all the way building with no errors then stops here:

i have not touched mali drivers yet, all default configs

edit i solved the problem above by deleting line 269 in sysctl.c

edit2 Finally compiled it!! i switched from linaro to NDK compiler, i got my first zImage :D

edit3 it doesnt boot :P stuck on galaxy s2 logo screen, cant even enter recovery with home+vol up, i had to use odin to ressurect it

is there a way to debug what is wrong?
[Galaxy S II Original Android Development] zukosok:
Congratulations Gokhan. I have son to :D
[Galaxy S II Original Android Development] innomi:
Perhaps to late.

But better late Then never!

Congratiolations on your family expansion :)

Sent from my S2 with RR + Siyah combo!
[Galaxy S II Original Android Development] Tungstwenty:
From your description, my guess is that you don't have the CONFIG_MALI_R3P0_LSI define being properly handled, on the makefiles and/or the code to initialize the right mali driver based on rom_feature_set.

The late_mali_driver_init function should always be there (it's from /drivers/media/video/samsung/mali/linux/mali_kernel_linux.c) and the new_late_mali_driver_init is in .../samsung/mali_r3p0_lsi/linux/mali_kernel_linux.c (or r3p1 in your case).

In this block from sysctl.c:

#ifdef CONFIG_MALI_R3P0_LSI
if(rom_feature_set == 3) new_late_mali_driver_init();
else late_mali_driver_init();
#else
late_mali_driver_init();
#endif

I think the config should be true and the right driver init function will be called, as they should be both compiled into the kernel.

IIRC, the *.rc scripts will set rom_feature_set to 3 for CM roms and regular boot, and to 0 for other roms AND for recovery or LPM mode, so the regular driver would make recovery boot correctly.

I don't know how you can debug this on a running device :(

There are a few debugging-related options when you run make menuconfig, but I'm not sure if any of them can help in such a scenario where the device won't even boot.
[Galaxy S II Original Android Development] emwi:
AW: [KERNEL][19FEB] SiyahKernel v6.0b5

i tried many Kernels, but yours is still the B(i)est! Thanks a lot for your great work. You're awesome!

sent from my GT-I9100 with XWLSD & siyah-kernel v6.0b5
[Galaxy S II Original Android Development] Dannyvld:
When will you fix dual boot? Just curious.
[Galaxy S II Original Android Development] rauschkugl:
AW: [KERNEL][19FEB] SiyahKernel v6.0b5

Search and read then you'll find it out. It's only some pages back.

Gesendet von meinem Nexus 10 mit Tapatalk 2
[Galaxy S II Original Android Development] Dannyvld:
Cant find it :(
[Galaxy S II Original Android Development] lovegambler:
is this a known issue or is this the ROM's prob?

when I backup my ROM [zero][bug]Galaxy Note 2 mini v5 there's no prob but when I restore that backup it ends in bootloop but when I backup without this kernal after restoration there's no bootloop everything goes fine..

same happens with dual boot it also gives bootloop on first ROM nd there's no possible way to boot in the second ROM.. :(

m on v6.0b5

help will b appreciated

:Peace:
[Galaxy S II Original Android Development] UltimHero:
Dual boot doesn't work with Samsung based roms .
[Galaxy S II Original Android Development] lovegambler:
ok, no issue with dual booting but what about the restoration from Nandroid it always gives bootloops..

it is must before flashing new ROM I have to make backup of my current ROM but for now its useless because when I restore have bootloops. so I have to perform a fresh installation again :(
[Galaxy S II Original Android Development] cnjax:
You will need to use an alternative backup method as the recovery in Siyah doesn't backup preload, try orange backup app or temporarily flash philz kernel to backup preload

GT-I9100 powered by

NeatRom Lite 4.4

SiyahKernel 6.0b4

JB Reloaded + MyLifeRock10 blue theme

Many40's battery tweaks
[Galaxy S II Original Android Development] HighlanderZA:
+1

BUT:

When using Philz, and you want to do a restore or make a nandroid, you must make sure that the /preload

partition is included. Look under "Backup and Restore" and then "Misc Nandroid Settings" and make sure that 'preload partition' is included.
[Galaxy S II Original Android Development] _FreaK_:
Hi.

Or use this guide from hawkerpaul.

Worked perfectly many times for me with Siyah v6.05b on sammy based custom roms :victory:
[Galaxy S II Original Android Development] PlutoDelic:
just a question...

S2 Kernel comes with CWM Manager v3.15, will it cause any problem installing CWM Manager v3.60 over it?
[Galaxy S II Original Android Development] Soldier2000:
Is this kernel stable to use with Android 4.2.2 (rootbox).
[Galaxy S II Original Android Development] edzamber:
No it doesn't works because v6.0b5 use only mali drivers v1

Posté via Vanilla Rootbox
[Galaxy S II Original Android Development] bogdan1980:
Don't think so. could you put an Dropbox link with this new version? Thanks
[Galaxy S II Original Android Development] PlutoDelic:
it seems to...i;ve noticed chainfire is not really giving much support for the S2, but the S3 seems to be rich with him.

http://download.chainfire.eu/190/CF-Root/SGS3/CWMManager-SGS3-v3.60.apk
[Galaxy S II Original Android Development] xtrevelade:
EDIT: Wrong thread. Sorry.
[Galaxy S II Original Android Development] Many40:
Please read again your post, read subject of this thread and ask yourself a question: "Is Siyah kernel development thread a proper place for my non-Siyah + non-development related questions? "
[Galaxy S II Original Android Development] fhzn:
Hai There, I using MIUI 3.3.1 (custom from Super Nexus 4.1.2) with Base (4.0.4). Are my Rom compatible with Siyah v6.0b5?
[Galaxy S II Original Android Development] xtrevelade:
I revised this already yesterday but wasn't aware of your reply. I am really sorry for posting in the wrong thread. It wasn't done on purpose. I had many tabs opened when I posted this reply and wasn't able to double check it if it lies in the right thread because I was rushing for an errand.

I have learned my lesson and I promise to never make this mistake again.

Thank you very much for your concern. :)
[Galaxy S II Original Android Development] tuniel:
if it is based on 4.0.4 then no, Siyah 6.xx do support only Stock JB roms (see changelog http://goo.gl/ygpvm)

you can use Siyah 5.0.1 (changelog http://goo.gl/kUANs)

good luck

edit: i checked the link you provided: that is a custom rom based on 4.1.2. it is not officially supported in 6.xx, it might boot, but there's no guarantee that it works
[Galaxy S II Original Android Development] innomi:
Its not only for stockrom based.

Im using v6 with resurectionremix. Wich is aokp 4.1.2

Sent from my S2 with RR + Siyah combo!
[Galaxy S II Original Android Development] dipenrique:
How to boot into secondary rom?

How to boot into secondary rom?

Kernel doesnt give option,directly boots into primary rom!
[Galaxy S II Original Android Development] timberwolf60:
Still not ready yet.

Send via i9100 using Tapatalk2,

ROM: Stock XWLSJ

Kernel: Phil XWLSJ V4.91.5

superSU 1.25, exFAT 64GB
[Galaxy S II Original Android Development] dipenrique:
Thanks
[Galaxy S II Original Android Development] HarkDoid:
Mate. you are wrong Miui 3.3.1 is based in 4.1.2 (JB)... you can use Siyah v6.0b5... works perfect included dual boot whit other CM 10.1 rom
[Galaxy S II Original Android Development] Many40:
Hi,

1. Did you read changelog for Siyah6b5 by GM from here?:

http://www.gokhanmoral.com/

The first sentence says:

So, better (being on Siyah6b5) to stick to stock JB 4.1.2 roms as single boot, until GM fixes dual-boot and give full support for CM10.1 roms.

2. This is a development thread and GM doesn't accept any non-development discussions conducted here. Proper thread for this is here:

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

Best regards
[Galaxy S II Original Android Development] gabx:
Nup. My device enters easily deep sleep, even with wifi on.

It should be some misconfiguration somewhere. I advise not tweaking too much if you don't feel comfortable with all these knowledges, neither using too many apps to do the settings.
[Galaxy S II Original Android Development] mrbuzz1967:
can't get this to work for me. maybe i'm just being stupid. on latest wanamlite v10 and tried the fix but but it says something about read only and when i change it to copy the file my phone freezes and i have to pull the battery.

i apologize for my stupidity but not really tried to mess with that stuff before, just normal flashing.
[Galaxy S II Original Android Development] gabx:
Your request is in fact quite judicious.

First, the 3 Kernel is still in beta stage, so for now, do not expect something like a "plain vanilla default" Kernel.

As I am not a huge fan of multi tweaks, what I did with the GB series was read what users reported, stick with big numbers (e.g 2.5, not 2.5.1), and NOT flash the new one too quickly. Wait for a while and see what users say.

When you are satisfied with one Kernel, stay with it. Do not feel like being forced to update. You know, many people are still running Windows XP today, and are very happy!

Overall I think your idea is a good one. The only reproach I can have about his work is the too many beta, experimental or even broken Kernels he is releasing. I do think sometimes it would be better to refrain a litle from releasing. But on other side, he needs feedback from users.

**To Gokhan, things have to be clear. I am not complaining, and ,as told above, I learned to deal with the high frequency of releases. I am just thinking aloud.

---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------

On CM9, with NO hack at all, and no BLN, back/menu buttons are lighted when screen is ON.
[Galaxy S II Original Android Development] danielsf:
Delete 10chars
[Galaxy S II Original Android Development] rauschkugl:
This is not possible because everybody wants something else. Maybe the next person wants to use it the same way as you but doesn't need calkrecording but wants to set a higher clock speed. A new kernel again then? Just don't touch the stuff you don't need. Where's the problem with it. Leave it stock and it's like it isn't there.
[Galaxy S II Original Android Development] Vaedryn:
SiyahKernel v3.0rc1

Posted on March 28, 2012

Changelog:

used lights.exynos4.so which supports both Samsung and CM9 ROMs (thanks to myfluxi for making necessary modifications on it for CM9 part)

native BLN support for CM9 based ROMs.

fixed touch screen sensitivity problem while charging

not released yet.

http://www.gokhanmoral.com/

:)
[Galaxy S II Original Android Development] sadonlyone:
it is not about "something else" here, it's about performance and stability; individual or both.

I pointed that subject by that post and for your consideration, a lot of stuff included means more problems. simplicity always is the best way and that you can apply everywhere on everything on this planet.
[Galaxy S II Original Android Development] :
Does anybody else on cm get sods with beta 7?
[Galaxy S II Original Android Development] stanmarx:
Does this kernel works on MIUI ICS ?
[Galaxy S II Original Android Development] gabx:
Not at all
[Galaxy S II Original Android Development] MistahBungle:
Have you bothered to read any of this thread ? (Yes, I realise there's no mention on the first page of the thread, however...).

No.

Gokhan - Can you please add something to the first post to say SiyahV3 doesn't work with Miui until it does work with same ? Thanks.
[Galaxy S II Original Android Development] rauschkugl:
The kernel is in beta state! There are lots of things included in the gb kernel and there are also no problems. I understand what you want but he can't compile a kernel for every individual liking. If you want your simplicity there are cf root and speedmod. Siyah has always been the one where you can tweak absolutely everything and this shouldn't change.

Sure he could make two versions when it's stable sometimes but then somebody else will come and ask if he can add something in the light version because he needs it but doesn't want to use the full version. This will have no end then and as already said, there are simple kernels which have what you're searching for.
[Galaxy S II Original Android Development] Ven0m:
It was stock GB -> Siyah -> Stock ICS -> Siyah, no extra settings whatsoever. Well, I froze some Samsung bloatware with Titanium - that's all. Still, it's awake for >30% of time (and sometimes even around 90%). I'll just do backup and wipe after RC version is released. Before, Google Play caused a lot of wakelocks, but after disabling auto-update, "System Android" is around 60% of battery usage.

Now... CM9 or Samsung? I hope that I'll be getting standby times similar to what I used to have with Siyah Kernel just before ICS update.
[Galaxy S II Original Android Development] zekurosu:
if u hate Samsung bloatware and touchwiz...then CM9 is an excellent choice...couple with siyah b7 with extweaks modifications does work excellently well enough

Sent from SGSII powered by CM9
[Galaxy S II Original Android Development] gabx:
As far as I can understand, it sems to me your issues are ROM related more than Kernel related.

Best is to do a factory reset between GB and ICS. Then, I am not sure using TB is a very good idea when coming from GB.
[Galaxy S II Original Android Development] sadonlyone:
@rauschkugl

I don't know what to say, you may be right, but my best guess is that you are not. and I thought I was very specific about issues and what is 2 versions about. again: less things means less problems. on the other hand why stick on stock kernel, if this one (a future "light version") is way better ? and I'm not talking only about developing progress...

well, we'll see what and if gokhanmoral has something to say about it. till then, regards.
[Galaxy S II Original Android Development] gabx:
BOTH! That's what Gokhan is working on with his dual boot. Stay tuned.
[Galaxy S II Original Android Development] antt00:
Not a single one with latest nightly.
[Galaxy S II Original Android Development] gokhanmoral:
I added it to the second post after reading the question :)
[Galaxy S II Original Android Development] Mastakony:
CONGRATS GOKHAN
[Galaxy S II Original Android Development] Krishnadusad:
Congrats gokhanmoral :) .
[Galaxy S II Original Android Development] lomistars:
I had same issue using Philz kernel,,my CWM backups became useless because whenever i try to restore i end up on bootloop

i use Jeboo kernel,, everything works perfect,, backup & restore fully working without any problem
[Galaxy S II Original Android Development] pamarakos:
Hi all

Just testing this awesome kernel indeed

I usually test it with Antutu+ui responsiveness self experience

Now 3 things have come up

1) In third part of Antutu with the " many soldiers and their swords" (not gls es2.0 last 3d part, the previous one) I get a yellow or blue colored screen although it counts fps in the bottom till it lands down and shows them in correct colors

2) How can I set via Stweaks performance gov, because even if I set it to performance through Settings-Performance after Antutu finishes I see that cpu is at 800mhz, not 1400 where it started, I've already tried 2nd core always on but no luck

3) Can I somehow have Aroma Filemanager in CWM?

Thanks for this great kernel, it gives ease of tunning my phone

EDIT: Anybody??
[Galaxy S II Original Android Development] big_bum:
2. You reach the thermal trottling temperauture,that's why you get stuck with 800MHz.

3. I don't think so.
[Galaxy S II Original Android Development] pamarakos:
Can you try antutu to see if you get colored yellow or blue screen on 3rd part (gl 1.1 part)

Also I get exactly same behaviour (colored overlaped screen) in nfs shift!!

Thanks for both explanations, this explains a lot:)
[Galaxy S II Original Android Development] bogdan1980:
Put an screenshot pls.
[Galaxy S II Original Android Development] rauschkugl:
AW: [KERNEL][19FEB] SiyahKernel v6.0b5

What's the problem with just flashing the zip? Someone would have to make a modded recovery for this, but it would be possible.
[Galaxy S II Original Android Development] pamarakos:
No I just need aroma file manager to copy some system files after flash rom update before booting:)

I can use aroma fm by flashing just one zip??
[Galaxy S II Original Android Development] pamarakos:
One pic with the message is what nfs sfift gives me
[Galaxy S II Original Android Development] pamarakos:
Sorry...found how to start aromafm in recovery:) thanks
[Galaxy S II Original Android Development] toonarmy4life:
Could anyone tell me if siyah 5.0.1 is compatable with this rom aokp_i9100_jb-mr1_build-6.zip

Thanks
[Galaxy S II Original Android Development] bogdan1980:
Pamarakos, i never seen that. You use custom rom? Try with another kernel or rom.
[Galaxy S II Original Android Development] pamarakos:
Im on cm10.1 official...since its happening only in antutu and nfs shift...i wont break my head with it...just would be good to know if someone had any idea...

Thanks
[Galaxy S II Original Android Development] bogdan1980:
cm10.1 use mali v2 drivers, right? If so, try dorimanx 9.x or def cm kernel.
[Galaxy S II Original Android Development] Bartidesigns:
So Siyah v6.0b5 will not work on CM 10.1? :(((
[Galaxy S II Original Android Development] bogdan1980:
Maybe will work. I'm on neatrom, an mod of official rom.
[Galaxy S II Original Android Development] Bartidesigns:
Myślisz że zadziała? Warto próbować? Czy nie ryzykować? Pozdrawiam.

EN: You think it will work? Or there is a risk to brick phone? Regards
[Galaxy S II Original Android Development] bogdan1980:
Polish or what? Download dorimanx v9, install siyah in cwm. If you receive bootloop, enter cwm and flash dorimanx.
[Galaxy S II Original Android Development] marc.knuckle:
I flashed siyah 6 b5 today. After messing in stweaks following some settings posted on here my led touch lights won't go off. I have turned off the led setting in the rom and also the bln setting in stweaks but it still doesn't help and the lights just stay on. I have rebooted numerous times and no good.

Edit... I have found that after turning those settings off and turning screen off and on that turns them off. But i like them briefly coming on when i press but it doesn't work when i select 1.5 seconds for example. It is a Samsung based rom.
[Galaxy S II Original Android Development] asd1301:
hi .. i'm still on android 4.0.4

what's the LATEST kernel i can download ? (can i have a link?)

10x !

:)
[Galaxy S II Original Android Development] parag1dubey:
Siyah 5.0.1. Www.gokhanmoral. Com
[Galaxy S II Original Android Development] Tungstwenty:
On Samsung ROMs the normal rom setting won't work.

Go into STweaks, BLN tab, and select a value from the LED_TIMEOUT other than "Use ROM defaults", for instance 1s.

Note that this has nothing to do whether you use BLN or not, it's just on that tab since it's related with the backlight of the softkeys.
[Galaxy S II Original Android Development] marc.knuckle:
thanks, that sorted it
[Galaxy S II Original Android Development] motoman992:
can i use this kernel with official cm10.1 ?