yashsingh1/xdaforums huggingface dataset:
[Nexus S General] AdamG:
Just thought I would add my input here, I have just had somebody test the kernel with stock toolchain and they was convinced they had yellow tint even after the new kernel, they sent me a picture of 2 devices next to each other and it definitely WAS NOT yellow tinted, people are confusing this issue with the cool blue colours that some devs are adding into kernels.

If your device looks like the following after the new test kernel then its a problem!
[Nexus S General] apatal:
Nah I beg to differ. I think my SLCD screen makes life a whole lot easier than for you AMOLED folks. ;)

Sent from my Nexus S
[Nexus S General] sginkr:
i've got yellowish screen in some previously kernels. i don't like that color, so i've waited your patch. and today i've tried test1, it's not working. and then test2, it's working!!!

thank you thalamus!

fyi i'm using stock jb rom.
[Nexus S General] noobiekins:
I have never seen a dev be this active with his users. This makes me think that thalamus is a great dev.

Is there a way to tell which amoled panel you have without disassembling it?
[Nexus S General] jit_devil2:
ummmm this may be a noobish observation but the yellow tint might have something to do with the auto-brightness.

the yellow tint is definitely there but disappears if you turn off auto brightness and crank up the brightness slider to around 50% or higher (poor battery :crying: )

am talking about most kernels including jellybelly stock ones. the test 1 and 2 definitely is an improvement. not perfect but far better

just my 2 cents maybe it will help in someway
[Nexus S General] chronophase1:
Yeah. Whites don't like our battery too much. Lol.
[Nexus S General] madd0g:
Got a question regarding using your kernel on the stock ROM, but the JellyBelly BLN edition. Do I need the modified liblights/anything else ? I'll test the Phone app drain if it's the same on the stock ROM, but would like to keep the goodies from your kernel.:]
[Nexus S General] benoit2600:
I have the yellow tint on the google logo with both the kernel you mad me yesterday, and the one with the default toolchain. Moreover, the one with the default toolchain have green screen.

The only kernel who doesn't have the yellow google tint is trinity kernel, the google logo have blue tint instead.

Even the stock kernel have a small yellow tint , so I don't think it's an issue.
[Nexus S General] :
Lol, thanks. I hate bugs. I like happy users. I could add a printk to the init code, at least then I might be able to narrow down which panel is causing the issue.

I still think there is an issue with the panel init code which needs fixing.

I'm also unsure how reliable many of the reports of 'yellow tint' are. Maybe you are too used to the blue colours that are in some other kernels.

I only want to know if it is a different colour from *stock* (flash stock if you are unsure, you only need to backup and flash the boot.img from the factory images to test, then you can restore your old boot.img).

Anything which does exist in stock I'm not concerned about at this point because it's confusing the issue. My only concern at this point is regressions which *I* have introduced.

Anyway, here is a further test kernel.

This is 'test 2' built with the stock google toolchain.
[Nexus S General] :
And here is a further test kernel, compiled with the stock toolchain and with a couple of subtle modifications to the panel init code.

I am wondering if this will fix the issue that benoit2600 is having, and also I think it may fix the issue on i9023 where the CRT animation is not displayed, although I don't have a i9023, so YMMV.

Edit: No, it doesn't fix the i9023 issue.
[Nexus S General] safendi:
Which kernel is better for i9023? Test 1, 2 or 3?

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S General] :
None of them. i9023 is not affected by this issue.
[Nexus S General] sginkr:
gps came off when playing music.

i'm running your 25-test2 kernel on stock JB rom.

and i used sports-tracker app to track my exercise.

so gps started working on the begining moment of the exercise.

however, after one hour, when i checked my sports-tracker app screen, realized gps got off.

according my record on sports-tracker app, gps got off when i started playing music.

fyi, i use google's 'play music' app.
[Nexus S General] :
Yeah. I'm aware of that issue. I disabled the GPS detection code intentionally in test2. That was what worked around the issue benoit2600 was having, although I don't think it is actually the reason for it, but it is triggering a pre-existing bug.
[Nexus S General] leerapalot:
The above test kernel brings back the yellow tint for me.

Both versions of test 2 make it white again.
[Nexus S General] fear_factory84:
crt animation is working fine on my i9023 with your kernel shipped with jelly belly 0.1.5.0.1..
[Nexus S General] :
I know. It contains an ugly hack to 'fix' it. I was trying a nicer fix, which doesn't work.

---------- Post added at 02:24 PM ---------- Previous post was at 02:23 PM ----------

Try this please.
[Nexus S General] leerapalot:
Yellow tint is back.
[Nexus S General] :
Ok, narrowing this down.

Try this.
[Nexus S General] leerapalot:
Just flashed. White again.
[Nexus S General] :
Ah ha.

Ok, 1 more then, let me build it...
[Nexus S General] mixtapes08:
I love your dedication and attention to details. For that I admire you and apologize on what I've said in the other thread. Peace out :p

Sent from my Nexus S™
[Nexus S General] :
Ok, this kernel should be white too. After that I have one more and then I'll know exactly which the offending commit is.
[Nexus S General] mixtapes08:
Oh thanks but I think this is for I9020 users right?

Sent from my Nexus S™
[Nexus S General] :
It's for leerapalot
[Nexus S General] leerapalot:
Yes its still white.
[Nexus S General] :
Ok, just to confirm then, this will turn it yellow.

You can go back to the previous one after you have tried that. :)
[Nexus S General] leerapalot:
Yes I can confirm it is yellow again. Flashing back to test 6 now.

Thanks for your efforts to solve this.

I was starting to think I was imagining the yellow tint.
[Nexus S General] jit_devil2:
ok i was a bit disappointed when thalamus said he wont be including voodoo color but support like this................ hats off, respect and thank you
[Nexus S General] sidnoit22:
Thats the latest build right? kernel-i9023-S5PC110-3.0.38-25JB_test-1-g7b8bb8d-JB-20120729-002929.zip
[Nexus S General] :
Yeah, I figured. It's the same issue as benoit2600 was having also.

Weird thing is, the code in question doesn't touch anything anywhere near the display. It's code to tell IDLE2 that GPS has been activated. I do have a theory what the issue could be though, it's calling into cpuidle before it has initialised because the GPS serial port is being initialised first. But even that shouldn't cause this issue, because there is code there which stops the call from going any further if the workqueue isn't initalised. Perhaps a small delay might fix it.
[Nexus S General] apatal:
The latest test version that's been released, yes. However, _thalamus has been busy chasing a weird screen coloring bug and has released a number of debugging versions. I suggest you wait a couple more minutes/hours and a new version will probably be released with the fix for the said bug.
[Nexus S General] :
Any chance either you or benoit2600 can try this one.

I refactored the code slightly and added a 100ms delay into the GPS check, and it is now calling into cpuidle *after* initialisation has completed, rather than before as it was previously.

I'm hoping it will resolve it.
[Nexus S General] leerapalot:
Just tried this one. Yellow again.
[Nexus S General] :
Damn. I'll look a bit deeper at it and see if there is another way I can do it.

Thanks for your help so far. :)
[Nexus S General] screeny2:
Is this kernel supposed to work with stock JB? If so, I'm gonna try it :)
[Nexus S General] :
Ok. I've changed the code completely, it doesn't get called at all in early init now, so this kernel will not have the issue.

If it does, I actually might cry. Lol.
[Nexus S General] apatal:
It's supposed to work with any ROM. Try it, and feel the difference. ;)
[Nexus S General] apatal:
Your Thanks meter is at 1111 FYI. Nice. ;)
[Nexus S General] :
Heh. :)

So...AMOLED users, I'm going to do something here which I don't normally do, I'm going to have a vote to see which display colours people prefer.

So, reply stating you prefer either 1 or 2.

I'll explain the difference *after* the vote has been decided.

Kernel 1 here.

Kernel 2 here.
[Nexus S General] leerapalot:
Your right. White again.
[Nexus S General] :
Good. Thats that fixed then. :D
[Nexus S General] Imppy:
I'm on amoled screen and I think I like the first one better
[Nexus S General] leerapalot:
Kernel 1 looks best to me
[Nexus S General] daniel3ric:
Kernel 2 seems more neutral to me, I prefer. But honestly, I don't see a big difference :).
[Nexus S General] 420p:
Version 1, Version 2 has yellow tint on mine.
[Nexus S General] Supersaiyan.IV:
Music sounds even better when the CPU is undervolted - less hardware noise. This could also be the case with the IDLE2 implementation, this time however due to the CPU sleep implementation.
[Nexus S General] lurtis:
Quick question... do these kernels work on the D720 (sprints CDMA 4g version nxs)? I only have one phone and don't feel like borking it. Running burnsra's experimental cm10 release. Using trinity now Cruz of the nice color but would like better battery while playing music.

Thanks in advance.
[Nexus S General] neilmb:
The first one, test3, has much better white balance on my phone.
[Nexus S General] noobiekins:
The first test is more blueish, the second test is more yellowish. I prefer the blueish one since the colors seem to pop out more, but the yellowish one looks more natural, colors more similar to my monitor
[Nexus S General] :
It's looking like a 1 so far...only 1 vote for 2. I'll wait for some more votes though. :)
[Nexus S General] alexdemonumber3:
1, all the way
[Nexus S General] Maximilian Mary:
I prefer 1 (test 3).

I tested at auto & max brightness outside, with the sky bright, but overcast. I also tested at min brightness in a dark basement, with a small amount of natural light coming in. This should remove any skewed temperature perception coming from overly blue or yellow artificial light. I looked only at white, on a blank page in chrome.

2 seemed alright, but somewhat gray, and a little dingy. It looked like it could be a little cleaner.

1, however, just seemed a little gray. It did not look dingy at all, nor did I have the feeling that it should have been cleaner. (When I back came inside under fluorescent light with it still at max brightness, it looked fantastic - very clean, and very white.)
[Nexus S General] jorim.tielemans:
S-LCD users don't have to vote?
[Nexus S General] colonia27:
Nope. Problem exists only on Amoled

Gesendet von meinem Nexus S
[Nexus S General] srthimsen:
Running the same on my ns4g, works beautifully. I don't have 4g, so I can't report on that. But battery life and smoothness is quite good, especially considering the state of our ROM.
[Nexus S General] Imppy:
I'm getting random reboots when some app freezes...cap buttons light up but the whole screen is black before reboot...back to kill does not work
[Nexus S General] benoit2600:
1 is better
[Nexus S General] colonia27:
What version are you running atm? There was a problem with black screens a few versions ago which is solved now

Gesendet von meinem Nexus S
[Nexus S General] Imppy:
I'm on the latest one amoled version one
[Nexus S General] :
I've no idea which version that is. You have seen how many kernels I got people to test today, right?

What is its filename?
[Nexus S General] Imppy:
kernel-S5PC110-3.0.38-25JB_test-3-g81c04bd-JB-20120729-170854.zip
[Nexus S General] :
I is it a soft reboot or is it a hard reboot back to the bootloader splash?

Either way, I'll need some logs. Nobody else has reported such an issue since I fixed the previous bug, and I haven't introduced anything recently which would cause any new bugs, so I'm at a loss as to what might be causing it without a last_kmsg if it's a hard reboot or a logcat if it's a soft reboot, plus steps to reproduce it.
[Nexus S General] Imppy:
It reboots to the nexus boot animation screen..could you tell me how I get those info? Last-kmsg and logicat
[Nexus S General] :
Right, no last kmsg needed, just a logcat then. Install alogcat or something and collect it immediately after it has soft rebooted.
[Nexus S General] Imppy:
Thanks do I need to open the app always? Or it would automatically start after reboot?
[Nexus S General] superhil:
Hi _thalamus,

Is there any workaround to fix slow usb transfer rate when in OS mode?

(http://xdaforums.com/showthread.php?t=1751028)

Thank you very much
[Nexus S General] :
Dunno, there was a patch Samsung implemented, I remember 'borrowing' it for the desire and it improved the speeds there. I think the difference is recovery allows caching, whilst when android is booted, it doesn't, and tbh, we haven't really got the free RAM on the Nexus S to enable caching. Non-cached transfers are slower.
[Nexus S General] zyrill:
Hi there,

sorry for asking a seemingly obvious question, but which file is the correct one to flash for a given phone? That is to say, what is the difference between "kernel-i9023-S5PC110-3.0.38-25JB_test-1-g7b8bb8d-JB-20120729-002929.zip", "kernel--JB-20120729-144557.zip" and "kernel-S5PC110-3.0.38-25JB_test-7-g3748d15-JB-20120729-164802.zip" for example. Except for the difference in build/test number/time, that is? Are all of those kernels for the i9023?
[Nexus S General] stojshic:
_thalamus, as you said on JellyBelly that you won't read that topic anymore, I hope you don't mind reporting stock JellyBelly 0.1.5 problem here. I already reported one reboot today there, you've read it, but I had another reboot this evening. I was reading xda, locked phone, and after a minute I saw it rebooted. Hard-reboot... Here's last-kmsg again, I guess it will be the same as last time, but it might help you, either way, nothing to loose by uploading it again: http://db.tt/q6fEYdxH
[Nexus S General] Imppy:
Yes I get similar issues as above...sometimes lockup after using app
[Nexus S General] d_phekt:
Wow! Went out of town for the day and come back to see such awesome dev support. I flashed both 1 & 2 test kernels and #1 is definitely nice and white for me. I also noticed that the two Google boot screens are now both white instead of white, then yellowISH. Great work thalamus! Such support and awesome work is one of the reasons I have stuck with this phone.
[Nexus S General] deltatux:
While test3 has "true" whites, test4 seems softer due to the slight yellow hue. I like test4 a bit more because of that, test3 is a bit too strong for me in terms of how white it is. Looks a bit too unnatural.

EDIT: Plus, don't SuperAMOLED screens eat more battery on true whites compared to other colours even if they're still considered "white"? I remember something like it eats at least 2x the amount of battery.

EDIT2: Test 7 seems to be slightly yellower than test4 ... to be honest, the changes between these builds except test3 are so similar, I can't really tell if my brain is tricking me or not anymore lol.

deltatux

---------- Post added at 10:00 PM ---------- Previous post was at 09:24 PM ----------

The test kernels are mainly meant for I9020 phones as they have the SuperAMOLED screens. It seems like the colour calibration may not affect the SuperLCD screens in the I9023.

deltatux
[Nexus S General] :
No problem. I think I've fixed that now by adding a null pointer check. Not sure why there wasn't one there, but I guess the pointer should never be null.

I'll do a release later with the likely fix although I'm not promising anything. :)

---------- Post added at 06:35 AM ---------- Previous post was at 06:25 AM ----------

As for colours...

I'll let you into the secret now...

Kernel 1 had the pre 2.3.3 colours, kernel 2 has the post 2.3.3 colours after Google adjusted them and caused a fuss.

I'm not bothered which one I go for, I perfer 1 personally, but I'm honestly not bothered.

It seems more people like 1, so I will probably go with that unless there are any major objections.
[Nexus S General] lurtis:
Not bad...this is my first cycle with this kernel. On 3g the entire time inside my apartment where my signal is very spotty. playing hard with phone.
[Nexus S General] madd0g:
To answer my question: yes, one need to copy the liblight*.so from /system/lib/hw and replace the stock one, then BLN and this kernel works on stock :]
[Nexus S General] Imppy:
The null pointer fix? Does that fix the reboots with apps?
[Nexus S General] giannis_mathiou:
First time that I installed _thalamus kernel and as I can see I'm getting pretty good battery life.

Installed it (latest test version 3.0.38-25 ICS) on CyberGR v14 and its the first time that I can see my battery hoping down slow and at the same time having great performance, especially @1GHz...
[Nexus S General] :
No. It should fix the occasionally reported reboots which occur when the device is idle.

Your app issue isn't a reboot, it's a runtime crash. Wiping will probably fix it tbh.
[Nexus S General] kirpi:
I'm trying to install the latest test version for my i9020T (on stock rooted JB with 3.0.38.24JB_test)

I think "kernel-S5PC110-3.0.38-25JB_test-7-g3748d15-JB-20120729-164802.zip" is appropriate since it is the latest one however I read the thread going back to 3 days, and "kernel-S5PC110-3.0.38-25JB_test-3-g81c04bd-JB-20120729-170854.zip" may be the correct choice.

So, for a daily driver, which one should I install? (I just want the latest color scheme and no null pointer etc. reboots, although it didn't reboot even once with current 24)

Also, if it won't be too much work, I think writing the latest daily use filename on the blog post, or the info file could eliminate a lot of the confusion and question answering :)

Edit: I tried kernel-S5PC110-3.0.38-25JB_test-3-g81c04bd-JB-20120729-170854.zip and the screen is really more blue than white in my opinion. I think this blue problem has to be handled with caution. I remember a Samsung interview that blue LEDs lifespan is lower. That was why Samsung keeps on using a pentile matrix with a shared blue. (Though I don't really get the reasoning. If you use a shared blue subpixel, won't it burn it faster than two blue subpixels?) I am going to try "kernel-S5PC110-3.0.38-25JB_test-4-gc8a8951-JB-20120729-171112.zip" now.

Well, I tried the test_4 now and it has much cleaner whites (not gray one). I suppose I get used to the JB (& ICS) colors. I'd love if this scheme is continued.

Thanks for the great job. (My idle battery consumption is finally stable and low)
[Nexus S General] JFOC:
My phone i9023 using JellyBelly ROM with thalamus kernel, for sometimes when receiving or calling phone make my phone reboot itself.

Is this cause by null pointer issues ?
[Nexus S General] :
Let me just guess the answer to that because you didn't provide a log.
[Nexus S General] JFOC:
Here is the log
[Nexus S General] :
Thats a kmsg and not a last_kmsg.
[Nexus S General] JFOC:
That is file from last_kmsg but i named as kmsg.txt

Sent from my Nexus S
[Nexus S General] :
Well, it doesn't show any crash unfortunately, hence why I assumed it was a kmsg.
[Nexus S General] metalgear873:
What app do you use for these logs. Or are they stored somewhere by the system, thanks!
[Nexus S General] Supersaiyan.IV:
"cat /proc/last_kmsg" in Terminal Emulator and pastebin it.
[Nexus S General] :
Experimental kernel for anyone who is interested, but please read the below first.

I'm going to ask that you refrain from flashing this this if you are a n00b or you don't know what you are doing, or if you feel the need to ask a question about it before doing so.

Some of it is code which I only wrote today and whilst it appears to be fine, I haven't tested it for long. I thought I would chuck it up here for experienced testers to have a play with.

It has IDLE2 v0.213 (experimental) as well as a possible fix for the NULL pointer issue and it's built from my IDLE2-Experimental branch.

IDLE2 is enabled at all times whilst the screen is off. This is working towards milestone 3, which I posted about the other day. I'm not planning on implementing this functionality in the next general release, ie -26, it's purely for testing at the moment.

If you get any crashes, It is critical that I get the last_kmsg, so if you can't do that, please don't flash it.

The changelog here, it's the 3 commits since 3.0.38-25_test.

I'm interested in any crashes and battery drain when idle compared with my previous kernels.

There is absolutely no need to post that it boots or you are flashing it or whatever, I know it boots and I don't care that you are flashing it or not flashing it as the case may be.

What I would like to be posted is reliable bug reports (if any), and reliable statistics for battery drain after a reasonable amount of time sat idle. Also, battery drain whilst playing music would be nice too, if there is something reliable to compare it to but not a necessity, I'm more interested in idle drain.

And yes, I am trying to scare the n00bs off. I need reliable, experienced testers to find me any bugs, not daft questions and crap bug reports!

By clicking this link, and installing this kernel you agree that you have read the above, you are not a n00b, you know your way around a command line and you are going to provide the last_kmsg if you get any hard reboots. ;)
[Nexus S General] deltatux:
I've noticed that the test7 kernel seems to be eating more battery than the previous kernels in -25. Can someone please verify this?

deltatux
[Nexus S General] srthimsen:
Running:

3.0.38-25JB_Test on NS4G on CM10 for past few days. It has worked flawlessly so far.

Just had my first (that I know of) hard reboot today, while streaming Pandora. Last_kmsg attached.
[Nexus S General] apatal:
I'm on it! ;)

EDIT: no reboots yet. I'll report back as soon as I hit one. Cheers!

Sent from my Nexus S
[Nexus S General] cadarn07:
I also have a Sprint NS4G running burnsra CM10 JB ROM and am looking at flashing this kernel to slim down some of the unnecessary features and improve battery life. As of right now, there are 3 JB builds to choose from on his blog. Which are you using?

** kernel-S5PC110-3.0.38-25JB_test-4-g6df7029-JB-20120730-232256.zip	31-Jul-2012 00:23	2.8M

** kernel-S5PC110-3.0.38-25JB_test-JB-20120728-201105.zip	28-Jul-2012 21:12	2.8M

** kernel-S5PC110-3.0.38-25_JellyBelly-JB-20120728-201319.zip	28-Jul-2012 21:14	2.8M

Thanks in advance.

Edit - the first one just came out today so I know you weren't using it as of your above post. I've read through this entire thread today and with all of the builds and test builds involved in this kernel, I lost track of which one is the most stable and works with the CM10 JB ROM. I will say though, the support of this dev is simply outstanding. And I love the philosophy he has with this kernel which is exactly why I want to try it.
[Nexus S General] qu3becker:
Hey,

I got a hard reboot when I was browsing with Opera Mobile so it could be an issue with this program... The screen closed from inactivity, I pressed on the power button to get back to it, Opera froze. I pressed on the home button to get back to the launcher. I opened Opera from the shortcut but it opened a black screen. Got back to the launcher, and force closed Opera by going in the App info. The phone froze, pressed on the power button. The screen went off, tried to press on the power button again but nothing. I pressed the power button several time but to no avail. I held the power button, it got back to the froze app info and suddenly, the phone rebooted.

Please refer to the attachment for further information.

Using i9020a with Jelly Belly 0.1.4 which I had no stability issue since it has been released, I may try version 1 if you want me to.

Sorry if there's too many details.

By the way, I have 4 years experiences in software QA testing but I wrote this report the most casually possible. I could use the template that I used to work with next time. I'll check the idle battery consuming tonight.