yashsingh1/xdaforums huggingface dataset:
[Nexus S General] madd0g:
IMHO, I don't actually see a point in making those "n00b how-to's". there's enough info already.

If someone with enough knowledge wants to do it, he'll find the resources, put them together, learn something on the way and will succeed eventually. If anything can come out of this "anyone can build a kernel" is a ton of "my l33t kernal version 43.32", like most of the ROM's out there, with the "zip developers" or zillions of kangs. Quality > quantity.
[Nexus S General] knzo:
Before XDA turned to an after-market service users think they're entitled to, it was a board where you shared knowledge, information, feedback and opinions. That being said, I can't imagine why you would be against the creation of such educational guide, especially when you built a kernel through a summarized one posted by thalamus. Is it perhaps now that you do know how to build it you don't want to lose the "spotlight"?

P.S. I also wrote one of these guides some time ago but it also has a few useless steps (like the packages for building android). Anyway, I'm all for it, no more releases, let the users be proactive and build it if they want teehee.
[Nexus S General] madd0g:
You mean like every other kernel out there who's full of tweaks, because more stuff added = better ?

PROGRAMMING AINT EASY.

It can't be tought in a tutorial. You get to know the building blocks, but to actually code something you need a deep understanding of hardware and software you're working on, not just pasting something together.
[Nexus S General] FloHimself:
Do a forum search for "compile kernel from source". XDA is full of guides that show how to build a kernel. So the knowledge is already available. It's just wasted time to write another guide for the lazy and impatient.
[Nexus S General] Randomwalker:
Exactly, ppl. will see that it doesn't take much to build one of those and the feature lists will perhaps no longer inspire so much awe in contrast to the actual programming you are talking about.

For that matter nothing can be taught in a tutorial, but tutorials can be helpful in understanding, just as good tutorials can augment even the best of lectures. Yes, you will always have those that will only "consume" the tutorial in search of a ready made recipe, but that's their loss.
[Nexus S General] madd0g:
First of all, I don't give a flying **** about a "spotlight", because I did the BLN addon for myself. I've said it many times that all the thanks go to _thalamus, because he did the actual work and reminded a user to state his name in the signature, not "kernel madd0g@asusULTS". I posted it in a "thank you" way, because _thalamus bothered with posting his instructions and helped with BLN commits and how to make it compatible with JellyBelly.

Let me explain why I wrote before about the tutorial. You said that it's a board for sharing knowledge and information, I agree on that. But nevertheless if there's 1 million tutorials out there posted, there will still be certain lazy individuals who just don't have enough CS knowledge to do it. Not everyone is for it and some of them will never be and copy pasting **** together certainly doesn't bring anything new to the table. If someones intention was to build something new, he would done it already, because that knowledge is far beyond something needed to install linux in a VM (for instance).

There are countless tutorials for how to root the device and people are doing it by them. That's kewl, easy way to root, yeah. But most of them HAVE NO ****ING IDEA WHAT THEY'RE ACTUALLY DOING (I had to write this in caps). They don't know, they just follow the text written there. And after something goes ape ****, they don't bother looking for a solution, THEY EXPECT IT (just like in the "simple root how-to no. 29192"). And you call that education ?
[Nexus S General] albundy2010:
Can't we do/discuss anything without turning into a argument?

Hell maybe xda should lock the entire q and a forum for the device as well. Being that all the info and all ?s have already been asked and answered numerous times already also?
[Nexus S General] madd0g:
You've just described an issue for all forums like this one, which is around for some time. A web forum ain't the optimal way for this. On the other hand a wiki + github with it's bug tracker would be more appropriate to host the files and maintain support for projects, not wasting time on countless mindless questions. The maintainer could then only post a informational thread on forum(s), but wouldn't participate in the discussion there.
[Nexus S General] :
Hmmm, I like that idea actually. Github has wiki, issues and pull request features in the rare event someone decides to contribute.

It would be a lot easier to manage than an XDA thread too.

I'll look into that.
[Nexus S General] FloHimself:
For zipped kernel releases the github download sections could be used.
[Nexus S General] :
Most of it. It's too much blah blah blah and not enough nitty gritty. As I said, it's a wall of text, an uninteresting wall of text at that.

You are also completely wrong about the GPL requiring people to maintain a git account.

If someone takes my source, changes some config values and releases a kernel based on it, all they have to do to be compliant with the GPL is state what tag or commit the kernel was built from and state the configuration values which have been changed, so that anyone who wanted to could replicate that binary.

If someone takes my source and adds 3 patches to it, to be compliant with the GPL they simply have to state what tag or commit the HEAD of the source was and provide a link to the patches or a tarball of the patches. That is it.

The GPL simply states that source must be available which will reproduce the released binary. Both of the above approaches achieve that and neither requires forking on Github.

Technically, to reproduce the binary properly you would also have to include details of the toolchain used, or build instructions for said toolchain, but I think that is being anal about it.
[Nexus S General] knzo:
Sadly there are still many developers throughout this forum that don't share the config file.
[Nexus S General] :
If they do that they are breaking the GPL so XDA should close their threads.

I encourage you to report them or PM me about them and I'll happily report them if they are in breach of their GPL obligations.

Some of us take the GPL seriously, those that don't shouldn't be referred to as developers.
[Nexus S General] rift999:
I got a forced reboot on the burnsa rom the very second I tried to underclock to 800 in nstools
[Nexus S General] :
Don't use nstools. It doesn't work with my kernel. It causes issues. There are several discussions about it in the thread already...

I do love the way you came on here saying it in such a way that it is a kernel issue though lol. No, sorry, it's because nstools is crap.
[Nexus S General] rift999:
My apologies. I meant nothing against your kernel. I should have searched the thread.
[Nexus S General] :
Fair enough, I just found it a bit amusing. But yeah...NStools = bad when it comes to my kernel.

I'd love to know what it actually tries to do which causes a reboot. SetCPU has no such problems. I might investigate the NStools issue just for my own curiosity.
[Nexus S General] :
I learned new respect for development by trying to do some. If more people on xda actively build and share stuff, even at a basic level, there'll be more development talk and less whining about eta's and feature requests.

This is genius though. An idea this good ought to exist already.
[Nexus S General] :
There wasn't any need to though. I've said several times that NStools causes problems, yet people still choose to use it then come and complain on this thread.

With your post, you aren't adding anything which people didn't already know and which I haven't said several times on this thread already. Or perhaps what I say isn't good enough and needs 'confirmation' every time... :rolleyes:

If I need confirmation of something, I tend to ask for it. Otherwise it is generally unwelcome.
[Nexus S General] madd0g:
+1

Github awaits ;]
[Nexus S General] Andy:
Regarding the recent posts in this thread.

I don't care who you are, or why your here at XDA. Either post like an adult or do not post.

You all have had enough warnings from me. I've been lenient. Bans will be next.
[Nexus S General] :
It's also absolutely nothing to do with the kernel in any way, shape or form.

So why is it being discussed here?

This is a kernel thread. Not a general chit chat thread and certainly not a ROM thread.

Why is JellyBelly being discussed? Why are ROMs & ROM issues being discussed? Are people utterly incapable of staying on topic, seriously, how hard can it be to stick to the topic? I really despair.
[Nexus S General] crazyfool_1:
I have a question. I have searched the thread and read the op as well as the trolling (lol) and couldn't see it asked or answered before. So forgive me if it has.

Would you consider or do you have any intention to add mtp into your kernel? From my understanding it is implemented in the kernel and not in the rom. I know you don't want to clutter your kernel with pointless features which I agree with, but mtp is a useful and functional feature, imo obviously.

I don't know how the code is to implement it for the nexus s however, whether its hacky or not, might cause more problems then its worth.

Edit: Just read its not compatible with Idle2? If so guess I answered my own question then, battery saving from idle2 (I use my phone for music alot) vs mtp.. no contest.
[Nexus S General] :
MTP is implemented by the ROM, specifically within the ramdisk.

The kernel already includes the support...
[Nexus S General] crazyfool_1:
Hmm.. my mistake then. Thanks.
[Nexus S General] veyka:
Thread has been cleaned of most recent OT discussion.

Unless it's related to THIS KERNEL, then it doesn't belong here, that means no chit chat about roms, they all have their own thread for that.

That means let's keep the "I LUFF U HAV MAI BABIS" posts out of here as well, that's what the thanks buttons for.

In general, if it's not constructive and related to this kernel, just don't post it, if in doubt don't post, its simple.

Lets not waste the developers time, the time of people who bother reading and not posting, OUR (the moderators) time in cleaning up the nonsense, and finally, your time, in typing something that's pointless.

XDA is about development, first and foremost, we just happen to allow end users to access the forum, don't abuse this, it's a privilege not a right.

Now, lets get back to business and happy hacking :good:
[Nexus S General] :
I don't know if it is or not. It wasn't compatible with the method bedalus was using, but then again, that could likely have been something else which was causing the issue and may have been absolutely nothing to do with MTP, which is why I am dubious of that result.

I won't know until I test myself, which I will do soon.

After getting my Nexus S back today, I have been working on IDLE2 and testing and with my latest changes, it is spending about 80% of the time in TOP OFF mode whilst music is playing with the screen off, with the frequency forced to 400MHz.
[Nexus S General] Maxxd01:
The i9023 available there is for JB or ICS ROMs?

I ask because I applied in my i9023 over a ICS rom and I got a bootloop.
[Nexus S General] :
Lol. Take a guess. What does it say in my release blog post?
[Nexus S General] coluichepensa:
I want just report I haven't any problem with the 3.0.31. 28.

Great job. Clear, simple, fast and stable.

Thanks again thalamus for sharing with us
[Nexus S General] polobunny:
Well, I get a "post thanks action deny" on Tapatalk, so here's a written THANKS for the work you've been putting on the Nexus S.
[Nexus S General] :
I built a kernel with the only difference being mtp/ptp removed from the ramdisk. At this point IDLE2 worked.
[Nexus S General] srthimsen:
Had a reboot this morning, had just tried to update an app and shut the screen off. When I checked my phone awhile later, it had rebooted and was showing an update for that same app.

Last_kmsg is here: https://docs.google.com/file/d/0B52f9BiiVczcbmIzNTZLQnVoYnM/edit

Edit:

Sorry, had permissions for google drive wrong - anyone can now view the file.
[Nexus S General] :
There isn't anything in that log which would suggest a kernel issue. It just looks like a normal reboot.
[Nexus S General] simms22:
agreed. looks like a simple derp from the phone, the kind that a reboot usually fixes.
[Nexus S General] stojshic:
I know you do not support kernels that are modified versions of your kernel, but maybe you could look into this? I use modified version of your kernel that came with knzo's version of AOSP ROM. If you could look into it, I would be grateful, if not, and it's against your principals, not a problem.

Anyway, I did nothing with my phone, I just got it out of my pocket, and it asked for PIN, it hard reboot-ed 30 mins ago....

Thanks

http://db.tt/yamSuJm3
[Nexus S General] knzo:
The modifications are the same that madd0g made: CRT fix and BLN, both in the JellyBelly kernel.
[Nexus S General] simms22:
bad link
[Nexus S General] :
There is nothing there which tells me what happened. And no, I don't support anything other than kernels I build myself, it would be a minefield otherwise.

I don't object to looking at last_kmsgs though, if I have time.
[Nexus S General] :
Er, yeah. Thanks for that. If I had wanted them advertised on XDA I would have written my own post. I don't need assistance with that kind of thing.

And what on earth are you doing flashing stuff you know nothing about? I could have been testing *anything* there. How do you know they wouldn't make your phone explode?

Seriously, people, think before action and don't advertise my unreleased work without my permission, which *will* be withheld.
[Nexus S General] veyka:
Lets keep this on topic, that means Nexus S, and this kernel only.

Also before posting random things, take a moment to think, if the developer wanted them widely available, they would have posted them themselves.
[Nexus S General] irminsul:
Sorry, sorry. My bad. Excuse.
[Nexus S General] Gitah.:
I just got a reboot while talking on the phone. I'm using madd0g's mod 3.0.31-28JB_test-00004-gca65d93.

Here's the last_kmsg.txt.
[Nexus S General] :
Yeah, I can see the problem. IDLE2 is enabled. I didn't enable that for my .31 release because I didn't think it was stable enough and there were quite a few unfixed bugs with it. Unfortunately, it seems madd0gs release has it enabled.
[Nexus S General] madd0g:
Got a PM from gitah about the crash, the IDLE2 commits are in the kernel I cloned : https://github.com/thalamus/android-kernel/commits/S5PC110-3.0.31-28JB_test, so just reverting those from last to first would work ?
[Nexus S General] knzo:
Use the stable defconfig, not test. Make sure that IDLE2 is disabled before you build.
[Nexus S General] madd0g:
Wouldn't changing to CONFIG_S5P_IDLE2=n be enough ?
[Nexus S General] :
Just use the stable defconfig. And no. That isn't how you unset a config variable.

Look at the rest of them, how many others say =n ? None.

# CONFIG_S5P_IDLE2 is not set

is the correct way to disable it, but that is already done if you use the stable defconfig.

make ARCH CROSS blah blah crespo_release_defconfig before you make the zImage. Easy.
[Nexus S General] madd0g:
Yeah, wanted to do that, but wasn't sure if IDLE2 was the only difference between them. Better to ask and learn, then blindly experiment around, thanks.

[edit] Updated original post with new version.
[Nexus S General] Ibn Saeed:
Which file to flash

kernel-S5PC110-3.0.39-27JB_rel.zip

kernel-i9023-S5PC110-3.0.39-27JB_rel-1-gfdf9f98.zip

I am running a JB ROM on my Nexus i9023. Why are there 2 versions ?
[Nexus S General] TG2708:
I would say flash the one that has your phone model in it. The different versions might be specific fixes or patches.
[Nexus S General] Ibn Saeed:
Just flashed the i9023.

So far good. The phone feels a bit snappier especially while opening apps. I am using it with Dario's Rascarlo JB ROM
[Nexus S General] apatal:
Maybe you can try using this release instead. It's rolled back to .31 base and my testing shows some improvements on battery life.

Sent from my NexuS
[Nexus S General] Ibn Saeed:
Thanks, ill try that. But i wouldnt i need a i9023 file for .31 release?
[Nexus S General] degiovab:
The only difference is the crt fix (which is required only by i9023) and it's not available for the .31 kernel: reason explained here

http://xdaforums.com/showpost.php?p=30078094&postcount=992
[Nexus S General] rasengan82:
http://db.tt/HVRDBabo

Got a reboot. Latest test .28 JB.
[Nexus S General] _imac_:
Is it compatible with stock 4.1.1 JB ?
[Nexus S General] apatal:
Not really since thalamus has optimized the code and removed unnecessary stuffs from the kernel.

Sent from my NexuS
[Nexus S General] _imac_:
What do you mean? Completely not ? Or It should works but with some bugs ?
[Nexus S General] cadarn07:
I though stock was specifically what he tested on and therefore the best to be running the kernel on?
[Nexus S General] apatal:
Oops sorry I misread your last post. Yes it's compatible with stock. I've tried it with rooted stock ota.

Sent from my NexuS
[Nexus S General] robrob777:
Just for feedback, I installed the latest version yesterday (never tried the kernel before), Today at work phone went to sleep of death, can't wake up, tried calling it and nothing.

I wonder why, so far i was using hypotalamus 7.28(_thalamus base) with no problems, but I wanted something w/o voodo.

Stock 4.1.1 i9020T
[Nexus S General] apatal:
If you haven't rebooted your phone since the SoD occurred, please post your last_kmsg here so the dev can analyze what happened better. you can find the file in /proc folder in root.
[Nexus S General] rasengan82:
Just in case this was missed.
[Nexus S General] :
Man, don't bump stuff. When do I miss stuff? If I don't reply it means I either don't have anything to say or I don't have time to reply immediately.

Yes I saw it, yes I'm rather busy, no I didn't have time to reply and no, I don't know why the **** that is still happening because I added a check in for it.

I'll have another look when I get a chance.

Edit: And why post it on here when you are in my irc channel? Lol.
[Nexus S General] rasengan82:
LOL my bad my bad. I forgot about the IRC ;)
[Nexus S General] :
Test build

So, a test build with idle2 enabled and working.

Yes, it does save power, a substantial amount in fact, as I found when I broke suspend and the idle power usage only increased by 50%.

No, I'm not entirely sure about it's stability.

No, I'm not listing what has changed down to fine detail, you will have to look through this branch on Github yourself and read this thread. I have no time to be writing changelogs. Quick and dirty changelog is merged android-common, idle2 v0.370, bugfixes.

No, you probably shouldn't flash this unless you are prepared to encounter problems.

Download here.
[Nexus S General] apatal:
OP updated! Cheers! :)

Sent from my NexuS
[Nexus S General] deani77:
I was on latest test kernel... it weird to see it stays at 800mhz when charge using USB. Normally it stays at 100mhz
[Nexus S General] :
Working as designed then. Notabug. :)
[Nexus S General] mpjoe2000:
i charged my phone last night until 90% and leave it all night long, only data, wifi and 3g on
[Nexus S General] albundy2010:
What is the reasoning behind locking the frequency @ 800mhz during USB charging?
[Nexus S General] :
^^ Applies here. I know about the drain issue. I'm working on it.

---------- Post added at 06:52 PM ---------- Previous post was at 06:51 PM ----------

To save a ton of unnecessary CPU frequency transitions. No point in thrashing cpufreq when the core is power gated, as the frequency is meaningless in that scenario.
[Nexus S General] ADJack:
Flashed the latest IDLE2 test. Was pretty much rock solid stable prior. Phone signal gave out at about 9 hours post-flashing and was getting an error while trying to scan for my network thereafter. A chance that it is the kernel but I post this as a heads-up; it could be an isolated case on my part (will continue to use to try to replicate issue). I managed to dump logcat and dmesg but not last kmsg (not found) . Will link on request but waiting to see if others have similar experience.
[Nexus S General] :
That's irritating. I thought I had fixed that issue.

Well, put it this way, I *have* fixed it as far as my device is concerned, which used to do that on a regular basis.
[Nexus S General] albundy2010:
Makes sense. I was not aware that when CPU spy reports 800mhz that it was powergated.

Just had the screen freeze( while screen off) and it rebooted. Was just about the pull the battery before it rebooted on its own. On the latest pre compiled idle 2 kernel ( test 54) Was running fine till then so I suspect it wasn't kernels fault but here is the last ksmg if you want to check it.

http://db.tt/YC8miZAK
[Nexus S General] :
Nothing in there that suggests an issue. Although, I think the stat collection can cause hangs and resets, so I'll be disabling it in future builds. It's only for debugging anyway, and it's expensive.
[Nexus S General] srthimsen:
Been running latest test build with idle2, and have noticed a modest battery life improvement (very subjective).

One thing I did notice is that if you shut the screen off while using navigation app, it doesn't give you turn instructions on time... it told me to turn about a mile after I did! My assumption is that idle2 would cause this, as it worked properly previously. Small price to pay for idle2 implementation.
[Nexus S General] :
New Test release here

It contains IDLE2 v0.380 and a few wifi fixes from android-common.

It seems stable.
[Nexus S General] srthimsen:
Do you happen to have md5 for this? Thinking I got bad download, refuses to wake when screen goes off.
[Nexus S General] :
Your latest experimental kernel is very unstable on my crespo. Power on, screen timeout and the screen stay off. I must remove battery.

I'm on latest CM10 nightly.
[Nexus S General] :
Bah. I bet if you held a wakelock it would work perfectly. God damn suspend again.

Fixed and working. It was nothing to do with idle2, just some config changes that I made. Disabling the FIQ debugger is seemingly a bad thing and as I have being testing the efficiency of idle2, I have had a wakelock held for 5 hours and it never went into suspend, hence why I missed the bug.

New link here.
[Nexus S General] albundy2010:
Had a SoD and had to pull battery and plug the phone back in for it to boot at all.

Last_ksmg seems useless. It has 2.6 cm kernel mentioned in there and just looks all wrong. http://db.tt/YC8miZAK. Be shocked if that is any use at all but there it is anyways
[Nexus S General] jojoost:
Do we have to toggle wifi on the latest IDLE2 build with IDLE v0.380?

---===:::Greetzz, jojoost:::===---
[Nexus S General] :
Alas yes, the stupid bcmdhd bug still exists. :(

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

Linux version 2.6.35.14-cyanogenmod-g1ad182f (kalimochoaz@KalimochoAz-HPUbuntu)

I feel dirty now after looking at that, I'm going to have to wash my eyes.

Anyway, the bug is fixed. It was my error.

By the way, IDLE2 uses about the same amount of power as suspend now, about 1% every 45 mins.
[Nexus S General] simms22:
washing your eyes with sulfuric acid might not even help you with that.. :silly:
[Nexus S General] :
Everything works fine now!
[Nexus S General] kwibis:
Bit confused now what to download. The last link you posted thalamus?
[Nexus S General] srthimsen:
Yes, last link.
[Nexus S General] tymonn:
I'm using your kernels for a time now and I love them :)

I'm sorry if this is a noob question but how do i enable IDLE2?
[Nexus S General] deani77:
AFAIK thalamus kernel will automatically enabled all it features. Because of that you will no need for 3rd party apps for this kernel.
[Nexus S General] apatal:
Yep, but don't forget to toggle WiFi on/off after boot, just to work around a bug that's been causing some issues for some.

Sent from my NexuS