yashsingh1/xdaforums huggingface dataset:
[Nexus S General] :
With all due respect, this is a developers forum and a development thread. Dumping logs is basic troubleshooting and is one of the first things a developer will ask for, and some, me included, expect the log to be provided with the issue report, otherwise the report is pointless and just irritates me.

If you search this thread for last_kmsg you will find what you need to know...
[Nexus S General] migz012788:
I am also on the latest kernel but not experiencing a single reboot. And this kernel runs fine with me
[Nexus S General] coluichepensa:
No problems for me too. I installed the latest kernel and works very well.

thanks again for your great work
[Nexus S General] moon-unit:
I've tried all the JB Kernels available and this is hands down the best of the lot. No problems to report from me, just a smooth, fast experience. Well done and many thanks for your hard work.
[Nexus S General] degiovab:
This thread could maybe help Gitah:

http://xdaforums.com/showthread.php?t=1520508
[Nexus S General] jimdem:
Hello guys. Yesterday i had a reboot while i was messing with some dolphin browser's settings. As the browser was in beta stage, i assumed that the reboot was related to the app so i uninstalled it. A couple of minutes ago, i had a restart again, this time, while downloading updates from the play store. Here is the last_kmsg ;)
[Nexus S General] cadarn07:
Been using this kernel on my NS4G for a couple weeks and love it. I have noticed that as I move through updates for this kernel and for the CM10 JB ROM, that my max battery percentage has fluctuated. Back when I was stock, battery maxed at 94%. Switching to CM10 and this kernel, max battery was between 95% and 98%. Then right around the time I updated to the 7-31 kernel (I don't remember actual version numbers, just giving general time frame for my updates) and the 8-02 version of CM10 my max battery was only 91%. Then I updated to the current kernel build and the 8-06 CM10 build and my phone charges pretty quickly to 91% and then very slowly moves up to 95% and stops there (which is higher than what I got on stock so I'm fine with it).

It's my understanding that battery life is determined by the ROM and apps but what about the max battery charge? I assumed the ROM but someone at the CM10 thread said he thought the kernel dictated that. Is that true? And is there any way to get a better charge? That particular commenter said his kernel (matr1x) allows him to get to 100% charge which I've never seen on any kernel/ROM combo on my phone. I like this kernel too much to switch as long as I'm getting in the mid-90s but was curious why the max charge seems to fluctuate a lot for me.

Edit: I did just read an article explaining how unreliable the battery indicator is - but still thought it was strange that I had max battery percentage fluctuations and that I've never gotten anywhere close to 100% except for a couple times that I hit 98% a few ROM/kernel versions ago.
[Nexus S General] :
Looks like a filesystem issue on the /data partition.

[ 1261.186546] Aborting journal on device mmcblk0p2-8.
[ 1261.192320] journal commit I/O error
[ 1261.205056] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:296: Detected aborted journal
[ 1261.205308] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
[ 1261.211810] Kernel panic - not syncing: EXT4-fs panic from previous error

The filesystem is mounted with the errors=panic option, so the kernel has done the correct thing by panicking to forcibly reboot the device.

Doing a backup, a full wipe and format of /data and then restoring the backup in recovery should fix it without any data loss.

Don't ask what caused it, because I have no idea. Nothing or something. Filesystem corruption happens sometimes.
[Nexus S General] jimdem:
Thanks for your quick anwser. Recently, i made a full backup because i wanted to test another rom+kernel combo. But i wasn't satisfied at all so i decided to restore the backup and use again my favourite combo. So you have a point here. I'll try what you've said to prevent any reboots related to this issue from happening in the future ;)
[Nexus S General] rasengan82:
100 hours uptime on latest release kernel on ICS. Very stable man! Thanks for the hard work!
[Nexus S General] KTamas:
Does this / will this kernel have the 50 MB big highmem patch?
[Nexus S General] tommy0823:
Edited to avoid confusion. I forgot to quote the post I was answering.
[Nexus S General] noobiekins:
Yes
[Nexus S General] KTamas:
Thanks. Just flashed it, works great so far, the system is noticably faster.
[Nexus S General] :
Coincidence, that is all, nothing to do with the battery has been touched. The battery percentage is unreliable anyway so I wouldn't worry about it.
[Nexus S General] Gitah.:
Thanks, next time it reboots I'll post the log.
[Nexus S General] ShensMobile:
Sorry if this has been asked before, but nothing came up on a thread search...

But I keep getting "Status 7" errors in CWM when I flash this kernel on my i9020a. I've just recently fastboot flashed the latest 4.1.1 image from Google onto my phone and flashed CWM. Running the stock rom still. Could that be it?
[Nexus S General] :
Dunno.

What is the full error? Status 7 means nothing really, I'm guessing it's a failed assert, but I dunno which one.

It would probably be easier just to open up the kernel zip and flash the zImage in the kernel directory via fastboot, that is more reliable than the recovery method.

fastboot flash zimage zImage
[Nexus S General] albundy2010:
What version of cwm? If it is a older version update to a newer version like 5.8 or the 6. Whatever.

Better yet ditch it all together and use twrp.
[Nexus S General] inFECT:
Nexus S: Unresponsive screen during a ringing incoming call!!

First of all, kudos for this awesome kernel.

Running the 3.0.39-27 on a 9023 with jellybelly 1.0 and everything works fine.

Just a quick question. Is it possible to look into this bug? On cyanogen gerrit is a fix for it, which i allready tried before i switched to JB. Unfortunatly it didnt work.

Since it seems to be kernel related (according to the fix) i thought it might be a good idea to bring it up on this thread because yesterday the unresponsive bug striked again on me. I gonna reproduce the bug tonight and will provide logs asap.
[Nexus S General] :
I've seen this bug and tested a similar recalibration fix for it which didn't work. In fact, the fix was pretty much exactly the same but was written about 18 months before the version that is currently in CM gerrit. I can't say I've ever experienced it myself during normal usage though, only when purposefully attempting to trigger it. The workaround is simply do not touch the screen when it is turned on lol. I did some tests and 1 and 2 fingers don't trigger the bug, however 3 and above do.

There is no need to provide logs, I already know how to reproduce it on demand and the logs show precisely nothing anyway. :)
[Nexus S General] jimdem:
I haven't seen the "unresponsive screen bug" (yet :P) while using jellybelly+thalamus but it happened to me many times when using ics (both stock+custom roms/kernels). Also, apart from the screen being unresponsive when someone called you, many times, when i tried to unlock my phone, i just couldn't slide the ring to the unlock icon. It wouldn't let me do that. I was able to move the ring but it wouldn't reach the unlock icon. Like the phone was struggling not to unlock, and it was pushing the ring to the opposite side :D
[Nexus S General] inFECT:
Good to know that you allready aware of this really annoying bug. It's kinda rare that it happens, but for murphy's law sake, always on important incoming calls ;)

Well, i noticed myself that there is not really that much happening on standard logcat. On ICS i collected one, but that was before i know it is kernel related. If you say that you didnt see anything suspicious also, than i guess we covered now all logs (including kmsg). Maybe it is not a bug, but a feature to prevent accidentally answering the call during the time grabbing it with the finger out of the pocket ;)

Thanks for the feedback.
[Nexus S General] KTamas:
Oh wow I just had this happen yesterday and it kind of freaked me out, good to know it's a known bug, thanks.
[Nexus S General] mon3:
the kernel 3.0.39.27 does not BLN more, this is not implemented?

and there is the built-in Jelly Belly kernel to download?

I use Jelly Belly 1.0 on Nexus S

thanks!
[Nexus S General] :
No, I never included BLN in my default kernel, that was simply a special addition for JellyBelly.

The JellyBelly kernel isn't maintained now development has ceased and there is no separate download for it.
[Nexus S General] :
New blog post here.
[Nexus S General] srthimsen:
Thank you for this, appreciate someone who actually checks the worthiness of patches before throwing them in. As you said, feel and user experience is way more important than latest version number.
[Nexus S General] :
Hmmm, I was guilty of blindly merging stable updates until very recently and dealing with or ignoring the fallout thinking that it must be better to merge the latest code. Not any more!

Actually doing comparisons is scary when you realise how much slower the 'stable' kernel has become in 9 revisions. As I said in my blog post, there's simply too much junk being merged.
[Nexus S General] nexususer1:
Good to know there's somebody like you out there :) i've been flashing every single kernel for a couple of days and now I came back to yours. All those kernels which have 100000000 performance patches and 20000000 features always end up giving me some random and unexpected bugs. Your release has been fast and stable. Keep up the good work, waiting for a "new" 31 kernel;)
[Nexus S General] yxcv99:
I appreciate your decision! All the mobile development seems to be about getting higher version numbers and more features with more unstable code. I'm surprised by this post, but I'm happy about it.
[Nexus S General] :
Further to this post, there is a test release here based on android-samsung-3.0.31 with android-common-3.0 merged in.

It's identical to -27 apart from the lack of mainline stable updates. :)

---------- Post added at 09:05 PM ---------- Previous post was at 09:02 PM ----------

And all the lolbackports for pointless features that we don't even use on Android. :D

But I think AirKernel has at least 100000001 'performance' patches and at least 20000001 'features' to wank over. :silly:
[Nexus S General] knzo:
I hate to be that guy but there's a flaw in the reasoning. While I agree with your decision and on how overrated the mainline updates are (given that most not even affect our devices like you accurately stated in your blog), it doesn't make much sense that they would harm performance and stability at a significant level precisely for this reason.

Considering the boot time varies according to the preboot usage and the user experience perception is highly subjective, I wonder if there isn't a more objective method to analyse the alleged performance decrease following the mainline updates... as surely "proving" this would greatly benefit XDA community and kernel developers' mindset. But ignore me, I'm just thinking out loud. x)
[Nexus S General] :
I see where you are coming from there, and I wondered that myself until I started looking through a few commits. I see lots of fixes in mm and the core kernel for fixes aimed at large machines (like every one of those .39 mm patches). The problem is, we also use that code to a greater or lesser extent, so we are being mothballed whilst the large machines are optimised for, hence the slowdown.

I agree, it was a rough and ready test when I compared boot times, but I only did that because it booted noticeably quicker with .31, so I tested each kernel a few times and the difference was about 15%. I accept there are a lot of variables there, but there is a definite slowdown after merging all the mainline stable updates.

I doubt it will change the mindset of feature list wanking amongst certain developers. It might open some users eyes though and it would be interesting to prove the point, I think bedalus is probably the person to do the comparisons.
[Nexus S General] knzo:
Yeah, well, I hope it flags someone's attention with the time and spirit to look into it as I'd really like some solid numbers to throw around to a few people.
[Nexus S General] atl4ntis:
now that you realized this you should come back to TC 4.4.3 since you're not seeking big numbers anymore and TC 4.6.x is atm worse to build our kernel according to my tests. grats
[Nexus S General] :
I've always seen a slight linpack increase between 4.4.3 and 4.6.x.

I'm using the Google 4.6.x currently for all my devices.
[Nexus S General] karx23:
Hello _thalamus.

What about BLN? Would it affect performance a lot?

Also, I've read in oxygen's forum your thoughts about wiping dalvik cache/cache. Nice to know that. Just flash the kernel and fix_permissions. Am I right?
[Nexus S General] DaXmax:
Is it gonna be a tweaked one? I starting to love your kernels becuz its so smooth on ICS-Mod....
[Nexus S General] :
No, I don't like BLN, I think it is unnecessary and very hackish, which is why I have always said I won't add it.

I didn't add voodoo colour by the way, I just reverted a commit which changed the temperature, so it's at pre 2.3.3 values in my current test release. I do think it looks better, but the colour is nowhere near accurate, the white is very cold and blue, so I won't be keeping it.

You just need to flash the kernel, nothing else required.
[Nexus S General] wmdunn:
Thank you, Sir ... the test colors are quite washed out on my ns4g. Must be the difference in screens. Would still prefer voodoo adjustment ... thanks for such a quick response.
[Nexus S General] jjhrrsn:
Just flashed, running smooth, am interested to see how the battery is as I know will be stable. Any info on the tweaked interactive governor?
[Nexus S General] :
Just pushed a new release, info here.

I backed out of the interactive governor because it's a lot more expensive than ondemand in terms of CPU cycles.
[Nexus S General] DaXmax:
Tested it, it went smoothly and fine on F4k's ICS MOD. Only thing, that sometimes in game, like Temple Run, it lags... Any solution?
[Nexus S General] karx23:
Yeap, I noticed that too. For me, the best overall experience (performance both in games and everyday tasks, SDcard write speeds) is still in favor of 3.0.34_r1 release. It's buttery smooth. I'm sticking with that for the moment.
[Nexus S General] apatal:
Updated OP with link and changelog. Thanks, _thalamus.

Sent from my Nexus S
[Nexus S General] :
Right, so a couple of people say it lags, and others say it is buttery smooth (on the previous page). It either does or it doesn't. I don't think it lags, in fact if anything, stock ICS appears to be less laggy than normal.

Perhaps it is the ROMs you people are using?
[Nexus S General] jjhrrsn:
Anyone that thinks it lags keep in mind max is 1ghz, vs other kernels that you are overclocking upwards of 1.4. Although I don't see any lag regardless
[Nexus S General] DaXmax:
The weird thing is... I used Matr1x, INK and AIR, all always on 1 gHz and they were fine without lags, music also didnt startled too... But its come to your kernel, always there is a hiccup... I wanna use this kernel, but sometime it lags, i have no clues to this at all... So far i know that _thamalus kernel is heavily optimized with no extra governors, extra config and no BLN to make it a fine, minimal, stock kernel. And i loved it, i will try and see what i can do to minimize the lags.
[Nexus S General] chronophase1:
The only time my phone lags is when I use Google Music and stream it. This is with every kernel I've used. No idea why. Probably using a ton of CPU or something. Either way, aside from that scenario , I've never experienced lag using it.

Sent by pocket technology
[Nexus S General] karx23:
First of all, I'm only using _thalamus kernel. It has the best performance and stability.

Ok, just flashed a pretty stockish rom (Bugless Beast), tried for a couple of hours version 3.0.34_r1 and then went to 3.0.36-13. There's definitely some improvement. There isn't any lag, definitely not in games, and it's faster overall. Maybe it was just a bad flash with the previous rom.

Sorry for the bad report. Keep up the good work.
[Nexus S General] ironia.:
stock kernel vs this kernel with stock ics 4.0.4 battery drain?
[Nexus S General] :
I've been running his kernels, including the last two newer builds, on stock 4.0.4 for the last few days without any problems. No lag (though I don't do any gaming) and battery life is decent. I had one reboot after first setting up the phone, but haven't had any problems since then.

I was on Trinity/Rascream for a while, but had weird reboots and freezes without touching any of the kernel's settings, so I decided to go back to stock.
[Nexus S General] spupuz:
are these kernels undervolted?
[Nexus S General] ironia.:
so for the battery thalamus is better than stock??

is manageable through nstools??

tnx you again
[Nexus S General] :
I think it's a little better than the stock kernel, but hard to tell. The biggest difference I can tell (not that I have proof) is that it's smoother. I believe he's tweaked ondemand a little bit, but I don't know enough about kernels to understand most of his changelogs. :)

You may be able to manage the processor speeds through NSTools, but there's no undervolt, BLN, BLD, or anything like that in the kernel.
[Nexus S General] ironia.:
no
[Nexus S General] madd0g:
Aha! So it wasn't BLN who caused instability all along. Now since this is taken care off, can we see it on a .31 release ?

/s

*runs&hides*
[Nexus S General] :
Urgh. Yeah, sure. Over my dead body. :silly:
[Nexus S General] al_madd:
Aha...finally you bought Galaxy nexus...will be busy day after this...

Even I cant red code...I have seen franco and ezekeel using linux version 3.0.8 in a mean time others using 3.0.2x for their ICS kernel...
[Nexus S General] jayjay3333:
Euroskank AOKP comes with 3.0.39-27JB_rel (http://fitsnugly.euroskank.com/?rom=aokp&device=crespo) Makes this ROM fly on my Nexus, despite your blog post. If you roll back to 3.0.31 for the next crespo and it will be as good as you say..oh sh@*! It will be like Mario Balotelli and Sergio Aguero... unstoppable!

:victory:
[Nexus S General] superhil:
Hi _thalamus

which one is for i9023 (with CRT animation fix) ?

I see two files in that directory

Thank you very much
[Nexus S General] nexususer1:
Yep, no crt animation on i9023 on .31 ;)
[Nexus S General] apatal:
Test Nexus S kernel release 3.0.31-28JB

OP updated! Cheers! :good:
[Nexus S General] colonia27:
So? Ain't CRT one of the most useless 'feautures' of all. For me, I never even look at the phone when switching it on or off
[Nexus S General] nexususer1:
Crt animation is stock, why shouldnt it be there?:)btw it's nice, eyecandy :)
[Nexus S General] Ron Overdrive:
Its called a bug. :p its a known issue with the i9023.
[Nexus S General] nexususer1:
Yes, I know it's a bug, I'm just reminding thalamus to fix it, because it was previously done :)

---------- Post added at 01:15 PM ---------- Previous post was at 12:43 PM ----------

Besides this crt bug, 31 seems to have smoother transitions :)
[Nexus S General] :
I'm sorry, I'll get onto it right now... </sarcasm>

I don't need reminding. I know that there is a cosmetic bug with the CRT animation. I also know that I don't like the very hackish fix so won't include it in my standard kernel. You should also know my position from my previous posts on the subject.

I don't have time for this at the moment, but once again my time is being wasted by silly posts on this thread.

I don't really care that the CRT animation doesn't work on SLCD devices. It's a bug in stock too, so it's not like it is a regression in my kernel.

I have 3 other devices, other than the Nexus S. The Nexus S is the least capable and oldest of the devices that I own, yet for some obscure reason, I seem to be spending most of my life on the Nexus S.

If it is absolutely essential to you, feel free to compile my kernel with the fix included and post it for everyone, that way you won't be appearing to be selfish, you won't be wasting my time, you will be helping the community and you will make yourself feel good in the process.

There are plenty of compilation guides on XDA, the commands you will need to get my source, toolchain, apply the patch, build and flash are:

git clone git://github.com/thalamus/android-kernel.git
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6 #### Add -b master if building on 64 bit linux :)
cd android-kernel
git checkout S5PC110-3.0.31-28JB_test
curl https://github.com/jellybelly-rom/android_kernel_samsung_crespo/commit/45f909a1e7d2eb479eb8a7cddcb1fbc783181728.patch | git am
make ARCH=arm crespo_test_defconfig
make ARCH=arm CROSS_COMPILE=../arm-eabi-4.6/bin/arm-eabi-
adb reboot bootloader
fastboot flash zimage arch/arm/boot/zImage
fastboot reboot

Not hard at all, is it?
[Nexus S General] nexususer1:
Well, I didn't want to be rude at all with that reminding. Sorry, if you got me wrong and thought I demanded that fix from you. I just thought you'd want to include that fix since it's been done before.

I love the .31 release, but I'd love it even more with the fix;) unfortunately, even with your brief tutorial I'm still a noob and can't do it myself. I'm sure i9023 users would be grateful if you included the fix:)
[Nexus S General] :
With all due respect, that kind of defeatist attitude is what will keep you as a n00b and is one of my big frustrations about XDA users. Laziness and unwillingness to learn is not endearing. I told you how to do it. If you can't follow that, how did you root your device? How did you even manage to flash any of my kernels?

Read, learn and improve your knowledge!! XDA isn't (supposed to be) just about flashing random stuff.

You could actually do it by copying and pasting my instructions *without* reading anything else providing you have a linux machine handy.

By the way, full quoting the previous post is unnecessary and clutters the thread. :eek:
[Nexus S General] madd0g:
Hm, this made me want to compile your kernel with the BLN, thanks for the commands, I'll see if I can work something out and post it, if someone wants it and you don't mind.
[Nexus S General] nexususer1:
Problem is I'm on windows. Can it be done using pc?
[Nexus S General] :
Sure. If you manage to do it and ask apatal, he can put it in the first post as a community contribution build. Obviously I won't support it in any way though, if it works, fine, if not, it's not my fault. :p

I would suggest that you grab the BLN from the JellyBelly kernel, it's these 4 patches which need applying in this order: 1 2 3 4.

That is what the community is about. Not the "I can't do this because I'm a noob" excuse crap. Meh.
[Nexus S General] madd0g:
I actually compiled whole ROM's using Ubuntu 10.04 in Vmware on Windows. 1hour 30 minutes for whole CM9 on i5 2 cores and 4GB RAM dedicated to VM.

[edit] Here's a great tutorial I used for installing, obviously it's same for JB now, you only need to change repo init to android-4.1.1_r3 instead of 4.0.4_r1

http://www.freeyourandroid.com/guide/compile-ics
[Nexus S General] :
I've never tried compiling a linux kernel on Windows. I don't imagine it would be successful though.

You could use VMware Player though...

There are no problems, only solutions.
[Nexus S General] madd0g:
Sure, I'll be the one to blame :] Was looking at BLN commits on bedalus github, forgot about jellybelly git, this is more then helpful, cheers.

Yeah, it's sad how people don't invest more time/effort into reading and not asking questions.
[Nexus S General] apatal:
Just a suggestion: If you're applying the BLN patches, might as well make it such that it's on by default, just to stick to the spirit of the base kernel which is best when used as is - no need for buggy utilities (yes, I'm looking at you, nstools!)

Oh and don't bother with the blinking effect, which is unnecessary IMHO. Cheers!

Sent from my Nexus S