yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Player 4.0, 5.0] KOala888:
I know what can/should have been done, I simply would like to know which files EXACLY should be changed. But I can examine it later on my own if nobody knows ;)

seems like I have finally found proper way of compiling kernel, so probably I will make overclocked cpu&gpu etc. kernel for jb.

What is more we have better 3d performance there, comparing to paranoidandroid +5fps in nenamark while cpu is 200mhz lower! Can't wait to test some extreme frequencies like 1.8
[Samsung Galaxy Player 4.0, 5.0] DZonikg:
if you know maybe you can modify key table and for us with international device.

And 1.5 ghz is just enough..after that you need much more voltage witch meens less batery and a lot off heat
[Samsung Galaxy Player 4.0, 5.0] KOala888:
softkeys are ok for me, but I will do it later.

Yup, more just for testing. Ok guys keep to the topic ;)

Doesn't boot...

That is what I have made:

-downloaded your sources

-make modules

copied modules to initramfs/modules

-make CONFIG_INITRAMFS_SOURCE=Path to initramfs file

-made .tar and flashed by odin as pda

what's wrong?
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
Sorry, I was kinda making it general because I wasn't sure haha

Sparx639
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
You made a tar of the zImage, right?

Modules are on system partition, so not in initramfs.

Also, make sure you delete all of the EMPTY_DIR files and that things like init are executable.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Does the home key still not work on Alpha 4?

I'll gladly fix it if someone told me what I needed to do.
[Samsung Galaxy Player 4.0, 5.0] DZonikg:
Non key work..maybe you could send pm to noisyfoxs ..he made change in ics kernel ..i thing is just some change off key codes in some key table.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
So everything is allright except copying modules to initramfs? should I copy them to system or not?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
If you didn't modify them, (wi-fi driver, cifs driver), then you don't need to copy them.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Here is the error I got:

koala888@koala888-VirtualBox:~$ cd android/kernel/jb
koala888@koala888-VirtualBox:~/android/kernel/jb$ export ARCH=arm
koala888@koala888-VirtualBox:~/android/kernel/jb$ export CROSS_COPILE=~/android/kernel/toolchains/arm-eabi-4.4.3/bin/arm-eabi-

koala888@koala888-VirtualBox:~/android/kernel/jb$ make venturi_usa_defconfig
#
# configuration written to .config
#
koala888@koala888-VirtualBox:~/android/kernel/jb$ make -j2 CONFIG_INITRAMFS_SOURCE=~/android/kernel/jb_initramfs
CHK include/linux/version.h
CHK include/generated/utsrelease.h
CC scripts/mod/empty.o
cc1: error: unrecognized command line option ‘-mlittle-endian’
cc1: error: unrecognized command line option ‘-mapcs’
cc1: error: unrecognized command line option ‘-mno-sched-prolog’
cc1: error: unrecognized command line option ‘-mno-thumb-interwork’
scripts/mod/empty.c:1:0: error: unknown ABI (aapcs-linux) for -mabi= switch
scripts/mod/empty.c:1:0: error: bad value (armv5t) for -march= switch
make[2]: *** [scripts/mod/empty.o] Error 1
make[1]: *** [scripts/mod] Error 2
make: *** [scripts] Error 2
make: INTERNAL: Exiting with 3 jobserver tokens available; should be 2!

Got it after extracting kernel sources and initramfs, and trying to compile. I haven't added any changes. As you can see I use arm-eabi-4.4.3
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
I've gotten this error a lot while compiling. What you need to do is set the "CROSS_COMPILE" variable to the full path of the toolchain. (not ~/some/directory). Also make sure the path is not enclosed in quotes ('/path/to/toolchain'). Also make sure you put "arm-ebai-" on the end of the path.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
So did I, error again

koala888@koala888-VirtualBox:~/android/kernel/jb$ export CROSS_COPILE=android/kernel/toolchains/arm-eabi-4.4.3/bin/arm-eabi-
koala888@koala888-VirtualBox:~/android/kernel/jb$ make -j2 CONFIG_INITRAMFS_SOURCE=android/kernel/jb_initramfs
CHK include/linux/version.h
CHK include/generated/utsrelease.h
CC scripts/mod/empty.o
cc1: error: unrecognized command line option ‘-mlittle-endian’
cc1: error: unrecognized command line option ‘-mapcs’
cc1: error: unrecognized command line option ‘-mno-sched-prolog’
cc1: error: unrecognized command line option ‘-mno-thumb-interwork’
scripts/mod/empty.c:1:0: error: unknown ABI (aapcs-linux) for -mabi= switch
scripts/mod/empty.c:1:0: error: bad value (armv5t) for -march= switch
make[2]: *** [scripts/mod/empty.o] Error 1
make[1]: *** [scripts/mod] Error 2
make: *** [scripts] Error 2
make: *** Waiting for unfinished jobs....
koala888@koala888-VirtualBox:~/android/kernel/jb$

EDIT: seems to compile with arm-eabi-linao-4.6.2

Well it says (linaro4.6.2 used) that zImage is ready but there is no zImage in the folder.....

any ideas guys ;c?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Those error messages are your x86 compiler telling you it can't compile ARM code. Instead of

export CROSS_COMPILE=~/path/to/toolchain
make -j2

you need to put it on one line like

CROSS_COMPILE=/home/user/path/to/toolchain make -j2
[Samsung Galaxy Player 4.0, 5.0] KOala888:
without using initramfs?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
With. Add that to the command too :)
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
I think this error is mostly because he made a typo. we can see that he wrote CROSS_COPILE and not CROSS_COMPILE.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Or that :facepalm:
[Samsung Galaxy Player 4.0, 5.0] aznflawless:
Would I be able to use alpha 4 as a daily driver rom? I use it for internet and music use only. It says storage is fixed, Idk if the sound is still really fast.
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
Wait until sound is fixed, its not a hard fix so it won't be that long until it is.

Sparx639
[Samsung Galaxy Player 4.0, 5.0] KOala888:
SO I typed:

koala888@koala888-VirtualBox:~/android/kernel/jb$ CROSS_COMPILE=/home/koala888/android/kernel/toolchains/arm-eabi-linaro-4.6.2/bin/arm-eabi- make -j2 CONFIG_INITRAMFS_SOURCE=/home/koala888/android/kernel/jb_initramfs

and still both for arm-eabi-linaro-4.6.2 ang arm-eabi-4.4.3 NO zImage prestent in folder -.-
[Samsung Galaxy Player 4.0, 5.0] Supermaster34:
Could someone try turning on Bluetooth and sending me the Logcat? I think I have an idea on how to fix it.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Here you go (yes that's it):

D/BluetoothAdapterStateMachine( 293): HotOff process message: 1
D/BluetoothAdapterStateMachine( 293): Bluetooth state 10 -> 11
I/ActivityManager( 293): Start proc com.android.bluetooth for broadcast com.android.bluetooth/.pbap.BluetoothPbapReceiver: pid=1275 uid=10003 gids={3003, 3002, 3001, 1015, 1028}
I/ActivityThread( 1275): Pub com.android.bluetooth.opp: com.android.bluetooth.opp.BluetoothOppProvider
D/BluetoothMasReceiver( 1275): Bluetooth STATE CHANGED to 11
W/ThrottleService( 293): unable to find stats for iface rmnet0

Edit: I think the error is due to this in dmesg:

<3>[ 103.398079] Bluetooth: hci0 command tx timeout
<3>[ 104.405849] Bluetooth: hci0 command tx timeout
<3>[ 105.409807] Bluetooth: hci0 command tx timeout
<3>[ 106.413699] Bluetooth: hci0 command tx timeout
<3>[ 107.421481] Bluetooth: hci0 command tx timeout
<3>[ 108.425377] Bluetooth: hci0 command tx timeout
<3>[ 109.429275] Bluetooth: hci0 command tx timeout
<3>[ 110.433175] Bluetooth: hci0 command tx timeout
<3>[ 111.437079] Bluetooth: hci0 command tx timeout
<3>[ 112.440992] Bluetooth: hci0 command tx timeout
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
You need to export the CROSS_COMPILE so make EXPORT CROSS_COMPILE="/path/to/toolchain" (with the quotes)
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
I think I found an essential part to fixing the camera problem. I was looking around in some custom ROMs for the Player 5.0, and I found an APK file called "CameraFirmware.apk" in /system/app. This, with the libs/firmware files found here: http://goo.im/devs/gmillz/venturi_usa/files could give us a working camera. I have not tested this (I use my Player regularly, so I don't like to flash much), so please say whether this works or not. "CameraFirmware.apk" is attached to this post. Also you must put this APK in /system/app in the ZIP then flash, if you try to copy it using terminal emulator (as shell is denied root permissions over ADB), it will become corrupted.
[Samsung Galaxy Player 4.0, 5.0] Supermaster34:
Is this from a GB ROM? I'll give it a go in a bit
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
Yes, it is from a GB ROM.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
well compiled but zImage is like 4.2mb and ofc does not work.

Could anybody be so helpful and write for me commands which should I put in terminal to compile that kernel...?
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
It is because initramfs was not compiled with it. You must put the contents of initramfs in /source-dir/kernel/usr/initramfs. If this directory does not exist, just create it. Then run

export CONFIG_INITRAMFS_SOURCE=kernel/usr/initramfs

and then

make -j8 && cp -a $(find . -name *.ko -print |grep -v initramfs) kernel/usr/initramfs/lib/modules/ && make -j8

It should compile a working zImage.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
I have to write it like this to compile:

make -j2 CONFIG_INITRAMFS_SOURCE=~/android/kernel/jb/usr/initramfs && cp -a $(find . -name *.ko -print |grep -v initramfs) ~/android/kernel/jb/usr/initramfs/lib/modules/ && make -j2 CONFIG_INITRAMFS_SOURCE=~/android/kernel/jb/usr/initramfs

zImage is 4,9m so it is better in these terms

made .tar in ubuntu, send to windows, and after flashing via odin as PDA it doesn't boot

samsung logo for a while and blacscreeen
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
Send me your changes and I will try to compile, I use a physical Linux machine, so that may help.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
problem is that I haven't done any changes yet, simply trying to compile from source befere adding changes, as always ;)
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
Just s quick question, if I install SafeStrap recovery will it brick my Player?

EDIT: MAYBE THIS IS WHAT MIGHT FIX SOUND http://xdaforums.com/showthread.php?t=1784043
[Samsung Galaxy Player 4.0, 5.0] Supermaster34:
This looks promising. I'll see if I can find my player to test it on
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Didin't the CM10 zip you have contains this? If not then this could possibly work (it suggests the codecs of the build itself. The one you need is preferably the google one which is the generic codec.)
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
I got it to compile, but I don't think it will boot. It says that initramfs/lib/modules/ is missing, so I think that is the problem. Here is a link to my compiled zImage: http://www.mediafire.com/?s40c1fud7uc2xw0
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
For jellybean, modules are on /system, not in ramdisk. So copying them there is unnecessary.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Then, could you please tell me what commands do you use in proper order to compile your kernel?

and which toolchains do you use?

I would be very grateful, I just would like to help you guys and add some my improvemnts
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Personally, I always compile the kernel inside the CM10 build system (so 'mka bootimage'). Therefore I use the prebuilt GCC that it comes with.

Outside the Android build system, you would run

cd ~
mkdir kernel
cd kernel
git clone https://github.com/Mevordel/android_kernel_samsung_venturi -b jellybean
git clone https://github.com/Mevordel/venturi_cm10_initramfs
cd venturi_cm10_initramfs
rm -v `find -name EMPTY_DIR`
cd ../android_kernel_samsung_venturi
export ARCH=arm
export CROSS_COMPILE=/home/username/path/to/toolchain/bin/arm-eabi-
make venturi_usa_defconfig
CONFIG_INITRAMFS_SOURCE=../venturi_cm10_initramfs make -j8

An alternative to adding the CONFIG_INITRAMFS_SOURCE variable would be to edit arch/arm/configs/venturi_usa_defconfig and fix it there.
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
I don't think this will work, since the file is already in the ROM. I did notice, however, that it is slightly different from the one included in the ROM. Someone please test this, as I don't fell like flashing my Player again. Also if someone could test my possible camera fix, that would be greatly appreciated also. To get into the camera on this ROM, just drag the lock circle to the camera icon on the lockscreen.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Sound is a kernel issue. There's nothing we can put on /system to make it work better. I'm gonna take a look at it on Tuesday
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
The thing is that by itself won't fix the camera, although it may be a part of it. The reason there's no launcher icon for it is because it cannot load the (nonexistent) camera HAL

library

, which must be ported or written from scratch, as Samsung did not give us the source for theirs.

@JackpotClavin: Right, but I haven't gotten the sound libraries (libtinyalsa, audio.*.default.so, etc.) to all build properly so sound works at all. I can copy them from the pre-alpha, and then sound works as well as it did there, but that's no real solution.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Thanks mevordel, I will try to compile it again.

Well, have anybody managed to use files from samsung galaxy tab p1000 or p1010? seem quite similar to our device....

both have 3mpx camera and 4.1.2 with all features working
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
I found a CM10 ROM for the Tab p1000: http://xdaforums.com/showthread.php?t=1774560 Maybe we could use some files from this ROM to fix some problems with our ROM?
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
I took a look at the p1000 and it seems that they are still on the 2.6.35 kernel. Plus they have a lot of functions not working. This is based on the post above me ^.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
yup they are only working on 3.0 kernel, not having it.

But there is nowhere in 4.1.2 thread said that something doesn't work so I guess everything does accually
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
From what JackpotClavin said (and I think it is a really good idea), we are going to take our 2.6.35 kernel and backport drivers and whatnot so it at least works completely, and later possibly move back to 3.x.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Instead of:

CONFIG_INITRAMFS_SOURCE=../venturi_cm10_initramfs make -j8

I had to write that to compile:

make -j8 CONFIG_INITRAMFS_SOURCE=../venturi_cm10_initramfs

Anyway kernel is 4.2 mb and doesn't boot, blackscreen after samsung logo -.-

Just compiled as you said, made tar and flashed as pda in odin
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
I thought you guys were already on a 3.0 kernel? It is a good idea though but what about hw acceleration? I thought I read that you needed a 3.0 kernel for that

Sparx639
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
We are, but updating certain parts of a working kernel is a lot easier than adding hardware support to a new kernel. And new drivers can be backported to 2.6.35 - that's what team Supernova did.

@KOala888 look in android_kernel_samsung_venturi/usr for initramfs_data.cpio. How big is it? Is it there at all?
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
That sounds like the easiest way to go about it but I'm a n00b so I don't have any say in this :D

Sparx639
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Also, and probably most importantly, using 2.6.35 headers allows us to use Samsung's proprietary modules, and that keeps us from getting stuck in recovery.
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
I know nothing of kernels, save for a few elementary aspects. But, if you backported drivers to 2.6.35, would that eliminate kernel 3.x functionality (such as hardware acceleration, etc...)?
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
The idea of backporting is that the 2.6.35.7 (stock) had everything working. If we take the hardware acceleration and bring it to the 2.6.35.7 kernel, it eliminates the missing functionality. The backported kernel is a temporary thing till the 3.0 kernel is fully working. I've got a full hw acceleration kernel going right now on my galaxy player with the backported hardware acceleration pvr drivers into the 2.6.35.7 kernel. The only thing is that sound is still not working as I wanted it to work. The best rom we ever hard that had full sound still has to be the CM9 one. Until I can figure out why our audio libraries don't work with CM10 but with CM9, we might only have CM9 for the time being (for those who want sound)
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
So, for those of us that are okay with CM9, at the moment, is the backported 2.6.35.7 kernel compatible with CM9? Also, is there a way to find some working camera libs for the backported kernel that could be ported up to 3.x later?
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
I'll see what I can do tomorrow. I have a CM9 build from around September so I'll use that to see if I can get anything going in regards of the camera. Worst comes to worst, tomorrow we will have our first ROM for the galaxy player that has full hardware acceleration and sound albeit it's gonna be CM9 not 10
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
Again, sir, you never fail to impress.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Awesome! Source please? ;)

Does this new kernel work with CM9, 10, or both? If you're on CM10, which ROM? I know there are sould library issues in all of my builds at least - tomorrow or Wednesday I'll work on that and sensor libraries (basically all of lib/hw). I'm trying to pull stuff from both aries and your CM9 device tree. One thing useful I did find is that the alsa libraries and configuration are not proprietary - the source is in Samsung's opensource platform zip, but the makefile needs to be fixed. I noticed in hardware/cm there's a legacy audio library; maybe that's useful, maybe not. I tried using the audio folder from aries-common, but it needs audio.a2dp.default, audio.usb.default, and libtinyalsa, which should be there, but never build; I guess I need to do more investigating. The other option is to update the folder from the CM9 tree, but I don't really understand what you did there.

Also, out of curiosity, which ramdisk method are you using? Which do you think is better?

And, of course, at the worst time, I seem to have broken something - my builds today bootloop - so don't use today's changes, or maybe try going back to the phone config or removing the overlay. (Not that anyone else is building of my device tree, but just in case)
[Samsung Galaxy Player 4.0, 5.0] KOala888:
It has 3.8 mb

When I used

there was some error related to that file
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
That's the compiled ramdisk, so I have no idea why your kernel build doesn't work. I'm stumped.
[Samsung Galaxy Player 4.0, 5.0] noisyfox:
Good job. I'll try this way using your current source and continue the patch.
[Samsung Galaxy Player 4.0, 5.0] cvcduty:
Wow... looking at all the messages in this threads, it seems that we have all the heavy weights of this forum participating to make the 3.x kernel working for the 5.0 player. This is fantastic and very encouraging.

I am clueless when it comes to dev work but I can certainly help test when it's appropriate.

I have both the US and INT versions so I would be willing to "kick the tires" a bit with your builds when needed.

Thank you all... :laugh:
[Samsung Galaxy Player 4.0, 5.0] alljokingaside:
ditto as the previous poster. you guys rock
[Samsung Galaxy Player 4.0, 5.0] noisyfox:
Well I have one big question. If there are some extra lines just lie in the patch rejections, what should I do? If I keep these lines the patch will fail but I don't know whether these codes are useless.

---------- Post added at 07:08 PM ---------- Previous post was at 07:06 PM ----------

Should I just ignore it and fix it manually after apply the patch?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
It depends on how you want to go about it. One option is to patch first (which I may end up doing) and manually fixing conflicts later, which is all failures are. The other option is to take out the extra lines, even though sometimes they aren't useless, so the patch will succeed, and put them back as needed.
[Samsung Galaxy Player 4.0, 5.0] noisyfox:
I get it. I've fixed some file and sent you a pull request. Check it whether I had done right.:o
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Pulled. Good work, thanks :thumbup:

I'll see what I can do for the more confusing ones probably Friday.
[Samsung Galaxy Player 4.0, 5.0] noisyfox:
Ur... It's totaly different between sound/soc/codecs/wm8994.c and the patch file. I don't have any idea about it.

---------- Post added at 04:30 PM ---------- Previous post was at 04:09 PM ----------

sound/soc/codecs/wm8994.h does not have any trouble... Just because the encode of this file is the form of windows. It has \r\n at the end of each line but the patch just has \n so it will fail.
[Samsung Galaxy Player 4.0, 5.0] noisyfox:
I don't know why there is always a rejection in drivers/mmc/core/sdio.c. I've compared it serval times but just don't know what's wrong.

Maybe we can ignore it and apply the patch amnually.
[Samsung Galaxy Player 4.0, 5.0] spartacus279:
It looks like the list and bugs is getting way smaller, great job guys!!!

I have both a us and int 5.0 to test once your done if you want!!! :)
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
This is the easy part. Once we patch, we still have to get it to compile :)
[Samsung Galaxy Player 4.0, 5.0] omaroe666:
awsome you guys rock!!!! finally we allmost can use camera on ics :victory:
[Samsung Galaxy Player 4.0, 5.0] noisyfox:
Well we still have a long way to go. Once we can successfully apply the 2.6.36 patch to our kernel, we still need to change a lot of (maybe) codes to make it boot. And then 2.6.37 and 2.6.38. Then update to 3.0.

And debug a kernel is difficult because we don't have logcat for kernel.
[Samsung Galaxy Player 4.0, 5.0] omaroe666:
that's allright i just think you guys do a great job ;) keep going on guys:D
[Samsung Galaxy Player 4.0, 5.0] KOala888:
I spotted that we don't have logcat. ATM I am noob at kernel development but I want to add some features to available kernels. Can a logcat be added to?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
The kernel equivalent is dmesg. It's very useful, except of course if the kernel doesn't boot at all.
[Samsung Galaxy Player 4.0, 5.0] noisyfox:
yeah i just afraid of that it can't boot
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
I'm afraid of that too... as it is, it doesn't even come close to compiling.

Just as a little side project today I decided to upgrade from 2.6.35 to the latest long-term-support version, 2.6.35.14.

It worked pretty well and boots fine (except no adb). Attached is the patch log. zImage is linked from OP.
[Samsung Galaxy Player 4.0, 5.0] noisyfox:
Just applied the patch and didn't fix the rejection?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Yep. But fixing it's probably not a bad idea. That may be why advanced doesn't work.

In other news, patching to 2.6.36 doesn't look like it will ever compile or boot (at least from what I can see), so I think I'm going to leave it up to JackpotClavin's slow but sure method of cherry-picking. In any case, I still hope you guys get the kernel working well and that my small contribution helped you.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Thanks. I will paste that error later maybe it would help. If not, maybe I will make fresh install of ubuntu

Compiling gingerbread gives same result-no boot.

Wouldn't kernel compiled without initramfs work?
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
For some odd reason, Netflix does not play in my CM9 2.6.35.7 kernel with hardware acceleration. I've got Chrome working fully, and to my knowledge, all other hardware acceleration aspects things working (youtube) but for some reason or another, I cannot get Netflix to work. Sound works as it was expected to and even the hardware composer works from the Galaxy S devices to make it even smoother. As soon as I get Netflix sorted out, I'll post a zip