yashsingh1/xdaforums huggingface dataset:
[Nexus S General] srthimsen:
I think it's the second one in your list - I flashed several leading up to that one, as builds came out in a hurry :)

I'm currently running test-4 - but please heed _thalamus' warning above before trying.
[Nexus S General] rasengan82:
First reboot on test 25 ICS. Screen went super bright and froze for like 20 sec. Then hard rebooted. Last kmsg shows PVR references everywhere.
[Nexus S General] :
Thanks for that, it looks as if it was a GPU crash, so nothing to do with my code I'm pleased to say. That bug has been around for a while and is pretty random.

There is *never* too many details.

Same again, it's that occasional PVR bug again. It's not really something I can fix as I wouldn't know where to start looking.
[Nexus S General] jorim.tielemans:
Isn't there a specific i9023-kernel anymore?
[Nexus S General] :
I've no idea which one test 7 is. Will people *please* stop referring to them by test X and provide the filename instead.

The number is meaningless, it's the output of git describe so the number is simply the number of commits since the last tag, and that will vary depending what branch I built it from or when I last tagged.

---------- Post added at 07:52 AM ---------- Previous post was at 07:50 AM ----------

No idea what that is because you have only provided a small part of the last_kmsg so I can't see what lead up to it.

Please provide full logs, snipped logs are invariably useless.

---------- Post added at 07:54 AM ---------- Previous post was at 07:52 AM ----------

Yeah, but I deleted it accidentally yesterday, I'll post a new one when I do a new test release.

All it fixes is the silly CRT animation anyway.
[Nexus S General] madd0g:
I've had some AlarmManager Phone wakelock drains on JellyBelly, so I went back to stock ROM, because I suspected it's the ROM. I flashed the stock JB image and kernel-S5PC110-3.0.38-25_JellyBelly-JB-20120728-201319.zip, with the liblights for BLN. At first it seemed OK, but even then the wakelocks started to pile up :

So I flashed SimpleKernel, which is from stock sources, only with added BLN and Voodoo. No sign of even one wakelock now:

Any ideas why this could be happening while on your kernel ?
[Nexus S General] :
Partial wakelocks are controlled from userspace, the PowerManagerService specifically, I don't see how it could be related to the kernel at all.
[Nexus S General] madd0g:
I see. I have no idea either, so I'll wait if the problem shows up again :] At least it did show up before and now it doesn't.
[Nexus S General] irishrally:
Somebody didn't read the whole post ...
[Nexus S General] madd0g:
Yeah, it started on the stock ROM/kernel also after some time. Suddenly there's 10 minutes of wakelocks for the Phone. Really have no idea anymore. Unless it's BLN lol.
[Nexus S General] ehiggins:
Bln would give me a wake lock from when it started flashing until I looked at the notification, I disabled it and never had the issue. This was back on ICS fwiw
[Nexus S General] yxcv99:
Got a reboot while using tapatalk @ kernel-i9023-S5PC110-3.0.38-24JB_test-1-g00c1bbe-JB-20120727-125025, dont know if its solved right now. Got no time to check

last_kmsg

https://docs.google.com/file/d/0Bx6ZDyyjyE9dOGVqZkVCbE1GTms/edit
[Nexus S General] chronophase1:
The only time it would probably do this is with blinking. Speaking from experience. Mine is doing the same thing, so it seems to not be a kernel issues as stated.
[Nexus S General] qu3becker:
Here's my night using the last experimental kernel.

Wifi on all night.

I'll flash the stock kernel tonight and do the same thing again.
[Nexus S General] :
Yeah, sorry, I completely forgot to fix that. It's just due to an assert in the updater-script which I have now changed to include crespo4g.

This should flash on crespo4g.

---------- Post added at 09:09 AM ---------- Previous post was at 09:01 AM ----------

Oh, and whilst I am here, thanks for all the positive comments that I have read here.

The ethos behind my kernel is to make it as lean and as fast as possible by choosing less expensive configuration options, by disabling unused features, and by optimising it as much as possible.

I did a similar thing on my desktop. With kernel modifications alone, I got the boot time down from about 12 seconds to about 2-3 seconds. I don't even see the splash screen now. :)
[Nexus S General] tycruickshank:
Just out of curiosity what os do you run on your desktop?
[Nexus S General] mixtapes08:
Definitely the wifi modules patch here the guide how to fix it http://xdaforums.com/showthread.php?t=1609721

Sent from my Nexus S®
[Nexus S General] apatal:
And thanks for dropping by, good sir. Glad to know you actually take time to visit the thread. :)

And we, and our phones, thank you for it. Your kernels are really one of the best.

Sent from my Nexus S
[Nexus S General] :
kubuntu 12.04 with 3.5.0-rc2-thalamus. Nothing like living on the bleeding edge when it comes to kernels. :)
[Nexus S General] apatal:
OP updated with link to the new version with the fix for Crespo4G devices. Cheers!

Sent from my Nexus S
[Nexus S General] jjhrrsn:
Sweet, been on teuv, going to try this with slim4.0 and rascream
[Nexus S General] irminsul:
Impressive. On latest rascream. Listened to music for almost 2 hours. My I9023 never holded it this long ;-)

Verstuurd van mijn Nexus S met Tapatalk
[Nexus S General] reference.phone:
http://cyann.mobi/article/show/cyann-kernel
[Nexus S General] apatal:
From the same people who made NStools, right? Too bad it's still on 3.0.29..
[Nexus S General] Icecoldmeat:
Definitely yes.
[Nexus S General] apatal:
New blog entry from _thalamus:

Please see the updated OP for the changelog and link to his blog entry with the download link.

Cheers! :)

Sent from my Nexus S
[Nexus S General] chronophase1:
How can it get any more stable? Lol.

Sent by pocket technology
[Nexus S General] apatal:
Have you tried it? How is it performing against the previous release? He implemented some pretty major changes this time. :-)

Sent from my Nexus S
[Nexus S General] chronophase1:
I'm on my way back home now(18 hour road trip ftl), so I'll have to flash it once I get home.

Sent by pocket technology
[Nexus S General] :
this kernel is just fantastic
[Nexus S General] apatal:
How is it performing? Any noticeable improvement from previous releases? Haven't had a chance to test it yet. :)
[Nexus S General] DaXmax:
So far, its much smoother than previous version.... ;)
[Nexus S General] wmdunn:
Kernel runs great, very smooth. Only thing missing is voodoo color adjustment.
[Nexus S General] :
That's nice to know. And yeah, as someone else said, I have made some pretty major changes, so I'd be surprised if there wasn't any fallout.

I've made the following changes for the next version so far which I am using on my current test build which is available for those who can find it:

The kernel package will become CM compatible by adding a symlink to the bcm4329 module so it will load and the wifi will work if the ROM is expecting it to be in /system/modules (stock) or /system/lib/modules (CM).

I've decided to bring non-essential features out of the main kernel image and build them as modules instead.

So far I have done cifs and utf8. I figured there was no point having rarely used code built into the zImage.

So, if anyone really wants any additional drivers / filesystems etc, and has a good reason for it, I don't mind building them as modules as long as the package doesn't end up getting stupidly large. I could make the package 2.5Mb smaller by ditching cifs, but I'll get moaned at. :p

I'm also playing with the interactive CPU governor again in my test build.

---------- Post added at 05:21 PM ---------- Previous post was at 04:51 PM ----------

Like this you mean?

Thats my personal current test build, YMMV.
[Nexus S General] madd0g:
Never used blinking option.
[Nexus S General] chronophase1:
Yeah. I've pretty much just given up on it for now.
[Nexus S General] madd0g:
Do you run on 3G or 2G only ?
[Nexus S General] :
Bad news...

I'm afraid I have some rather bad news, I managed to brick my Nexus S this morning, it's completely dead, no response, nothing detected via USB and it does nothing at all.

I was working on a method to test power drain on the device, using some wire and tape to enable me to put an ammeter into the circuit. However, due to my ammeter being too high resistance, the device wouldn't start. I then got the device booting by bypassing the ammeter, but after it booted, one of my wires slipped off causing the power to be cut.

This shouldn't have caused any harm as it's just like a battery pull really, however, when I tried to power the device back on, nothing. I removed my wire and tried again, still nothing. I left it for a while with the battery out to see if that would solve it, I put it on charge, I tried the resurrection tool by AdamOutler, I measured the battery voltage to ensure that it had charge, which it had 3.76 volts which is enough to power on.

So basically, it's f**ked. I'm undecided whether to warranty it or claim from the insurance and get the cash instead and buy a GNX.

I'm not the only one who has done this recently seemingly too.

Bah.

And you can go away with the discussion about the wakelocks. Take it to Q&A please, it's clearly not an issue with my kernel, so it's offtopic.

Thanks.
[Nexus S General] Imppy:
Oh man that really sucks...I say try to claim it

Could you just buy a new battery?
[Nexus S General] colonia27:
Now that's really sad to hear :'(

People, why don't we start collecting some donations. Shouldn't be to much we need for a new one..... or a used one

Gesendet von meinem Nexus S
[Nexus S General] :
I'm not convinced that it is the battery. I'm gonna see if I can get hold of a battery for it tomorrow anyway.
[Nexus S General] madd0g:
That sucks man, sorry to hear that. I also apologize to draw the phone lock discussion in here.
[Nexus S General] :
Nah, no donations necessary. It's not like I can't afford another one. The money isn't an issue. Anyway, I'll try a new battery first and work on the Nexus 7 for a few days. I'll still release the update that I said I would, because I'm reasonably happy with it, and I know the code well enough to fix any bugs which may crop up.

If it is completely knackered though, I don't see the point of buying another one when I could get a GNX for a little bit more.
[Nexus S General] knzo:
Despite my recent divergences with thalamus I second this and I'll happily contribute to such funding.
[Nexus S General] colonia27:
Nice to hear but as he said he does not want/need it, I think we shouldn't discuss this any further

Keeps the thread cleaner anyway :D
[Nexus S General] :
Thats very reasonable, and thanks, but no, there isn't any funding necessary. It was my mistake.

It does make me wonder why it happened though, perhaps suddenly disconnecting the battery fries the chip inside, that would certainly be the cheapest solution, and I like cheap.

I've ordered a new battery and it should be here on Friday, so I will obviously post and let people know the outcome.
[Nexus S General] yxcv99:
Gnah. Thats really bad news _ thalamus. The GNex owners are already waiting for such an assiduous developer while reading this. However my hope is with the new battery.
[Nexus S General] :
So, I got my multimeter out again and did a few tests. It seems that the output voltage from the battery is very unstable, it goes from 3.1V to 4.2V then to 0.0V then back to 3.1V, and it shows 4.5V when a charger is connected, which means it isn't accepting charge, and then when I disconnected the charger it went to 0.0V, and then when I removed it from the phone it showed 4.2V.

So yeah, the battery is completely knackered.

Warning to you all, be careful when you are doing battery pulls. Don't do them unless you need to. Mine was an accident, brought on by having a crap testing method, but that guy who posted in the JB thread the other day had exactly the same outcome after a pull, so be careful!

As for a GNX, it is on my list...so it will probably happen soon, regardless of what the outcome is with the NXS.

---------- Post added at 08:58 PM ---------- Previous post was at 08:39 PM ----------

Another test kernel for -26

http://thalamus.ineige.org/misc/zImage3.0.38-26RC

I figure releasing a zImage which is only fastboot flashable will keep the n00bs away, unlike my warning last night lol as I saw some clown on the JellyBelly thread had flashed it to try and resolve his usb debugging issue?!?!?!?!

Flash with:

fastboot flash zimage zImage3.0.38-26RC

If you don't know how and want to use it, then you'll have to Google and learn how to use fastboot. No questions about it on here please. :p

If you don't know how or don't want to use fastboot, you can't flash it, sorry.

I'm seriously considering releasing test versions via zImage only in the future, only releasing stables as a zip.

It's easier for me and discourages the n00bs.

Anyway, I'm probably going to release that tomorrow, possibly even as stable. I'm fed up of test versions.
[Nexus S General] _moriarty:
Don't know what this will add; however, 2 days ago I pulled the battery out of my Nexus S after it started going through a reboot cycle. It would not power on and no fastboot, no recovery, AdamOutler tool for linux did nothing. Linux nor Windows was detecting anything. After calling Samsung I took it to their service center which is VERY close to my house and told them that after receiving an update for my phone it turned off and stopped working. The tech guy told me that I had fried my memory and everything was gone. He simply replaced pretty much the entire inside of the phone and the cost was free as it was under warranty. Thought maybe _thalamus could do the same if he wants it fixed. Or you probably just want to move up and get a GNex. IF I were you I would get a Galaxy Nexus and leave us behind... but since I am a Nexus user I would rather you get it fixed, quite possibly for free too, and stay with us.

"I keep trying to get out... but they keep pulling me back in!" -Michael Corleone, The Godfather

-M
[Nexus S General] :
We'll see. I think it is the battery that is cooked tbh. New one will be here on Friday.

I'd like to continue my work with IDLE2, so I would like to think that I haven't knackered it completely.

It appears that adamoutlers tool only works if you do the hardware modification first. I might do that anyway, because that kind of low level access is useful to have.
[Nexus S General] Randomwalker:
OK, compared this kernel to kernel-S5PC110-3.0.38-25JB_test-JB-20120728-201105 in regards to BT music streaming.

After two hours of uninterrupted playback charge remaining was 76% vs. 78%, which can probably be regarded as a dead heat.

EDIT:

The test protocol:

- flash kernel

- charge till full

- leave connected for an additional 30min

- play music for 2h (random sample of similar low complexity an short duration songs)

- look up battery

WiFi and mobile network were enabled for the duration of the test, position did not change much.
[Nexus S General] srthimsen:
Not sure what happened there, here's the full log (having issues with xda allowing upload, probably company firewall).

https://dl.dropbox.com/u/11119108/last_kmsg.txt
[Nexus S General] :
It looks like something went horribly wrong, possibly a scheduler bug, I dunno.

Not sure what the original cause was though, because the log is full of BUG() spam.

---------- Post added at 10:13 PM ---------- Previous post was at 10:05 PM ----------

Yeah, that sounds about right. I don't think TOP ON playback (when either bluetooth / GPS is active) saves that much.
[Nexus S General] deltatux:
My mistake, I didn't know that those were automated filenames. The kernel revision I was referring to was:

kernel-S5PC110-3.0.38-25JB_test-7-g3748d15-JB-20120729-164802.zip

deltatux
[Nexus S General] :
I can't remember which one that one was, I can't remember what it fixed and I can't remember what the 7 commits were for.

Unless I specifically posted it and asked people to flash it, then you probably shouldn't have done, often I upload things for 1 person to try for a specific issue, which may break other things.

The problem is when people flash builds I'm testing I get bug reports for things I know about or that have been fixed in the releases *intended* for public consumption.

I'll release -26 tomorrow anyway. It seems alright, no bad reports yet. I might even tag it as stable.
[Nexus S General] srthimsen:
Thanks for looking - I haven't been able to get it to happen again, and I've been streaming music via pandora every night for the last 2 weeks for 2+ hours while I work on a class.
[Nexus S General] gregorypeg1000:
Great kernel thalamus.Awesome battery life.I get almost 4 hours screen on time in 23 hours of battery.Only one thing to ask.Is there any chance to make the kernel overclockable to 1.2 ghz?It's mainly phycological :P (If it can be overclocked it should even if it doesnt need it) :P

Many thanks for your work.Keep up
[Nexus S General] deltatux:
Alright, thanks for the heads up, I rolled back and flashed the standard -25 kernel. It seems to stabilize the power draw. Looking forward to the -26 release.

Cheers,

deltatux
[Nexus S General] Abaddon:
anyone can share -25?
[Nexus S General] chronophase1:
You mean the one mentioned in the OP?
[Nexus S General] apatal:
Or the experimental one found on this post?

Sent from my Nexus S
[Nexus S General] Lordofminor:
_thalamus can you add BLD?
[Nexus S General] jjhrrsn:
Oh my
[Nexus S General] irminsul:
I heard rumors it will be implemented in a kernel released on the day when Christmas and easter are on the same day.
[Nexus S General] spider623:
I heard the day easter bunny will sing along with Dio(Black Sabbath v2) and Vladimir(LoL)

Sent from my Nexus S
[Nexus S General] :
How does no sound?
[Nexus S General] Lordofminor:
Thanks for reply, I thought it can't be hard since most kernels have it. Switching to something else. Thanks...
[Nexus S General] 420p:
What's so hard about respecting Devs decisions about not using dirty hacks? It's not hard to implement, he just doesn't want to add it.
[Nexus S General] Lordofminor:
What are you talking about?
[Nexus S General] 420p:
Same you are talking about, viewed from a less whiny angle. If you want feature galore and no slick running kernel, then use CM and some patch slapper stuff kernel.
[Nexus S General] Lordofminor:
What in the **** is wrong with you? I only ****ing asked him if he could add it. I did not whine or anything. He said no, ok, I thanked for reply. So go shut your mouth please and go ***** on something else
[Nexus S General] 420p:
You are simply lacking common sense, like 90% of the users here. If i was searching for a specific feature i would find a corresponding kernel instead of asking Devs for features to implement, if I don't know the person personally and his schedule. You could also ask the guys at google, if they could implement it. Why don't you do this, they also reply. Mostly less kind than anybody here. ;)
[Nexus S General] :
Good. Bye then. Don't come back, I don't need users that sulk when I say no to something.

Hey, douchebag, don't start abusing my users.

I suggest you wash your mouth out with soap and water. Maybe he thinks you are a twat for not searching / reading the thread first. If that is the case, then he's right.

Are you still here? No? Good.
[Nexus S General] polobunny:
I lol'ed. Good times be had when people cannot read even the first post.
[Nexus S General] schiznik:
Hahahahahahahahahahaha Lars/Will... you two make xda so entertaining....

Now where's jelly belly and a kernel for my sgs2?!?!!? ;)

Sent from my GT-I9100
[Nexus S General] 420p:
READING?!?!?! :silly:
[Nexus S General] albundy2010:
I love the usage of the word could. Its not that hard...

Like being able to add it was a issue
[Nexus S General] caliban2:
You really expect people to read?! Oo

Illiterates and Minimods - those two always were and always will be the majority on xda. :) (you didn't believe it's about devs, right?!)

More on topic:

Sad to hear about your phone, thalamus. Nobody wishes a phone to die. Let's hope it's really just the battery. Does it still make sense to flash the latest test-version or is there gonna be a new one in the very near future? (Yes, even I know how to use fastboot. :p ) I'm not having any bugs per se, just the rather high batt-drain in standby (jellybelly).
[Nexus S General] :
Test build - test because it's untested (lol) as I don't have a device to test with. I was gonna release 3.0.38-26 today, but as 3.0.39 was released I figured I better update, so here it is.

3.0.39 has got quite a few memory management backports, so should be more performant.

Changelog:

Merged to 3.0.39 from mainline

zImage here, flash with fastboot.
[Nexus S General] deltatux:
After reading the lwn.net post on 3.0.39 I decided to take the leap of faith and flashed it.

Seems quite stable, apps seem to be very responsive (I think they're loading slightly faster, not sure if it actually true or just a placebo effect).

Any specific test needed that doesn't involve special tools?

deltatux
[Nexus S General] :
Nah, just general usage is fine. I don't think there will be any issues, I suspect those mm patches will have been given quite a bit of testing.
[Nexus S General] fear_factory84:
just flash jellybelly 0.1.5.1 instead of 1.0.0, battery drain will go away.

Now I'm running it with a self compiled kernel from thalamus sources (up2date since yesterday) + usb fast charge patch, and it works fine.

With the same kernel and jelly belly 1.0.0 it drained a lot. There is something between the two releases that broke something.

Unfortunately, Adam decided to shut down development of that rom, and that's very sad, since he also removed sources from git, so nobody could continue his work. :crying:

Adam if you read this, please release again sources, and don't care about those dumbasses that offended you, world is full of them.

Just go ahead with your good work.

Thalamus, could you release your complete kernel .config (crespo_release_defconfig and crespo_test_defconfig are not complete)? I had to use bedalus one (he forked your sources). Perhaps I should have configured those missing options manually, but they were many...
[Nexus S General] :
1) Can we stay on topic, this is not a JellyBelly thread.

2) Do you actually know what a defconfig is? It only contains the options that are *changed*. Most devs use a copied .config file and call it a defconfig. That isn't correct, and it's not a defconfig. To use a defconfig, you do

make ARCH=arm crespo_test_defconfig

and the .config file is generated for you. Simple.
[Nexus S General] jfmac:
As far as I can tell it's not placebo, now apps are loaded slightly quicker. (First thing I did after flashing zimage was I opened Facebook, which needs ages to open, now it took about half a second less)
[Nexus S General] fear_factory84:
Thanks thalamus, I learned a new thing today.

I liked to have fast charge on my device, I liked your kernel, so I downloaded sources, applied fast charge patch, compiled it and flashed it. And it works actually.
[Nexus S General] Imppy:
Hey would you be able make the new one .zip flash able?
[Nexus S General] fear_factory84:
just replace zImage and .ko files on the older .zip ;)
[Nexus S General] ppamungk:
Tried the 3.0.39 test kernel.. everything seem to be faster... but lost crt animation.. and phone a litlle bit hotter than usual..
[Nexus S General] Imppy:
It would be nice if you could make a .zip for me!
[Nexus S General] colonia27:
thalamus does not provide flashable .zips for his test releases anymore --> http://xdaforums.com/showpost.php?p=29599035&postcount=794
[Nexus S General] caliban2:
thalamus,

running zImage3.0.39-26-test and so far it seems fine, but which idle2-state is which? idle -> top-on -> top-off? (state0 -> 2)

that's how i'd interpret the stats on my system. but when i read up on it (xda & blog), it seems state1 is top-off. :confused:
[Nexus S General] colonia27:
state0 --> IDLE

state1 --> IDLE2-TOPON

state2 --> IDLE2-TOPOFF

you can check states using adb:

adb shell cat /sys/devices/system/cpu/cpu0/cpuidle/state*/{name,time,usage}