[Samsung Galaxy SL i9003] loSconosciuto:
These kernels are for CyanogenMod 10 - Alpha 4.

The goal of these builds is to fix the issues with phone signal, which is not properly working with the stock kernel. Nothing was changes, no extra features, no nothing.

There won't be any more "development" now that the bug is fixed.

The experimental sync bug fix, as the name says, it's a new sync bug fix I was testing. It's here because it partially fixed the missing signal issue at first, but it's not the real fix.

Downloads:

kernel-cm-10-A4-signal_fix.zip: dhiru's kernel + signal fix [0001, 0002] - (previously known as V1)

kernel-cm-10-A4-signal_fix-exp.zip: experimental sync bug fix [0003, 0004] + signal fix [0001, 0002] - (previously known as V2)

kernel-cm-10-A4-restore.zip: stock alpha 4 kernel.

Note: I forgot to change the "name" of the kernel, so you'll get dihuri1602@ICS_CM9. Don't worry, it's for CM10

Even though I marked V2 as experimental build and I added it as alternative choice, it's the most downloaded version.

As I reported several time ago, mobile data is maybe less stable with it and I think it's because the PDA state is controlled with early suspend instead of the regulr suspend, as it was in the old Samsung releases. In case of problems, flash V1.

If you noticed anything, please report

Source code:

android_kernel_samsung_latona at 0e84cc4896 + patches attached, applied as indicated above.

I verified that when a stock ROM is used, GPIO 126 is normally set to 0.

If you are stuck at Samsung splash screen and you are unable to reboot in recovery (I don't know why some users are facing this issue), so you are not able to flash another kernel or restore a backup, you can try to flash one of the kernels with ODIN.

Downloads:

kernel-cm-10-A4-signal_fix-ODIN.tar: dhiru's kernel + signal fix [0001, 0002] - (previously known as V1)

kernel-cm-10-A4-signal_fix-ODIN-exp.tar: experimental sync bug fix [0003, 0004] + signal fix [0001, 0002] - (previously known as V2)

kernel-cm-10-A4-restore-ODIN.tar: stock alpha 4 kernel.

Reboot in Download mode and flash as PDA.

Kernel modules are not included in the PDA. They are not necessary if you were using dhiru's CM with no custom kernels. If you are not sure, do as follows:

Flash kernel as PDA with ODIN (assuming you are stuck at Samsung splash screen and can't reboot in recovery)

Reboot in recovery (pull the battery if nothing works and use the three-keys combo)

Flash CyanogenMod 10 zip (your data will be preserved)

Flash once again kernel as PDA with ODIN

_____

Older posts:

Update: Now I know what stock ROMs use (GPIO 126 = 0). I'll soon update the kernel.

I already wrote that this won't be a custom kernel, no extra features, overclock etc. I opened this thread simply to test a fix, that's why I opened it in the general section, even though the dev section would have been more appropriate.

I'm lazy, so read this post.

kernel V1: includes only the sec_get_param_value fix

kernel V2: includes both the first change (the reworked sync bug) and the sec_get_param_value fix

As I posted in dhiru's thread, with my kernel I catch the mobile signal faster than with the stock kernel. I don't have to wait, all I have to do is to turn off and then on the screen once.

I've recently done some changes to my kernel regarding the sync bug. So, suspecting those changes are what makes the difference, I applied the same changes to dhiru's kernel and built it.

I tried to reboot few times and there's really a difference, at least for me.

I suspect that with the stock kernel there are only issues in reporting the current intensity, because 3G and calls seem to work.

Download: (Flash from recovery)

kernel-cm-10-Alpha4-TEST.zip

kernel-cm-10-Alpha4-RESTORE.zip

Source code:

android_kernel_samsung_latona at 0e84cc4896 + patch attached + unset CONFIG_SVNET_WHITELIST

I don't know if battery life is affected, if the sync bug is really gone (no issues till now) or if there are issues with this kernel (I'm not using it. I only tested it for a few minutes). Flash at your own risk.

Don't report any bug in CM10 thread if you are using this kernel. Use the restore zip first, try to reproduce the bug and then report.