yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] mazen1990:
different hardware? I thought that the hummingbird processor and gpu on the sgs and nexus s are identical, arent those the most important factor? or is the Inand/MOVInand difference that important.

In all honesty all I want to know is that is it possible that our GT i9000 will perform as well as or at least close to the NS if the devs can get gingerbread running on the sgs. I keep on reading all these other topics on how the NS cpu scores pretty high on quadrant advance scores, while the sgs cant even manage to get 25% of what the NS is getting.
[Nexus S Android Development] DebauchedSloth:
Confirmed. Reverting to stock fixes bluetooth.

Bummer. :(
[Nexus S Android Development] Anderdroid:
Bluetooth :'( Have to go back. Now... How do I go back?
[Nexus S Android Development] DebauchedSloth:
You flash this:

http://koush.tandtgaming.com//samsung/herring/rootboot.img

From here:

http://xdaforums.com/showthread.php?t=875875
[Nexus S Android Development] annihilist:
Yup, bluetooth is le broken with modified kernel.
[Nexus S Android Development] slowz3r:
I'm all for rooting my device and installing kernels and such, but at this point i think its way too early to sacrifice my device :)

I think ill make the jump when CM Alpha or Beta hits the NS
[Nexus S Android Development] krumb:
agreed. i've had the phone for just over a day.

once the process has been perfected, along with modifications, THEN i will maximize it's power.
[Nexus S Android Development] supercurio:
Hi, thanks for the bluetooth error report.

I used a very conservative approach (use the stock zImage, and a slighly modified ramdisk) but it seems it wasn't safe enough - strange.

I'm gonna try to find what causes the bluetooth issues.

Not so easy without a test device, but I'll give it a shot.
[Nexus S Android Development] supercurio:
Errors are random and appear only when activating / deactivating bluetooth.

My current hypothesis is that it's the CyanogenMod mkbootimg i have fault, I'm grabbing Gingerbread AOSP source to check
[Nexus S Android Development] madfarmer:
My quadrant stops during 3d test and it doesnt load textures.. Could this be kernel related ?
[Nexus S Android Development] pigs3littleones:
BT broke. I don't notice a difference but the phone is fast out of the wrapper so I am not surprised by that.

I can't get quandrant to run. Stock or this kernel. Starts the 3D tests. No textures at all in the halls, planet and moon are plain white, then it dumps me back to the run benchmark menu. Uninstalled/Reinstalled etc..
[Nexus S Android Development] madfarmer:
Puh.. I'm not the only one.. Any ideas what this might be ?
[Nexus S Android Development] ogdobber:
Seems Quadrant doesn't play well with GB...the app needs to be updated
[Nexus S Android Development] madfarmer:
But it works for others :/
[Nexus S Android Development] madfarmer:
Well my phone just finished quadrant for the first time.. Still no textures in 3 tests and a score of 1678 without vodoo mount options..
[Nexus S Android Development] ranxoren:
Hey guys so im super interested in trying this however I have a question.

When I do this on my Nexus S, is it going to wipe it back to Stock ? If not what is it going to modify besides the kernel ? Does it make all my apps and settings go away (I made a Titanium backup) ?
[Nexus S Android Development] Bo$s:
Please someone post a result of mount command (or busybox mount). Thanks :)
[Nexus S Android Development] Anderdroid:
No wipe.

And as for Quadrant, it's like that for everyone. You simply need to keep running Quadrant over and over again until it works. It eventually will.
[Nexus S Android Development] unremarked:
EDIT: Seemed to be an issue with my desktop. I was able to flash this from my netbook. Very odd.
[Nexus S Android Development] madfarmer:
Sweet.. Nice to know..
[Nexus S Android Development] ranxoren:
Cool thanks for the update :)
[Nexus S Android Development] pigs3littleones:
I'll wait for an update. Without loading textures even if it completes I wouldn't consider it valid.
[Nexus S Android Development] ranxoren:
So i just flashed this and it might all be in my head but i feel like it improved my Wifi reception by a LOT
[Nexus S Android Development] brian6685:
Would this change battery life at all?
[Nexus S Android Development] k0mpresd:
C:\Users\k0mpresd\Desktop\phone\G2TempRoot>adb.exe shell
$ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock6 /efs yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/platform/s3c-sdhci.0/by-name/system /system ext4 ro,relatime,barrier=
1,data=ordered,noauto_da_alloc 0 0
/dev/block/platform/s3c-sdhci.0/by-name/userdata /data ext4 rw,nosuid,nodev,noat
ime,barrier=1,data=ordered,noauto_da_alloc 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:3 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:3 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
$
[Nexus S Android Development] brian6685:
So I have been using this kernel for about a day and everything seems to be running smoothly. are there any downsides/dangers to running this other then Bluetooth not working?
[Nexus S Android Development] ranxoren:
+1 on this affirmation and question
[Nexus S Android Development] supercurio:
As it's the same exact kernel code, this is unexpected ;)
[Nexus S Android Development] supercurio:
Exact same battery life, or extremely slightly better, as the filesystem driver becomes a tad more efficient ;)
[Nexus S Android Development] supercurio:
As far as I know, None.

The issue is actually quite disturbing, and I will report it properly to Google as soon as possible.
[Nexus S Android Development] brian6685:
Okay :) thanks for the reply.
[Nexus S Android Development] Khoral:
Do you know what's the model of the BT chip embed in the phone ?

Cause if it's another time a Broadcom thing, you'll perhaps get stucked with their closed drivers :/ Hope not.

BTW, gj for achieving this kernel, frenchies rock :D

Edit : I'm at work now, so I'm doing git diff by switching between webpages, and it's painful :'(

Anyway, wouldn't it be worth the try to make 2 new kernels, each one with only one noauto_da_alloc (one on /system, one on /data) and see if one of them make BT goes on again.

If yes, that would help to center on the source of the problem :)
[Nexus S Android Development] ranxoren:
haha its probably just in my head then but i definitely my Wifi Bars a lot fuller since
[Nexus S Android Development] supercurio:
Yeah we debugged it already on IRC #NSdev, and the result was the same.

The BT issue is totally unrelated to the tiny changes I made, and is also present

using an unmodified initramfs.

Hard to tell right now without Nexus S device :D

I can't wait to publish updated kernel later.
[Nexus S Android Development] dudeimgeorge:
Is there a way to flash this without connecting to the computer?
[Nexus S Android Development] Khoral:
I'll seriously think of joining you guys there, following you on twitter isn't sufficient anymore :D

Well, I wonder how DebauchedSloth got it back then :/ That's a really strange issue.

Can't wait for your publishing too, I'm learning much by following you and the others devs :D (and perhaps one day, I'll do the same things \o/ hopefully)
[Nexus S Android Development] DebauchedSloth:
Don't know. It was 100% reproducible and 100% solved by going back to stock - and as you can see, was a pretty nasty beast. Would very much prefer to be running this kernel, but I need BT.

Definitely think the drivers are not yet 100% stable on this device. That BT panic should not have happened; quadrant should not crash in the driver the way it does, etc.
[Nexus S Android Development] Koush:
Supercurio, please check out AnyKernel. It allows you to replace just the zImage in a user's boot image (does not touch the ramdisk).

It's basically become the standard way to package custom kernels. Custom ROMs often need custom ramdisk, and this kernel distribution method works with any custom ROM.

https://github.com/koush/AnyKernel
[Nexus S Android Development] zdiddy14:
Im getting can not load Nexus-S-stock+Voodoo+root-kernel-1.0_boot.img... any idea what I'm doing wrong?

Never mind I fixed It. :)

Quadrant went from 1655 to 2299. But Bluetooth bug is on mine too...

Linpack is the same but I expected that. Very good work though!
[Nexus S Android Development] vapor311:
By dead here as well
[Nexus S Android Development] supercurio:
Hey, but that's awesome, I will try that thank you.

However it still don't explain the bluetooth error, but that's cool.

Also, i asked Brian Swetland.
[Nexus S Android Development] graemegb:
quadrant score: 2301! WooHoo! thanks!
[Nexus S Android Development] supercurio:
I'm happy people are happy, even if starting a new Quadrant competition was everything but the goal of this :)
[Nexus S Android Development] graemegb:
slightly faster than stock.
[Nexus S Android Development] madfarmer:
This forum really needs a like/dislike feature :) anyways.. Nice work superc.. Glad to have you as one of the pioneers on the nexus.. Your work on the SGS was awesome, though i changed to speedmod later on, i was aware that is was building on your work.. And im sure you'l find some way of improving the NS.. looking forward to see what the voodoo kernel brings..
[Nexus S Android Development] hansmrtn:
Works great! Keep it up! :D
[Nexus S Android Development] graemegb:
I'm actually getting more free RAM after flashing this. 156 compared to 37.
[Nexus S Android Development] Break Action:
Help me please i getting error while turning on Wi-Fi. How to fix it?

PS: When i used stock boot wi-fi work good.
[Nexus S Android Development] k0mpresd:
you are trying to use this 2.3 img on a 2.3.1 firmware phone? use the boot.img i posted in my thread. it has supercurio's hack integrated and is for 2.3.1.
[Nexus S Android Development] Break Action:
Thank you very much!
[Nexus S Android Development] RinTinTigger:
Is there a STOCK Kernel, if i want to revert back?
[Nexus S Android Development] gotgadget:
How do I flash
[Nexus S Android Development] RinTinTigger:
read the first post?!?!?

BTW: Camera NOT working for me on this kernel!
[Nexus S Android Development] MrNameless:
Guys, error while turing on wifi :(
[Nexus S Android Development] jthornton71707:
Every time I've flashed this kernel I get the wifi error afterwards. Any help??? Ive tried w cm7 and stock and both I have no wifi
[Nexus S Android Development] k0mpresd:
did you people actually read the thread? lol
[Nexus S Android Development] jthornton71707:
What thread is this? there is nothing in the OP saying 2.3 or 2.3.1?
[Nexus S Android Development] jthornton71707:
sorry, so i found the thread... flashed it and im still getting the wifi error... any suggestions???
[Nexus S Android Development] andyandrwew:
gettin some wifi trouble and camera trouble is confirmed
[Nexus S Android Development] Zenoran:
hm still no stable kernel?

seems like a trivial thing on the surface... expect someone to have this shot all over the place. :)
[Nexus S Android Development] Magikman74:
Getting the wifi error also. I can live without the Bluetooth.. but wifi is another story.
[Nexus S Android Development] maliciousmunky:
I too am having the wifi error ( i had it before kernel, after i rooted it) and now bluetooth and camera dont work ...

what now?
[Nexus S Android Development] chaval:
Thx

Boots fine with 2.3.3

Quadrant around 2200

Good to have Voodoo sound back.
[Nexus S Android Development] nicholasbgr:
Just flashed, great to have voodoo sound back <3

On the OP didn't you mean:

fastboot flash [b]boot[/b] Nexus-S-Voodoo-latest.img

?
[Nexus S Android Development] reddv1:
Flashable Zip in Clockwork Mod

I put the latest kernel posted in the OP in a flashable zip for Clockworkmod for people that would rather flash the kernel that way. Here's the link NexusS-2.3.3-GRI40-stock-voodoo-kernel-CWM.zip
[Nexus S Android Development] barmanham:
Everything seems to be working for me wifi camera not sure about BT

edit: spoke to soon its up but not working ugh the wifi

edit edit: ok after a reboot wifi is now working
[Nexus S Android Development] ogdobber:
everything works. my post about broken bt was on a version long ago, check the date...
[Nexus S Android Development] barmanham:
Huh? You sure you are in the right thread?
[Nexus S Android Development] ogdobber:
look at the date /\ /\ jan 6th

or an earlier post by me post 17 dec 16

this is a resurrected thread that "supercurio" started some time ago;)
[Nexus S Android Development] barmanham:
ah wow it all makes sense now lol
[Nexus S Android Development] CB620:
flashed for 2.3.3 how do i get the vibrant colors back i went in the color profile and ticked the circle underneath the first one. now what do i do.
[Nexus S Android Development] MadFerIt2011:
Supercurio,

Thank you so much, I absolutely love the improved colour profile. My only suggestion is to give us the option of switching to the 2.3.3 colour temperature in addition to the original/voodoo.

Also, can you please do some sort of versioning with your releases? It's hard to determine when you've updated the kernel if there's version associated.

Thanks again for the hard work!
[Nexus S Android Development] terryhau:
When i first got the Nexus S, i straight away thought the colors were a bit too saturated. I think the new 2.3.3 colors are more correct, and people only think it looks washed out because they're too used to the old profile.
[Nexus S Android Development] supercurio:
Switching back and forth to 2.3.3 colors is impossible (or say, complex to code) because of changes in the driver code itself.

But fortunately 2.3.3 color driver is written properly, and it should be possible to build an accurate color profile on the new code.
[Nexus S Android Development] Nutsonfire:
Thanks for the super job! Couldn't stand these new colors.

Un admirateur de Genève^^
[Nexus S Android Development] MadFerIt2011:
Thanks for the information! It would be nice to see a colour profile on the 2.3.3 driver, more stability either way (noticed a few bugs her and there with this kernel).
[Nexus S Android Development] no_one_can:
many thanks for your 2.3.3 with the original color profile
[Nexus S Android Development] brian6685:
Just to be clear I'm on stock 2.3.3 and I like the new colors with it. Can I use this without changing the colors? I want the voodoo sound... also does the wifi and bt work? I was reading and some people are saying yes and some no? Thanks for the work super
[Nexus S Android Development] mhaedo:
Use ogdobber's build from the following thread http://xdaforums.com/showthread.php?t=949292
[Nexus S Android Development] ogdobber:
everything works excellent. check the dates on those post...
[Nexus S Android Development] brian6685:
Okay, thanks.
[Nexus S Android Development] mingkee:
I finally bit the bullet and unlock the bootloader (fastboot oem unlock) and flash this image file.

Lo and Behold, the color is back!

The every bit of it is close to Nexus One and MT4.
[Nexus S Android Development] jlevy73:
Now that looks great. I thought the colors on 2.3.3 looked good but these are just amazing. The yellow hue to the whites are gone. Well done sir, and 2700 on quadrant ain't bad for a stock kernel :)
[Nexus S Android Development] sevet:
Can you please make the tun and cifs modules? I need the tun module for openvpn
[Nexus S Android Development] asci:
Hi all,

I just flashed last kernel but now my wifi is broken, while BT seems to work fine. How to solve it?

THX!
[Nexus S Android Development] MadFerIt2011:
I've been forced to switch back to stock 2.3.3 due to this kernel reintroducing a bug that was present in 2.3.2.

This leads me to believe the "init 100% CPU" bug is related to the old driver. But, I look forward to the work you're doing with the 2.3.3 driver, and I will switch to it as soon as it's available :D.
[Nexus S Android Development] MrNameless:
Wifi Broken for me too, any solutions?
[Nexus S Android Development] ogdobber:
your wifi is broken because you had flashed another kernel that replaced you bcm4329.ko located in system/modules. 3 solutions...nandroid back, flash any other kernel or push the ota bcm4329.ko in with adb
[Nexus S Android Development] supercurio:
Sorry I don't plan to add other kernel modules yet.

Current goal is "as close to the official kernel as possible" + Voodoo

It's not so bad, a lot of great other kernels have more features.
[Nexus S Android Development] nxt:
Today is the first time I've flashed this kernel (or any other separate kernel).

I've been running CM7 nightlies.

Today build 11 came out and yeah the colors look like crap on my Nexus S, so I wanted to fix that and use this kernel.

Once I fastboot flash it, and the phone boots, I get unlimited force closes for all kinds of stuff, and nothing else happens.

Any ideas? Flashing back build 11 obviously fixes it.
[Nexus S Android Development] ogdobber:
you need a kernel built for not only cm7 but 2.3.3....

Netarchy Nexus - 1.2.7-cfs-2.3.3 (CM7 2.3.3 Compatible)

or (CM7 2.3.3)og-ns-CM7-ogext4-VS-VC-1.3.3.zip
[Nexus S Android Development] no_one_can:
How can I find that I have the latest voodoo kernel? and how do I know when there is a new update?

Thanks
[Nexus S Android Development] Waza_Be:
Just installed it and got a infinite loop of FC when starting the phone.

(CM7 nightly)

Edit:

Ok, thank a lot for the info, but all these kernels are so modified.

I just prefer a "as closed as possible from stock" like supercurio did.
[Nexus S Android Development] supercurio:
Sorry profete162 so far I don't plan to support CM7, only AOSP.

To me, CM7 requiring different incompatible kernels sounds definitely wrong & poor design.

Anyway, I just updated the kernel with Voodoo sound v5!

Colors of this kernel are still 2.3.2, and you can switch of Gamma table from Voodoo Control app.

Changelog:

https://github.com/project-voodoo/linux_samsung/commit/d61f4e987f6f599eecc420044e56da5b378cdc9d
[Nexus S Android Development] :
I agree,

I think the community is much better served by you staying independent from cm7.

JD

JD

Sent from my Google Nexus Magic Wand S
[Nexus S Android Development] Waza_Be:
Thank a lot for these very clear explanations, supercurio!
[Nexus S Android Development] apreichner:
I flashed this but couldn't see a noticeable difference, while I do notice a difference from 2.3.2 to 2.3.3. Should I keep the brightness set to auto since I had manually turned it up when 2.3.3 came?
[Nexus S Android Development] jroid:
Hey supercurio, have a question regarding an issue im having on my hc to ns port. Im trying to init egl libs but i cant because in dmesg its saying it cant load driver in the kernel (bad). Any ideas? Thanks

Sent from my Google Nexus S.
[Nexus S Android Development] suksit:
Hi, could you tell me how often does the kernel gets compiled? I downloaded the latest image but the Voodoo Sound is still version 5 :confused:
[Nexus S Android Development] poyz:
I've just installed Master's Stock 2.3.3 Deodexed ROM with the Voodoo Kernel + Root. Will installing the latest kernel require a wipe/delete or can I just follow the instructions on the first post.
[Nexus S Android Development] ogdobber:
no wipe is required... but this kernel only will work with the "pure" stock rom . if you fastboot it in, you wifi will break
[Nexus S Android Development] poyz:
Ok, but Masters ROM is the stock rom (deodexed). See here - http://xdaforums.com/showthread.php?t=979851

I'm currently running the Voodoo Kernel + Root. Bluetooth/Wifi work just fine.

What do you mean by "fastboot it in". Is that what the first post suggests? Should I just stick with what I have then?
[Nexus S Android Development] ogdobber:
not aosp stock...
[Nexus S Android Development] ykphuah:
I too agree that you should save your time by working this on the stock, let others integrate your kernel into their own.

I know using the CM kernels always give me this "will this fail if I am running stock?" doubt whenever I hit a problem. Because as I know the CM kernels tend to change how the stock kernel works drastically (like enabling a toggle for the mobile data for external apps).

However I do not understand what you meant by different incompatible kernel sounds. :P Care to elaborate further for educational purposes. :)
[Nexus S Android Development] ykphuah:
I just went to stock 2.3.3, rooted it, then flashed this kernel. I am using Voodoo Control 0.10. Now under the Super AMOLED hardware control, there's only one item "Color profiles" compared to the 3 that I have when I was on NSCollab (which I believe uses netarchy's kernel).

Will I be able to use the Voodoo App to get back the "yellowish" color profiles? Basically I am interested in the speed and sound improvements of this kernel but I want to see if I am able to get used to the more "accurate" color profile.
[Nexus S Android Development] suksit:
You need to flash this in order to get the additional options.
[Nexus S Android Development] Matchstick:
BLN support coming ?

Are there any plans to incorporate support for BLN into stock versions of the Voodoo kernel in the near future ?
[Nexus S Android Development] Bandis710:
Is this kernel also for the european version with slcd (GRI54 , 9023) ? I just bought mine yesterday. Noticed the colours are not as vibrant as I was used to on my galaxy s .. But that can also be the difference between samold en slcd
[Nexus S Android Development] suksit:
Yep, it's compatible. I'm currently using this combo myself :D
[Nexus S Android Development] Bandis710:
sorry for the noob question ( I am very busy reading everything I can about the nexus s ..have it since yesterday) but suppose I do not like the kernel, how can I put back the stock kernel I have now ?
[Nexus S Android Development] belair56:
It's in the op, fastboot boot to test. It will revert when you reboot.
[Nexus S Android Development] Bandis710:
okay my mistake for missing that .. But how cn I return to stock after I did not do a test boot ? On my galaxy s, there were also a lot of kernels but I could always go back to stock kernel by flashing orginal one (eg via odin) I haven't seen a list of stock kernels in this section, or did I miss something ?
[Nexus S Android Development] simms22:
either reflash whatever rom that you are using or pull the boot.img out of the zip(of the rom you are using) and flash it via the terminal or fastboot.
[Nexus S Android Development] ykphuah:
I have ran stock 2.3.3 for a couple of days and started to like the new colors. Is there a way to only apply the voodoo sound but not the voodoo colors with this kernel?
[Nexus S Android Development] bfdream:
Could you please update this kernel image to the new v7 sound driver?
[Nexus S Android Development] bfdream:
You can download the voodoo app, and use the kernel

http://dl.project-voodoo.org/nexus-s-kernels/Nexus-S-Voodoo-color-with-calibration-tools-latest.img

You can set the stock 2.3.3 color scheme
[Nexus S Android Development] oldblue910:
I decided to try this kernel and I am blown away. I loved the new color profile in stock 2.3.3 but the Voodoo colors are even better. It's so perfectly balanced. Really shows off the Nexus S screen.

I also love the sound option to tune the speaker for music. That however may not be everyone's cup of tea since it severely cuts the high end. The audiophile in me loves the "flat" sound without the extra high end but your mileage definitely may vary.