yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] al_madd:
CM7.1+/Any Rom 2.3.4-2.3.7 NS+NS4G:

http://goo.gl/TjMg2

Lucid Yellow 3.0: (post-2.3.3 voodoo color drivers)

Stock 2.3.4-2.3.7 NS GSM:

http://goo.gl/xZksA flash in CWR

CM7.1+/Any Rom 2.3.4-2.3.7 NS+NS4G:

http://goo.gl/4TDt8

any rom kernel can be use MIUI ROM right??are we having misscommunication here??:confused::confused::confused:
[Nexus S Android Development] doc_v15:
Thats what I wanted! Thanks bro!
[Nexus S Android Development] treUse:
Thank you, was waiting for something like this. Also liking th new name of the kernel :)
[Nexus S Android Development] snandlal:
@ reddv1......got everything setup. Could you explain how to change the kernel to pre 2.3.3? I really want these colors in matr1x. Thanks
[Nexus S Android Development] reddv1:
I'm assuming you already setup AOSP following the guide I posted earlier.

1. Setup git:

OK, first register an account on github and setup git by following this guide: http://help.github.com/linux-set-up-git/

Second, go to Mathkid's kernel repo at https://github.com/mathkid95/linux_samsung and fork his repo.

2. Setup local repo:

Now you have to set up your local repo by cloning your github repo to your PC:

First, open terminal and CD to mydroid directory by typing

cd ~/mydroid

Next, clone your repo by typing the following in terminal

git clone git@github.com:snandlal/linux_samsung.git

assuming that's your github username. This will take about 10 minutes as it downloads.

Next, setup mathkid's github repo, so your local repo stay up to date with all the changes he makes.

In terminal type

cd ~/mydroid/linux_samsung

this will cd to your local repo.

Then

git remote add upstream git://github.com/mathkid95/linux_samsung.git

Now, every time mathkid makes changes on github you can sync them with your local repo by cd-ing to your local repo and typing in terminal

git fetch upstream

.

3. Add pre-2.3.3 colors:

Now, we will apply the pre-2.3.3 voodoo color drivers to your local repo.

First, On your repo on github.com switch to the branch "nexus-s-voodoo-with-pre-2.3.3-colors" and download the branch as a zip.

Second, extract the zip and copy the following 4 files to the same directory in your local repo using file manager:

File 1: arch/arm/mach-s5pv210/herring-panel.c

File 2: drivers/video/samsung/Kconfig

File 3: drivers/video/samsung/s3cfb_tl2796.c

File 4: include/linux/tl2796.h

4. Push changes to your github (optional):

This is a good idea to do so you have your changes saved on github in the the event you mess up your local repo and to share your changes with others.

First, stage the files you changed by cd to your local repo and adding the files, in terminal:

cd ~/mydroid/linux_samsung

Then,

git add arch/arm/mach-s5pv210/herring-panel.c

Then,

git add drivers/video/samsung/Kconfig

Then,

git add drivers/video/samsung/s3cfb_tl2796.c

Then,

git add include/linux/tl2796.h

Next, you commit the changes, in terminal:

git commit -m "Voodoo color: revert to pre-2.3.3 voodoo color drivers"

Finally, you push the changes to github in terminal:

git push origin nexus-s-voodoo

5. Compile kernel:

Now, compile the kernel, in terminal:

cd ~/mydroid/linux_samsung

export PATH=$PATH:/home/<your-username>/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/
make ARCH=arm clean
make ARCH=arm herring_defconfig

Replace <your-username> with you ubuntu username.

make -j4 ARCH=arm CROSS_COMPILE=arm-eabi-

6. Flash kernel:

After the kernel compiles, You'll find your kernel at: ~/mydroid/linux_samsung/arch/arm/boot/zImage The wlan module is at: ~/mydroid/linux_samsung/drivers/net/wireless/bcm4329/bcm4329.ko

Copy those 2 file into the cm7/any zip in the OP replacing my zImage and bcm4329.ko.

Flash the zip in CWR

YOUR DONE YOU COMPILED YOUR OWN CUSTOM KERNEL AND FLASHED IT.

Let me know if you need anything.
[Nexus S Android Development] snandlal:
Cool thanks! Gettin at it now. How will I know that this is for Nexus S 4g? Same procedures right? Or is there something that is different i need to do?
[Nexus S Android Development] reddv1:
They both use the same zImage, the zip when you flash it will combine the ramdisk and zImage into a boot.img and flash it.

The difference between ns4g and ns is the ramdisk.
[Nexus S Android Development] snandlal:
This is what i am getting. It won't generate a zImage.

srn@srn-laptop:~/android/system/linux_samsung$ make ARCH=arm CROSS_COMPILE=arm-eabi-

make: arm-eabi-gcc: Command not found

CHK include/linux/version.h

CHK include/generated/utsrelease.h

HOSTCC scripts/basic/fixdep

HOSTCC scripts/basic/docproc

HOSTCC scripts/basic/hash

make[1]: `include/generated/mach-types.h' is up to date.

CC kernel/bounds.s

/bin/sh: arm-eabi-gcc: not found

make[1]: *** [kernel/bounds.s] Error 127

make: *** [prepare0] Error 2

any ideas?
[Nexus S Android Development] SA-07:
You need to make sure you have your toolchain for cross compilation set up in your android source code under the prebuilt folder..

What version are you using 4.4.3?
[Nexus S Android Development] SA-07:
Oh yeah make sure to have your path exported correctly ;D
[Nexus S Android Development] snandlal:
How can i find out what version?
[Nexus S Android Development] SA-07:
Ok, use the link provided by reddv1 and look under:

Now the building. Copy and paste these lines into your terminal. BE SURE TO EDIT YOUR EXPORT COMMAND WITH THE CORRECT PATH!

Code:

export PATH=$PATH:/home/<your username>/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/

make ARCH=arm clean

make ARCH=arm herring_defconfig

make -j4 ARCH=arm CROSS_COMPILE=arm-eabi-

Notice how he sets the path to his stock toolchain in his android source code. You will see that there might be more than one version (4.4.0, 4.4.3, etc)

export the path to whatever version you want and cross compile
[Nexus S Android Development] reddv1:
This is the path of the cross compiler: /prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/ , do you have it in your build environmet?
[Nexus S Android Development] snandlal:
I will put it in bashrc. I think its just my path is wrong......hang tight....thanks for the help fellas
[Nexus S Android Development] reddv1:
No, you don't have to put it in . Bashrc, I was thinking of something else.
[Nexus S Android Development] reddv1:
Make sure you put the correct path for the cross compiler, in your case its, code: export PATH=$PATH:/home/srn/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/

In terminal run:

cd ~/android/system/linux_samsung

export PATH=$PATH:/home/srn/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/
make ARCH=arm clean
make ARCH=arm herring_defconfig

Replace with you ubuntu username.

make -j4 ARCH=arm CROSS_COMPILE=arm-eabi-

-j4 is the number of cores your CPU has +1. So if you have 2 cores it would be -j3. But I don't think it really matters. Is that right mathkid95?
[Nexus S Android Development] snandlal:
Well after putting in make -j4 ARCH=arm CROSS_COMPILE=arm-eabi- it is finally compiling right. Thanks alot guys.
[Nexus S Android Development] reddv1:
Let me know what happens next. Waiting anxiously :)
[Nexus S Android Development] SA-07:
Yeah its the number of cores
[Nexus S Android Development] reddv1:
Hey snandlal, I was checking your github but you don't have any repos. Did you clone mathkid's repo directly from his github?
[Nexus S Android Development] Kraenesk:
From a drunken Guy. Its nice to see developers supporting a potential future Dev like this publicly. Kudos to mathkid and rev. I love to see people making knowledge public instead of hoarding it. Its open in its purest form. *claps*
[Nexus S Android Development] snandlal:
Well when you said do this: Next, clone your repo by typing the following in terminal

Code:

git clone git@github.com:snandlal/linux_samsung.git

I think i did this:

git clone git@github.com:mathkid95/linux_samsung.git instead. was that wrong cuz when i put mine in it wouldn't go.

Well here it is. How would one verify it has pre 2.3.3 colors. Looks like it right?

Should i try the git clone git@github.com:snandlal/linux_samsung.git command now?
[Nexus S Android Development] SA-07:
Its pretty much the same. But you definitely should clone it for your reference
[Nexus S Android Development] reddv1:
No, you don't have to.

It didn't work with your username because you didn't fork mathkids repo on github. You have to go to mathkid's github and click fork in the top right then you can clone your own repo.

If you decide to do that, delete the current Linux_samsung. So you don't have any problems. Also you would have to copy over the 4 files for voodoo color again obviously.

Using your own repo you can push your changes back to github and keep track of all your changes. I recommend you do that.

I'm going to try your kernel, I'll let you know how it goes.
[Nexus S Android Development] snandlal:
Ok. So where should the 4 files have actually gone? Cuz it kinda doesnt look like pre 2.3.3
[Nexus S Android Development] reddv1:
They should go in your Linux_Samsung directory in the same path as they are in the zip you downloaded, as I mentioned in step 3.

Make sure when you download the zip from github you select the branch nexus-s-voodoo-with-pre-2.3.3-colors.

I just installed your kernel, the colors are not pre-2.3.3. You have to try compiling again with the correct files.
[Nexus S Android Development] SA-07:
Yeah make sure you have that branch.

Grab those 4 files from that branch
[Nexus S Android Development] snandlal:
Ok trying again. Sorry guys.

I know what i did. I used mathkids normal drivers. Doin the right ones now. Gimme a few fellas. :-)
[Nexus S Android Development] reddv1:
Hurry man, these 2.3.3 colors I just flashed are hideous!
[Nexus S Android Development] snandlal:
Ok I know. Well try this, if you don't mind.
[Nexus S Android Development] reddv1:
Not yet man, still 2.3.3 voodoo colors.

I'm going to send you the 4 files in a minute because you must be getting the files from the wrong branch.
[Nexus S Android Development] SA-07:
Yeah, red ur right he's on the wrong branch.

Snandlal, go to the pre 2.3.3 colors branch
[Nexus S Android Development] snandlal:
Dangit! I knew it. Ya if you could send me those that would be great
[Nexus S Android Development] snandlal:
Git is really new to me. Obviously :-)
[Nexus S Android Development] reddv1:
Here is a zip of the files, extract it and read the Readme to know where to copy and past the files.
[Nexus S Android Development] SA-07:
Make sure you get the right branch ;D
[Nexus S Android Development] butterdori:
On my Voodoo control app, under color profiles, i have the option 'Voodoo profile v1 <2.3.3'

Is this kernel different to this option?

I'm on NScollab with matrix 5.5 btw
[Nexus S Android Development] reddv1:
Yeah its different, on matrix that option doesn't do anything but on this kernel it actually gives you pre2.3.3 voodoo colors.
[Nexus S Android Development] SA-07:
Yes, my branch did not have those drivers needed for em. ;D
[Nexus S Android Development] reddv1:
You'll learn it eventually, its not as hard as you think :)
[Nexus S Android Development] reddv1:
So, any luck snandlal?
[Nexus S Android Development] snandlal:
Try this bad boy
[Nexus S Android Development] snandlal:
Thanks reddv1 for your patience and knowledge.
[Nexus S Android Development] reddv1:
That's it, you did it! Don't you love those vibrant colors.
[Nexus S Android Development] snandlal:
Looks great. That was a great tutorial you made.
[Nexus S Android Development] snandlal:
New thread with matr1x pre 2.3.3 colors in 4g section
[Nexus S Android Development] morfic:
All speeds are menuconfig options. But let me push latest changes, due to (X)TEUV, source is in flux, after the push it'll be good to clone.

Akin to the Kconfig.morfic in there you could make the colors a Kconfig option, toggling it on and off.

I actually always liked the colder WB, not a fan of this failed warm WB.

If it's not too much work i could even just build a TUV11 version with the colder calibration.

Either way, wait until i push to git. (And you know my Nexus S kernel is not on github, right?)

About Ezekiel's dimmer: You should add the busybox version to your OP. 1.16.x in CM7 does not contain crond nor does 1.18.4 (which stericsson's busybox installer defaults to). But switch his installer to install 1.17.1 (The one Ezekiel says to use) and it's a go. figure adding the note cuts down on "Hey this dimmer doesn't work" posts down the road.

EDIT1:

Down to 3 files required:

morfic@othris ~/NSDEV/pre233voodoo $ diff -urp ../samsung/drivers/video/samsung/Kconfig Kconfig

--- ../samsung/drivers/video/samsung/Kconfig	2011-05-02 00:59:38.535175543 -0500

+++ Kconfig	2011-03-20 22:25:42.000000000 -0500

@@ -102,12 +102,11 @@ config FB_VOODOO

This enables support Voodoo color mods

config FB_VOODOO_DEBUG_LOG

- bool "Verbose Super AMOLED driver logs"

+ bool "Super AMOLED command logs & decoding"

depends on FB_VOODOO

default n

---help---

- Logging for developers

- Super AMOLED hardware command decoding and driver calculations

+ Logging for developer

config FB_S3C_NT35580

bool "NT35580"

morfic@othris ~/NSDEV/pre233voodoo $

nothing but comments/description changes.

EDIT2:

I admit the amount of "number" does make the encasing the current and the old into #ifdef #else #endif very tedius, I'll just make sure it's all easy for YOU :P

http://morfic.euroskank.com/git/?p=linux-samsung.git;a=shortlog;h=refs/heads/android-samsung-2.6.35 all good now.
[Nexus S Android Development] reddv1:
Added a new version of the kernel with post-2.3.3 voodoo colors, for people who like to use the sliders to set their own colors.

Add support for i9023 bln.

Updated cron.zip, that enables touchkey backlight dimmer option, to work on all roms regardless of busybox.(thanks morfic for pointing that out)

As ogdobber has sold his nexus s and moved to the sgs2, Lucid Nexus will replace Jame bond kernel.
[Nexus S Android Development] zadnica:
Nice! Thanks for kernel.
[Nexus S Android Development] krasnoff:
this kernel unstable on the cm7 nightly #159: less than one day I found two reboots, and one time remove the battery. i'm don't use CPU-management & other tweak tools.

my primary kernel jame bond 1.5.9.3 sabai is more stable now. I hope temporarily more stable. thank you for your work!
[Nexus S Android Development] ale.landra91:
I'm the 100th "thanks" :) I've a question...is normal that the white color is greenish on the lucid Blue? Because i buy a nexus with 2.3.4 and i don'know if it is normal (in particular the white screen where i insert PIN code)

thank you
[Nexus S Android Development] snandlal:
Runnin this and lovin it. Great job reddv1! Up and coming super-dev!
[Nexus S Android Development] RGX521:
Well, since Jame Bond isn't going to be developed anymore, I've switched to Lucix Nexus, now. Since I'm on the 9023, I haven't seen any difference so far. Which is a good thing, as Jame Bond was awesome - and it means I haven't seen any problems, either.
[Nexus S Android Development] reddv1:
Your welcome :)

I don't have a greenish tint on whites on my phone, I also tested the PIN code screen too. I know AMOLED screens have a lot of variations, so yours might just have a greenish tint.
[Nexus S Android Development] ale.landra91:
Thank u very much...it is the best and simpliest kernel i tried. Keep it simple with only bln and voodoo :) another question: what is the undervolt of the battery? Is it activated automatically?
[Nexus S Android Development] dario3040:
Well, it cannot be disabled, so I guess it is enabled automatically.

And I think it's a processor undervolt, as I haven't heard of any battery undervolts yet.
[Nexus S Android Development] ale.landra91:
Why undervolting a processor? (The common answer is: better battery life, something else? Is not clear for me...is the first time i use custom kernels...thank u and sorry for all the questions :) )
[Nexus S Android Development] reddv1:
The undervolting is for better battery life; however, it's not undervolted too low so you won't get any random rebooted.

Also, I'm keeping this kernel very simple, just UV, voodoo enhancements and bln. If I decide to add other stuff it will be a separate version.
[Nexus S Android Development] ale.landra91:
Thank you for your work and for your explanations!
[Nexus S Android Development] fv1ede:
i have put this kernel in a miui rom and it works like a charme

now i will try how the battery life is
[Nexus S Android Development] niscrome:
Freakin' brilliant! Thank you for this sweet kernel?
[Nexus S Android Development] caleb1783:
hi... i noticed something after changed to this kernel...

with wifi on, gmail syncs without problem...

but when on edge, gmail fails to sync... it keep trying to sync causing more battery drain...

btw... i am using NSCollab 1.0.39...

Could this be kernal related?
[Nexus S Android Development] window7:
Is it possible to use the Cron.zip with Trinity kernel?
[Nexus S Android Development] fordmanck:
So far the best kernel I've tried. Battery life is much better, I haven't had one random reboot which is huge. I was getting randoms on the stock kernel and/or any other kernel I tried out. I'm not even missing not being OC'd. Thanks!
[Nexus S Android Development] ale.landra91:
it works very well on MIUI 1.8.12 :)
[Nexus S Android Development] reddv1:
Yes, trinity supports it.
[Nexus S Android Development] dena994:
Also for me ....optimus!!

Inviato dal mio Transformer TF101G usando Tapatalk
[Nexus S Android Development] coloxim:
It is a nscollab' s problem ..is not the kernel!

Inviato dal mio Nexus S usando Tapatalk
[Nexus S Android Development] Bandis710:
I am right if think that Lucid Blue: (pre-2.3.3 voodoo color drivers) is not useful for me because I have the 9023 slcd ? So i should go for the post 2.3.3 color kernel ?
[Nexus S Android Development] ale.landra91:
I think that for i9023 you can use the 2 kernels (blue and yellow) with the same results because the voodoo color management is only for super amoled i9020...than there is no difference...you can use these two kernel only for bln and UV
[Nexus S Android Development] Jibreil:
Keep up the great work! Absolutely agree with what fordmanck said.
[Nexus S Android Development] reddv1:
Ale.landra is right, for the i9023 both versions are exactly the same
[Nexus S Android Development] coloxim:
but in blue version a can't cahnge the color manually?

it will be possible in the future?

And why my softkey don't turn off?

I've flash corn too..
[Nexus S Android Development] reddv1:
No only lucid yellow will have the color sliders to change the colors. Lucid blue will only have the original set colors with voodoo profile 1.

About the softkeys turning off, what rom are you on? Some roms don't have support for unit.d scripts or if you don't have root.
[Nexus S Android Development] mikemike23:
Hi, I am a new baby in Flashing rom, I want a bright and colorful feeling for my Nexus S, thus i want to download the "Lucid Blue", and I am now using MIUI 1.8.12 Rom, Please tell me which version of " Lucid Blue" should I download. And how to install it in my phone after that? Thanks
[Nexus S Android Development] reddv1:
You need to download the cm7/any tom zip and flash it in clockwork recovery. Then download https://market.android.com/details?id=org.projectvoodoo.controlappvoodoo control app and select color profile 1 in the app. That's it.
[Nexus S Android Development] mikemike23:
Thx for yr reply. And how to know I already install your file or not? how to check?
[Nexus S Android Development] reddv1:
Settings >about phone it should say lucid-nexus-1.4b under kernel
[Nexus S Android Development] mikemike23:
Thx, I already make it. And the most important things is.........I am success
[Nexus S Android Development] coloxim:
oh...ok...thanks...

I'm using superosr...

what i've to do?or there is no possibility?
[Nexus S Android Development] reapsor:
Best kernel that's for sure, I use it with the cyanogenmod nightlies and everything works like it should.

also combined with great battery life.

Thank you for this awesome work! :)
[Nexus S Android Development] reddv1:
Yes it's possible, Ezekeel posted an update. I'm going to update the kernel soon which does not require a cron.zip to enable the dimmer.
[Nexus S Android Development] ale.landra91:
got only satisfactions with lucid blue
[Nexus S Android Development] coloxim:
in the future it will possible see more kernel with old drivers?

maybe netarchy...
[Nexus S Android Development] leechy:
Of the few kernels I've tried, this has been the best balance of speed/responsiveness, stability (no reboots/freezes on Oxygen or CM7) and battery life for my NS4G. Thank you for continuing the work of James Bond! Please keep the philosophy of keeping it simple! :)
[Nexus S Android Development] reddv1:
I made one for myself I'll post it up soon, but I only compile stable versions of netarchy-nexus.
[Nexus S Android Development] reddv1:
Version 1.5

Updated kernel to version 1.5.

Updated Touchkey Backlight Dimmer, so you can set a custom interval before the touchkey lights go off, and does not require a separate flash-able cron.zip.
[Nexus S Android Development] coloxim:
but..can you make a tutorial for install the old driver in another kernel?

or i ask much?

:D
[Nexus S Android Development] ale.landra91:
Has it the same function of bln control pro? Do i have to uninstall bln control and use this backlight dimmer? Does it requires an app? Thank u
[Nexus S Android Development] Maximilian Mary:
These are two different things.

Backlight dimmer turns the button backlight off. The newer version requires the line of code mentioned above.

Bln turns the backlight on (or blinks it) when you receive a notification, even if the screen is off. This requires the bln app.

Both require a compatible kernel. You can use both at the same time if you like.
[Nexus S Android Development] ale.landra91:
I don't understand the utility of switching off backlight with backlight dimmer...
[Nexus S Android Development] Peter_Peterson:
It's a seperate "display" which consumes power.

Actually meanwhile I know where the buttons are placed so i don't need them to glow.
[Nexus S Android Development] reddv1:
A gave a tutorial to snandlal of how to do that earlier in the thread, just go back a few pages and all the information you need is in this thread.
[Nexus S Android Development] reddv1:
The touchkey backlight dimmer mod turns off the touchkey lights while the display is ON after a certain period of time. For example, I'm watching Netflix on my phone after 30 seconds the touchley lights go off and I can enjoy the rest of the video without the touchkeys on.

BLN works when the phone screen OFF to notify you of new message.
[Nexus S Android Development] coloxim:
I've read....too much complicated for me...

:D

ihihih,....
[Nexus S Android Development] reapsor:
Works well, got the timer set to 5 sec.
[Nexus S Android Development] Petarsson:
first of all, thanks for your kernel! i will give it a try immediately!

regarding the touchkey backlight dimmer, is that really a big deal? i mean, if i have my display on, i do not really care of that bit of power the touchkeys consume?! the display will need a multiple of battery, so why should i care about these leds? :confused: how much power can i save by disabling them?

please don't get me wrong, i do not want to talk bad of this development and i am really happy, that people take care of many, many things on our phone, especially regarding battery endurance!

but i want to know, if it makes sense for me to use this mod, or not...;)

again, many thanks for you work!

greez

p.
[Nexus S Android Development] reddv1:
The dimmer is an option I add to the kernel for people that want it. The dimmer doesn't affect battery life. It's disable by default so if you don't want you don't have to do anything.
[Nexus S Android Development] Peter_Peterson:
i know set up the they softkey dim and i love it. set it to 1ms, you it just flashed for a short moment when i power on the screen. then it goes into stealth mode.

just looks like a ninja nexus s

and if i im in my bed watching a movie the softkeys aren't the brightest thing in the room anymore.

got a random bootloop yesterday. phone was idle, had to pull the battery to fix it. first issue in a week of use

love this kernel!