yashsingh1/xdaforums huggingface dataset:
[Nexus S General] atl4ntis:
Since you like to fill your mouth with words here's my small thoughts.

You blame pseudo developers cherrypickers fooling ignorant (as developers) people about them development. All right, this is more or less what you do aswell, plus talking **** about others and acting like you've done lot of things.

Can you please pointing me out what you actually successfully developed on nexus s kernel?

tweaking values --> not kernel development

fixing compilers warnings (most of them reverted) --> not kernel development

adding likely here and there --> not kernel development

idle2 --> porting and isn't working

hotplug? is that all, also dunno much about it , i didn't follow it lately.

Seriously, what did you actually have done for the nexus s community?

From my perspective there are 1 2 real developers, the ones who actually wrote some code, code that is universally recognized and that everyone uses on his kernel, like color control, fast charge and so on.

Is funny also how people talks **** about cyanogen but every ****ing rom has something from it. Could you imagine android world without cyanogen? No Powerwidgets, Quadlocks and so on.

Also really did you spent so much time teaching Bedalus how to compile a kernel?

Last time i compiled mine what you had to do was pulling the source, the prebuilt toolchain, and run make with config and few flags.

3 ****ing mindless steps.

Yeah man you rocks.

Last but not least, you once pointed out another developer, how he was great and how he was one of the real ones... I don't want to name and shame, but he's more or less a cherrypicker aswell.

Adding a module control or tweaking values is NOT kernel development.

Rest is cherrypicked.

Also no config plus that attitude you pointed in your blog monologue, releasing "test" version without releasing the code because it's too good lol.

At least don't be biased.
[Nexus S General] crazyfool_1:
Dunno why you waste your time replying to these trolls mate.. Just wanted to say thanks for your work, been using your kernel ever since 4.1 came out and I've had i think once black screen.. one.. awesome work. I'll be upgrading to a Nexus 4 soon, hopefully I might see you there :)
[Nexus S General] nibla101:
Oh LOL, this was me exactly when I was reading the last posts.

Anywayz, time to lock this thread maybe?
[Nexus S General] apatal:
My thoughts exactly. I'll be getting in touch with one of the mods soon.

Posted using xda mobile app
[Nexus S General] simms22:
that would be ideal in my world :silly:
[Nexus S General] atl4ntis:
aint u using RasBeanJelly (nice rom) which is made 99% from CM an 1% from PA?
[Nexus S General] simms22:
more like mostly aosp and the few mods from cm. but i dont use the few included mods at all, id rather have it pure aosp with rasbeans theming and volume rocker wake. anyways, im not using anything on my nexus s anymore, hurricane sandy swept it away(and my ns thought it was a submarine).
[Nexus S General] atl4ntis:
yup i meant the things added are 99% cm, non that's 99 of cm... anyway hope you're fine, you're a nice and helpfull man. Also was talkin about your gnex :p
[Nexus S General] simms22:
yea, im alright. sandy might have destroyed my apartment, and taken all my things, but im not hurt in any way physically nor mentally. strong i am! it could even be a blessing in disguise, since i get to start over completely. i did get to grab my backpack before i took off, my gnex and nexus 7(also running rasbean) are safe. i literally ran from the water(i saw the water breach, ran grabbed a backpack with a few things, and ran off). whoever said that you cant outrun a flood was wrong ;)

thanks for the thought :)
[Nexus S General] MrMat:
Hi guys,

I'm searching for the missing CRT-animation fix on latest Nexus S JB 4.1.x stock kernel..

I've opened a thread about it in Nexus S Q/A section but it's hard to find a solution ... The only thing that I read all over the web is "flash any other custom kernel"..

heeeeelp meeee please :laugh:
[Nexus S General] :
I was pretty pleased with my patch to fix the GPU resetting the users minimum frequency to 200mhz. I shared it with r_data.

I came up with a crt animation fix, that works differently depending on phone model. I emailed that to morfic.

Any chance of a little help? I think I recently introduced some sort of unstable tweak that's been causing reboots. I began at the same time I introduced fast charge and bigmem. Maybe you could take a look through my git log and identify the problem?
[Nexus S General] simms22:
random type of reboots or reproducible? anything of interest in any last_kmsg?
[Nexus S General] :
More than you, you prick.

More than you, you prick.

Seriously, why don't you just **** off and die.
[Nexus S General] atl4ntis:
lol you didn't answer... but you made my day, thank you :D
[Nexus S General] The-Captain:
Guys, please before anything breaks out, use that report button! Keep things from getting bad. I can't see everything! I'll be keeping a better eye on this thread, but I can't see everything! Thanks!

- The-Captain
[Nexus S General] leap_ahead:
thalamus get banned?
[Nexus S General] ej8989:
He requested for his account to be removed from the forums.
[Nexus S General] mdean1981:
Probably better that way. From reading his post here and on his blog the guy seems to have some XDA hate issues. Better to just let it rest and maybe even close the thread.
[Nexus S General] MrMat:
So, no one can help me??? "The force is strong.. with me".. I cant surrender guys :D
[Nexus S General] :
http://xdaforums.com/showthread.php?t=1719775

My kernel has that fixed.
[Nexus S General] MrMat:
Thank you bedalus for your reply.. It's an honor :D

but, I'm searching for a "patch" or something like that to "fix" STOCK kernel..

I have to give it up??

Thank you, anyway ;)
[Nexus S General] Articudos:
I guess this is what you need,

It's compact Kernel.

http://xdaforums.com/showpost.php?p=32963771&postcount=251
[Nexus S General] :
Oh, i see: https://github.com/bedalus/marmite/commit/3424f9db66e7d01b3e2458bd70cef966cf8e2b60

It's not a very clean patch because it removes my first attempt. You just need the two added lines, and the msleep line.
[Nexus S General] MrMat:
OOOkk, this is what I looking for.. Some weeks ago I founded this, but I lost it in a minute :D

Thaaaaank you for your support... I don't know why there isnt any stock fixed kernel whitout any mod... the Kernel posted by Articudos is the one from 100,1% and has bigmem, powerhal etc...

Thankyou again.. I appreciate it!!
[Nexus S General] waterface:
I suppose you could pull the boot.img from a stock .tgz from Google and flash it via fastboot?

Or you could get SimpleKernel, stock 4.1.2 kernel with just BLN, BLD, CIFS module and voodoo added.

Link: http://xdaforums.com/showthread.php?t=1420542
[Nexus S General] Ted Mosby:
No BS, everything works so smooth and battery is slightly improved. Great work thalamus.

4.1.2 stock + thalamus 3.0.31(Oct16).
[Nexus S General] rasengan82:
Anybody has a copy of the latest kernel 4.1.2?
[Nexus S General] ej8989:
Here: https://www.dropbox.com/s/mlc10xyx1...3.0.31-666_rel-9-g76bb0a5-20121016-213036.zip
[Nexus S General] deani77:
Working great on Rasbean 4.2.1:good:
[Nexus S General] rasengan82:
Does the latest kernel work in 4.1.1?
[Nexus S General] madd0g:
All JB kernels are interchangeable.
[Nexus S General] rasengan82:
As always... smoothest kernel ever.
[Nexus S General] mssngr:
Has anyone got thalamus kernel working on CM10 stable? I remember thalamus stating not being happy with the course the CM team was going. Just curious.
[Nexus S General] apatal:
You can't use thalamus kernels on CM and cm-based ROMs as it doesn't have support for the custom ioctl.
[Nexus S General] mssngr:
Thanks for the quick reply! Not sure what custom ioctl means, but to bad, I've been very satisfied for a long time with the kernels from thalamus.. Would it be compatible with Paranoid Android, AOKP or PAC? I ask because I use PDroid security and it can only be patched with AOSP builds. Thanks in advance.
[Nexus S General] wmdunn:
Actually, you can use Thalamus' kernel on CM based ROMs. Here's a link to the info ...

http://xdaforums.com/showpost.php?p=35457168&postcount=14402
[Nexus S General] mssngr:
Thanks! I will definitely try this! :thumbup:
[Nexus S General] apatal:
Oh OK. Yeah saw that before. I supposed you can try that. :)
[Nexus S General] mssngr:
Worked like a charm! :)

Thanks a lot, really happy I can keep on using thalamus' kernels. :thumbup:
[Nexus S General] Ted Mosby:
Del
[Nexus S General] malick186:
Nice
[Nexus S General] NexScroogled:
Hi,

Is there someone who has the last stable kernel release by Thalamus?

The last version that he published on his blog is 3.0.39-27. Unfortunately, the link to download it is dead.

Thanks
[Nexus S General] ej8989:
I believe i posted it in the previous page a year ago.

Anyway, here: https://www.dropbox.com/s/mlc10xyx1...3.0.31-666_rel-9-g76bb0a5-20121016-213036.zip
[Nexus S General] NexScroogled:
Thanks ej for the link. Indeed, I have already found your dropbox link. Unfortunately, it's the version 3.0.31 of the kernel. I am currently using it on a Nexus S and it makes Android 4.1.1 work much faster.

Thalamsus published on his blog, on the 4th of August 2012, the last stable version (3.0.39) of his kernel before pulling the plug and removing it from server where it was hosted.
[Nexus S General] spider623:
Try using internet archive
[Nexus S General] NexScroogled:
Thanks spider for the info.

I didn't know that Archive.org was offering this type of archival service.

I gave it a try and all the the links in the archives are dead.

Good try!
[Nexus S General] Fast-Droid:
Final Thalamus Crespo Kernels (3.0.39-27)

JB https://www.dropbox.com/s/au1zzcjgefd04id/kernel-S5PC110-3.0.39-27JB_rel.zip

ICS https://www.dropbox.com/s/wvuulrdx2t84r5e/kernel-S5PC110-3.0.39-27ICS_rel.zip

i9023 https://www.dropbox.com/s/dcdcogv9jhu0s0r/kernel-i9023-S5PC110-3.0.39-27JB_rel-1-gfdf9f98.zip
[Nexus S General] apatal:
Oh and by the way, OP updated!

Cheers! :)

Sent from my Nexus S
[Nexus S General] :
People misunderstand what the dalvik cache actually is and what function it performs. It has absolutely nothing to do with the kernel and absolutely nothing to do with any native (non java) code what so ever. It also manages itself the vast majority of the time so doesn't require to be interfered with. It's very very rare that the dalvik-vm will get so confused that wiping the dalvik-cache is necessary to fix a bootloop, and that is the only time that there might be a need to try wiping it, but generally when the system is in that state it's either time to change the buggy ROM, or it's time for a full wipe anyway.

The dalvik-vm knows when the dex files aren't the matching one for the relevant jar or apk and regenerates them on the fly without user intervention, so another reason not to habitually wipe it.

All that wiping it achieves is making the next boot much longer as all the dex files are regenerated.

Kernels shouldn't require any form of wipe when they are installed. Kernel updater-scripts simply install the modules into /system (mine clears old ones out first) and then dump the boot partition, split it into kernel and ramdisk, sew the ramdisk back together with the new kernel to make a new boot image and then write said boot image to the boot partition.

None of that does anything which necessitates any form of wipe afterwards, because it doesn't touch anything other than the zImage in the boot partition and the kernel modules in /system.

As regards wiping, being forced to fully wipe shouldn't happen to often. I'm the master of not wiping unless absolutely necessary, because it's inconvenient and due to that I haven't wiped in months.

If changing to a completely different ROM, such as AOSP based to CM based, it's probably advisable to wipe, but not entirely necessary unless you encounter issues, ie crashes or a bootloop. It also depends what features and options have been used in the ROM.

As regards wiping cache, generally a waste of time, Android manages the cache and deletes stuff out of there on a regular basis (every time something triggers DownloadProvider). If doing a full wipe you might as well wipe it, or if you have a specific reason to do so, ie, it is full for some obscure reason. Otherwise, I personally wouldn't and don't bother.
[Nexus S General] ironia.:
i have flashed 3 hours ago the latest version on ics stock over kernel stock without any wiping
[Nexus S General] chdeul:
Hello,

this kernel is compatible with CM9? I have a boot loop on google logo. CM9 23/06/12
[Nexus S General] heX79:
Thanks for better explaining the management of the cache and dalvik, that first boot was a welcomed relief!
[Nexus S General] :
No idea to be honest, I don't like, use or test on CM. It *should* work though, assuming they didn't break something...

I can't see why you would get a bootloop though unless it's panicking and rebooting over something. If you provide a last_kmsg I'll be able to tell.
[Nexus S General] ironia.:
Sttange thing happens...ran clear cache app from titanium appear a Black wallpaper after a whilec..many su popoup notification...toggle disappears ...after everything works ad usually any relation with the kernel?

Tnx
[Nexus S General] apatal:
Nope. Just reboot. Next time, avoid clearing system cache while the phone is turned on. In fact, according to _thalamus in the post above, you don't have to clear cache at all, unless your planning a full wipe. Otherwise, it's not needed.
[Nexus S General] y3mita:
Been on this kernel all day, am a trinity fan for a long time.

I do find this kernel snappier than 1.1 latest trinity.

Things i miss *awesome* colors, since morfic managed to integrate the best dark colors on his.

BLN greatly missed, i wish there was a way to manage blinking and duration of lights.

So far battery is about the same as trinity, ill post a screenshot soon.
[Nexus S General] y3mita:
With trinity I can get pass the four hours with heavy usage.

I do love the smoother experience with thalamus though, I thank you for sharing your work with us.
[Nexus S General] wickid_d:
Here here! I pretty much live by these rules already.. :D GREAT explanation! Took the words right out of my mouth.. erm.. fingers.. yeah.. lol A million thank-yous, as this is what I try to stress to people!

Awesome little write-up! I'm going to be checking out your kernel VERY soon. Just waiting for some other downloads to get done as where I'm only running off of 4g at the moment.. (don't ask..)

My only question: I noticed this is in the regular s forum - is this compatible with the s 4g as well? Or do you have another version for that?

Thanks for the great work! :)

Peace,

~WickiD~
[Nexus S General] apatal:
Same one. His kernels are compatible with both GSM and 4G versions. :)

Sent from my Nexus S
[Nexus S General] ironia.:
I have not rebooted, after (crash!?) always works normally

06-26 23:52:46.257 E/su (15218): sudb - Opening database

06-26 23:52:46.257 E/su (15218): sudb - Database opened

06-26 23:52:46.257 E/su (15218): sudb - Database closed

06-26 23:52:46.265 D/su (15218): 10092 com.keramidas.TitaniumBackup executing 0 /system/bin/sh using shell /system/bin/sh : sh

06-26 23:52:46.277 I/ActivityManager(132): Process com.jim2 (pid 13584) has died.

06-26 23:52:46.277 W/ActivityManager(132): Scheduling restart of crashed service com.jim2/.UpdateService in 38408ms

06-26 23:52:46.285 D/Zygote (79): Process 13584 terminated by signal (15)

06-26 23:52:46.316 W/Smack/Packet(9629): notify conn break (IOEx), close connection

06-26 23:52:46.363 E/su (15220): sudb - Opening database

06-26 23:52:46.363 E/su (15220): sudb - Database opened

06-26 23:52:46.367 E/su (15220): sudb - Database closed

06-26 23:52:46.379 D/su (15220): 10092 com.keramidas.TitaniumBackup executing 0 /system/bin/sh using shell /system/bin/sh : sh

06-26 23:52:46.386 I/com.keramidas.TitaniumBackup.n.ap(13479): Listing running processes

06-26 23:52:46.449 E/JavaBinder(132): !!! FAILED BINDER TRANSACTION !!!

06-26 23:52:46.496 E/su (15222): sudb - Opening database

06-26 23:52:46.496 E/su (15222): sudb - Database opened

06-26 23:52:46.500 E/su (15222): sudb - Database closed

06-26 23:52:46.511 D/su (15222): 10092 com.keramidas.TitaniumBackup executing 0 /system/bin/sh using shell /system/bin/sh : sh

thank for help
[Nexus S General] wickid_d:
Awesome! Thank you sir! :)
[Nexus S General] apatal:
_thalamus thinks BLN is unstable and unnecessary. If you really need to have those mods though, but do not want to miss out on thalamus' great work, you'll be glad to know that someone is already working on a project that might include the best of both worlds. You can read about it here.

Sent from my Nexus S
[Nexus S General] :
Things are coming along nicely. First version is available now! http://xdaforums.com/showpost.php?p=27947157&postcount=13

EDIT:

Thalamus not certain about this project, felt obliged to remove links.

LINKS ARE BACK! New version with BLN + Voodoo color available
[Nexus S General] heX79:
This kernel is fantastic! Good battery life, although I'm a heavy app/game user, so I can't expect much better.

It's running Max Payne and Mass Effect Infiltrator flawlessly @ 1ghz. I figured I would definitely need the GPU, Bus and CPU overclocked to enjoy some of the new game engines, I was wrong and I'm delighted about it!

Edit: And my phone sleeps like a baby, not much battery loss at all!
[Nexus S General] apatal:
New test release uploaded!

It seems _thalamus has uploaded a new test release to his online repository. No word on what's been changed but be rest assured I'll update the OP as soon as we get information from his blog. In the meantime, if you want to give the new test release a spin, you can download it here.

Cheers!
[Nexus S General] androidforeve:
Wow this looks great how does this compare to the matrix kernel of anyone has a feed back that would be great
[Nexus S General] apatal:
Feel free to do some back reading on some recent posts here to get an idea of how the kernel performs, especially the latest releases. You can also check out the OP to get an idea of what these kernels have to offer, and how different it is from other kernels in the forum. :)

Sent from my Nexus S
[Nexus S General] androidforeve:
Thanks I will I was just curious because everyone seems to love matrix I myself use it but I'm always up for experimenting
[Nexus S General] :
Nothing has changed really. It's very much the same as the stable release, although 1 is compiled with CONFIG_ARM_UNWIND and the other is compiled with CONFIG_FRAME_POINTER.

Stack unwinding should produce a slightly faster kernel than the default frame pointers, in theory.
[Nexus S General] ironia.:
so the release is better than this latest dev?

thank for great work
[Nexus S General] deani77:
We can't set min to 100mhz when using this kernel is it?
[Nexus S General] zackandethan:
Been running on my ns4g for a little bit now . Not long enough for battery results but damm she's a snappy one . Thanks guys !
[Nexus S General] ironia.:
i know that would be possible to have battery problem under 200 mhz and it's not so convenient scaling from 100 to 1000 mhz
[Nexus S General] :
root@android:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
100000
root@android:/ #

You don't need to 'set' anything. It's 100 <> 1000 by default, which is what stock uses.
[Nexus S General] ironia.:
nstools report 200

anyway there is something that stop the battery charge at 92% into your kernel??

tnx
[Nexus S General] :
I'm telling you that it's 100 <> 1000 by default, before interference with stupid utilities. I don't care what nstools reports, it is incorrect.

Perhaps the fact you have used nstools has resulted in it being stuck at 200. Perhaps the ROM you are using changes it to 200. I don't know. All I know is that my kernel is 100 <> 1000 by default as per stock.

This was after a reboot with no nstools, SetCPU or any other crap like that installed:

root@android:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
100000
root@android:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
100000
root@android:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
1000000
root@android:/ #

Battery driver has not been modified, whatever it does it also does with stock.
[Nexus S General] ironia.:
tnx

with cpu spy i can see 100mhz
[Nexus S General] :
I know about this one... I saw it in a commit somewhere while I was working out how to merge stuff... The minimum frequency is 100MHz unless the GPU is active, in which case the system limits the minimum to 200MHz to avoid the reduced bus frequency (the bus scales down at 100MHz to save power). As soon as the GPU deactivates NSTools will report 100MHz correctly. The GPU is active for things like transition and window animations, which you can disable in developer options if you want to convince yourself that NSTools is functioning correctly.
[Nexus S General] apatal:
I knew it! OK I'm thru with nstools for now. resorting to init.d scripts instead for setting governor.

Sent from my Nexus S
[Nexus S General] mixtapes08:
Or just use set cpu :) anyway that 200mhz minimum frequency is fix by ezeekiel in early builds of his ics kernel. I dont prefer nstools to the kernels that didnt implement the 100mhz minimum fix. so for now use setcpu :)

Sent from my Nexus S®
[Nexus S General] karx23:
Yesterday I got sod. I 'm quite surprised that this happened. Unfortunately don't think I 've been able to catch the last_kmsg. Everytime I ran it in terminal emulator it gave me some kind of error. Rebooted and then got it. I don't know if it would be helpufull though. I'm on latest stable.
[Nexus S General] :
If it happened at 23:49, you did capture it. However, it was a normal reboot, not triggered by a kernel issue.
[Nexus S General] chronophase1:
Don't use nstools to set CPU frequencies. Ever. It will always default to 200.

Sent by pocket technology.
[Nexus S General] Articudos:
I hope there will be a _thalamus kernel for jellybean..;)
[Nexus S General] apatal:
I'm almost pretty sure there will be, but let's wait for him to say so. ;)

question is, will he be planning to use the stock JB kernel as base or will he continue with his new builds based on a more updated kernels from linux.org. :)

Sent from my Nexus S
[Nexus S General] :
I imagine that I will be doing a kernel for 4.1.

I expect that the source won't change much from the 4.0 kernel either, which will make it easier.
[Nexus S General] apatal:
New test release uploaded!

Almost missed this but a new test release was posted by _thalamus last June 30. You can download it here, and try it out.

As usual, we'll wait for word from _thalamus on the changes. In the meantime, I updated the OP with the links from the two new test releases.

Cheers!
[Nexus S General] :
That is just a concept kernel, it'll never be an official release because of the potential for performance regressions with some obscure apps due to the way Android isolates background tasks by using CPU cgroups.

The changes with that one is the replacement of the mainline CFS scheduler with Con Kolivas' BFS and the timer frequency has been increased to 1000HZ.

It most likely uses more battery due to the increased timer frequency. (Well, in theory it should, but it doesn't appear to, at least on my device.)

You might also encounter situations where the UI of an app may appear slow due to a CPU burning background task running at the same time. This is because there is no CPU cgroup support in BFS.

(Unlikely though, when I tested BFS kernels in Oxygen for Desire releases which had many thousands of users, only 1 user reported an issue with an obscure, non-marketplace (****ty) satnav application.)

However, even with those 2 caveats, it is more responsive in general.