yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] granets:
7.1.3 is a keeper. fast stable smooth easy on the battery. resetting location did the trick for me. Thank you so very much bedalus
[Nexus S Android Development] alen1901:
Bedalus, im on 4.2 rom and your kernel 7.1.2cm. Now on 81 hour of uptime, no reboots, nothing, kernel is fast. I think i will stay with 7.1.2 for a while. ;)

Sent from SpeedMachine i9023
[Nexus S Android Development] superng888:
May I know which version should I flash if I am on aosp 4.2? :confused:
[Nexus S Android Development] alen1901:
CM. Dev said there is nothing in ROM changed to work on cm kernel, but i tried for stock, all other and cm. Only cm worked.

Sent from SpeedMachine i9023
[Nexus S Android Development] deani77:
Both version work (CM and Any Kernel) but with Any kernel I get very long boot time (more than 2 minutes) before bott animation appeared...
[Nexus S Android Development] leap_ahead:
7.1.3CM on 4.2 rom !!!

---------- Post added at 03:23 PM ---------- Previous post was at 03:22 PM ----------

Dark One rom use the all rom kernel ...for Green Blue rom use the Cm base kernel
[Nexus S Android Development] astmacca:
I'm using CM10.0.0 with 7.1.3 on a 9023.

Works well. Fast, Smooth and Battery Life has been noticeably better than anything else i have tried.

Am getting through 14hrs of light use, a few calls back and forth, emails and an hour or two book reading no probs and still having 30% left.

Many thanks for this.
[Nexus S Android Development] rockerblood:
testing from 6.xx upto 7.1.3 all problems encountered. i must say that this version are stable and the best among the version and kernel for nexus s. hope to see u cook your own rom with this great kernel sir bedalus:) thumbs up!!!!!

Sent from my Nexus S™ i9020A
[Nexus S Android Development] Nemesis2k9:
Can someone tell me the correct kernel to use on cm10 stable nexus S i9020a? I flashed the cm tweak version and all seemed well until I started charging and it rebbooted 3 times in less than 10mins.
[Nexus S Android Development] polobunny:
That's the one. Your reboots aren't related to flashing the wrong version though. Are you overclocking?
[Nexus S Android Development] Nemesis2k9:
Yes, clocked to 1.1Ghz. I have clocked it to 1.2Ghz on the stock CM kernel and I didn't have a problem so I figured maybe I flashed the wrong kernel.
[Nexus S Android Development] polobunny:
Nope. Run stock frequency and see how it goes. 1.1GHz marmite has also FSB overclock so it's very possible your phone does not support it fully.
[Nexus S Android Development] Nemesis2k9:
Was just thinking about that. I didn't take into consideration the FSB & GPU tweaks. I was just thinking that I used to run at 1.2Ghz with no issue so 1.1Ghz shouldn't be a problem. Will run stock for a while and see if it makes a difference.
[Nexus S Android Development] benoit2600:
Hi bedalus, when you have time, can you adjust your tuto about the kernel compilation ?

I actually have problem with my own compiled kernel and USB connection. How does you fix that on yours ?

edit : actually, USB connexion don't even work with your kernel. It might be my ROM, but I don't think so, it's a CyanogenRom installed yesterday. I'll investigate that :)

PS : when I said USB connexion, it's the by default USB connexion, not MTP.
[Nexus S Android Development] polobunny:
Yep, plus the voltages might be different between marmite and stock CM kernel, so that's also something else to consider. Bedalus can probably chime in on that though to confirm/debunk that. :)
[Nexus S Android Development] ScOULaris:
CM version is what you need, obviously. :silly:

I decided to stick with 7.1.2. It's perfect. I've had zero problems with it, and the performance is great.
[Nexus S Android Development] Nemesis2k9:
Yea, I will continue to troubleshoot some more see if i can track the issue. I have one last question, with my current config I have 406MB of RAM with the cm10 tweaked kernel. Is there a way to improve this? According to bedalus it is possible to achieve 412MB. I assume this is possible with the "all other ROMs" kernel?
[Nexus S Android Development] polobunny:
It's possible to have up to 411Mb with CM10 and the CM version kernel. However, it depends on which version of Marmite you flashed. Bedalus is constantly trying to find the most stable setting and he pulled an extra memory patch from the kernel for the time being thinking it might be causing problem.

So for now, 406Mb available. Later maybe more. ;)
[Nexus S Android Development] Nexus HAL:
IMHO the best thing about Marmite over CM stock kernel is the 411MB available RAM. Really does make a big difference with 50+hrs of uptime!
[Nexus S Android Development] polobunny:
I don't see that as such a big advantage, although obviously not a disadvantage given that it doesn't create any instability. 15MB enables one to run 1 more small/medium application at a given time.

Matter of fact though is that so far, no instability whatsoever with CM kernel and I'm at over 40 hours. No softreboot or anything of the kind. If you read my previous posts, I've been plagued with softreboots for as far as I can remember minus that one CM test kernel bedalus linked me to once. Kinda hard to give up stability for the sake of running one more app. Why can't we have it all! :<
[Nexus S Android Development] Nemesis2k9:
Oh there is a difference alright, especially in some heavy 3D games. Mass Effect infiltrator is actually playable now!

Thanks for the heads up.
[Nexus S Android Development] Nexus HAL:
yeah i've read some of your issues, sorry about that. i'm glad, with PA 2.16 i'm yet to see any soft reboot on mine. regarding ram, i meant.. kernels with 393MB or 396MB RAM starts to lag here and there as the uptime increases... but with 411MB I've reached 120hrs uptime with no random lags in system animation, it still behaves like a freshly booted phone. makes me feel good.. :D

p.s. my only expectation with this kernel now is a full voodoo color implementation with gamma control, which bedalus said he'll consider once the soft reboot issue is solved. fingers crossed!
[Nexus S Android Development] :
My voltages are different to cm's. Remind me later and I'll post cm's
[Nexus S Android Development] polobunny:
I'll see how my uptime test goes. If CM kernel passes, I'll try marmite latest version for the sake of it. If it doesn't pass though, I shall fall into a deep slumber and live of CM kernel. :p

Will try to remember!
[Nexus S Android Development] superng888:
Version 7.1.3 on aosp 4.2 made the boot time faster and the room feels much more smooth 0.0 thanks bedalus!
[Nexus S Android Development] :
Ugh... Got to sleep at 1am, daughter awake at 5am. I just changed shifts too. Last night I was in work til 11.15pm but from today onwards I'll be starting at 7am and finishing at 3pm. While I adjust to this I suppose I'll be something like 'jet-lagged' so if it seems like I'm not here much during the next few days, that's why.
[Nexus S Android Development] hiphopboy:
Thanks so much :d but be careful with your health :d
[Nexus S Android Development] granets:
for the first time I feel my phone working as it should. 7.1.3 is the best.
[Nexus S Android Development] kalinusa:
I can double the comment above. After many months of frustration with the Nexus S getting slower and slower with the newer systems and after my battery getting 12-13h on 3G by just sitting and doing nothing. I AM FINALLY happy again due to this Kernel.

Phone is as snappy as never before

The battery drain line is FLAT when I am not doing anything!!!

No reboots no nothing. Although I never had this problem before.

My question is how stable is the 1096Mhz and 1.2Ghz OC? For me it has not been stable at all. On both options phone freezes after a few minutes. For example Skype video chat froze on 1096mhz after 2min, music playing and radio stream froze too on both. I have the Nexus S from T-mobile USA.

Although this is not an issue since I am happy with default conditions.

Thank you.
[Nexus S Android Development] Articudos:
3.0.53 online.:)
[Nexus S Android Development] rockerblood:
me too i didnt mess anything just use default setting and it will not let u down:) thats marmite

Sent from my Nexus S™ i9020A
[Nexus S Android Development] nexususer1:
I have exactly the same feelings :) great job bedalus, no competition for your kernel combined with cm10 stable :)
[Nexus S Android Development] deani77:
https://www.box.com/shared/tt98a32wrje7o69d9tkt

Last kmsg on AOSP 4.2 and 7.0.3CM kernel. OC to 1096mhz

Sent from my Nexus S
[Nexus S Android Development] granets:
that's the only thing that went wrong as of recent kernels - you can't OC with them. I've tried 1400mV on 1200MHz and still not stable (my phone can do 1200 with just 1300mV). But you don't really need to OC. Even 1096 isn't stable, and the gain in terms of performance isn't all that big, most won't feel it.
[Nexus S Android Development] Jamalsid:
can someone post the 7.1.3CM version here please as the link in the spreadsheet doesn't work on my phone.

Thanks
[Nexus S Android Development] dwarf77:
http://d-h.st/7x5

Hope that works for you.
[Nexus S Android Development] granets:
http://d-h.st/7x5 < there you go mate :)

woops 2 minutes too late :)
[Nexus S Android Development] Articudos:
Solved
[Nexus S Android Development] Nemesis2k9:
I can confirm that the 1096Mhz OC is not stable I get random reboots all over the place. That said running at stock clocks with this kernel has transformed my device! Smooth great battery life! I w in the process of getting a new battery thinking my battery was damaged or on its way out but now, its great!

As for the 1096Mhz OC with FSB nad GPU tweaks it really makes a difference in 3D gaming for the first time since GB my device is handling these games much better. Now if bedalus could free up some more RAM:)

bedalus:good:
[Nexus S Android Development] :
Thanks for the effort. I really appreciate when people try to help me debug the kernel, but if you're over clocking, that's probably why it rebooted.
[Nexus S Android Development] ej8989:
7.1.3 frozen while doing 2d graphics benchmark on antutu. No OC.

ROM: cm10 nightly 11-27
[Nexus S Android Development] :
Thanks, what model do you have?

-looks like the graphics driver went crazy, but there was a memory problem prior to this anyway. I'm starting to wonder if bigmem is to blame again. I think I'll take it out again and if people can just report any soft reboots I'd be grateful. I can't do it right now because I'm too sleep deprived!
[Nexus S Android Development] polobunny:
*By the power that flows through my veins*

i9023

(also shows in his signature that you might not be able to see :p)
[Nexus S Android Development] rockerblood:
yeah so far no reboots,usb connecting, multi taskin and deleting apps now all good without any reboot:) i9020 PA 2.54 marmite 7.1.3 :)

also battery consumptions are pretty good;)

Sent from my Nexus S™ i9020A
[Nexus S Android Development] xjerlzx:
7.3.1 is awesome my last used was 4.3 hahaha rock stable. And its faster thanks bedalus!
[Nexus S Android Development] superng888:
7.3.1 ?? o.0
[Nexus S Android Development] granets:
I'll probably be moving on to Samsung galaxy s3 soon, I'll miss my old phone, and the marmite kernel. I feel happy and sad at the same time. I'll miss this.

By the way, anyone got something good/bad to say about the S3?
[Nexus S Android Development] capoooro:
It's an amazing smartphone....but is not a nexus.:)
[Nexus S Android Development] superng888:
I actually like touchewize ui :D its very responsive and combined with s3 hardware lol hands down... But why aren't you going for a nexus 4?
[Nexus S Android Development] towelboy:
Phone colors tend to be on the warm side, touch wiz looks like it was made for little kids, so root + another rom asap!
[Nexus S Android Development] Nemesis2k9:
As much as I love the Nexus devices I don't think i will be getting another one. I just cant stand the lack of a sd card slot anymore:(
[Nexus S Android Development] leap_ahead:
+ for 7.1.3 ...is the best
[Nexus S Android Development] Basche:
He's from the future, where marmite is even better than it is now. Where we can use 4.2 ROM as a daily ROM

You have just been beamed
[Nexus S Android Development] granets:
because in my retarded country you can't find nexus 4. believe me I've tried. And I'm not buying a galaxy nexus. but yeah, I'll root it right away and smack dat custom ROM on it :)
[Nexus S Android Development] polobunny:
A little update on my test!

84 hours in, no problem so far.

I had an issue where when I put my phone to sleep sometimes it looked like it would wake up quickly then turn the screen off. Thought it might have been marmite, it's not. Happens with the default CM kernel too.

Android OS gets somewhat high if autorotation is on, with or without marmite. Something to look forward for some people having this issue.

Otherwise it's pretty good. Performance is on par. I don't know where the heck people saying it's night and day come from. Benchmarks show similar at stock clocks and it pretty much feels the same...
[Nexus S Android Development] xjerlzx:
Hahaha I meant 7.1.3 =P
[Nexus S Android Development] alen1901:
Im on 134 hours of uptime. 7.1.2cm. No problems at all. 4.2 ROM. :cool:

Sent from SpeedMachine i9023
[Nexus S Android Development] granets:
78hours for me on 7.1.3, just one problem since last night - huge OS drain, and I can't seem to fix it. I've tried everything I know, besides reboot :)
[Nexus S Android Development] csdibiase@gmail.com:
7.1.3 seems to have fixed my random reboots. Usually a log road trip with Podkicker and Navigation going will result in at least 2 or more reboots. 10+ hours of driving and nothing.

That said, something is wonky with battery drain and cell signal on my device. I've had my phone fall off the network a couple times in the last day or so and the battery is bleeding off much faster with 7.1.3 than it was before. Not sure if that's kernel related or related to some other app that's updated recently.

I'd rather have bad battery life than an unstable phone. Still interesting, not sure how to troubleshoot it.
[Nexus S Android Development] :
You're making me curious about flashing cm
[Nexus S Android Development] :
Did you turn your location settings on and off again?
[Nexus S Android Development] polobunny:
I was unsure before but I'm definitely not displeased. I don't see why there seems to be complains about the default kernel when it is just fine. It might have been different in the past, I know I started using different kernels before I used marmite because it lacked some functions I wanted, but as far as stability and speed though I see no reason to be switching from default on to another.

I'll wait for your magnum opus kernel and flash that to compare. :p
[Nexus S Android Development] :
Haha, I think my next great quest will be to start again from the top.
[Nexus S Android Development] granets:
yes, multiple times. it didn't go away. It got so bad, that I ran out of battery, so the phone turned off... Something was draining the battery really bad. I could probably provide a last_kmsg if it helps
[Nexus S Android Development] Basche:
Currently using CM version 7.1.3 and is great with 1ghz and smartassv2. Performance is better, but i don't really know how people get like 83 or 135 hours on their phone, is it from the voltage settings in NStools?
[Nexus S Android Development] polobunny:
These are uptimes, not time on the battery without charging. Just without reboot.

If I don't do much, I can usually eek out around 2 days of battery. But otherwise around 3 and a half to 4 hours of screen on time and my battery is depleted.
[Nexus S Android Development] Basche:
oh, i hadn't received any reboots when using 7.0 CM version, and I got that about 1 day after it was released. I only started using 7.1.3 since yesterday, so far no reboots. I barely used my phone recently as i'm finishing school next week, and have been very busy.
[Nexus S Android Development] Nemesis2k9:
Man if those numbers represented up times, life would be complete.
[Nexus S Android Development] :
v7.1.4 is here: http://goo.gl/HvUrp (for Android 4.1.2 and 4.2)

-Updates from linux mainline v3.0.53

-Updates from android-3.0/common for wifi

-Updates from the samsung tree for PVR driver and i2c bus

-These are all designed to be stability fixes, so nothing particularly exciting, but I hope to see less PVR crashes

I have been busy learning some new workstreams in my job, and changed shift blah blah blah... as it happens, I'm actually awake in the middle of the night again anyway due to my daughter having an upset tummy. When she went back to sleep I was like, what-the-hey, let's build some kernels. I found a bunch of stuff had been updated, so nothing particularly interesting here, but as usual, it's possible that things designed to improve stability can blow up in your face for no obvious or predictable reason, so keep your eyes open.

On a surprising note, there have been 700+ downloads of v7.1.3 which shocked me when I noticed it. Wow! Considering how long it's been available, and how many people appear to be using it, I'm very happy to note that there have been really very few issues reported in the thread.

So, just a reminder: if you do have an issue, please report! Especially if your issue is a reboot. Please specify if possible whether it was just a soft reboot, and if so, if you yourself can manually perform a normal reboot and send me the last_kmsg, I'd appreciate it. If you get a hard reboot (i.e. you see the google logo) you can send the last_kmsg right away, as it is already the right version. If reporting with a last_kmsg, please specify i9020/i9023, your ROM, and the kernel version, and pledge that you were not over-clocking.

If you are having reboots when using 1.1GHz, it could be that your phone doesn't like FSB OC, and if you use 1.2GHz, this might just be too much for your CPU to handle. As always, have a little play with your voltages first, this might be all that is required to improve stability. Voltages can be set for 1GHz, 1.1GHz, and 1.2GHz for ARM, and 1.1GHz and 1.2GHz for INT. This is all stuff you should already know if you've been following the thread. But it's probably about time I put the info somewhere in the OP! :p
[Nexus S Android Development] towelboy:
Picture is self explanatory :D

v7.1.3
[Nexus S Android Development] atxbang56:
need 411mb Ram...

Sent from my pretty cool Nexus S

Phone : Google Nexus S i9023

ROM : MIUI 2.11.23 by MIUI France

Kernel : Marmite v7.1.3 by Bedalus @1096MHz
[Nexus S Android Development] deani77:
http://db.tt/pOeXOUmn

Was on AOSP 4.2 and Marmite 7.1.4CM. I9023, no OC

Sent from my Nexus S
[Nexus S Android Development] :
Again it looks like a memory issue caused by the binder failing to kill some processes. Looks like I need to come up with something to deal with this.

EDIT: Searching through previous reports, it looks like only i9023 users are having reboots that are unrelated to OC.
[Nexus S Android Development] alen1901:
Well, im on 7.1.2cm, rom 4.2 from greenblue, and my uptime is 160hours. No issues. And i have i9023. So... I dont think thats i9023 fault. Maybe its some user settings, which users are not aware of.

Sent from SpeedMachine i9023
[Nexus S Android Development] hiphopboy:
160 hours :-s really ?
[Nexus S Android Development] caliban2:
I had these binder-failings during summer, if you remember. I have a 9023 too, back then I was pretty much the only one with these. But now marmite is stable for months, even the 411mb-versions.

=> meaning: I'm quite certain it's setup-related. Restoring the wrong stuff after a wipe etc

I'm on 158h, no big deal about it. :)

(Started a new job on Monday, installed 8 new apps, had some updates from the store, added an exchange-account and still no problems)
[Nexus S Android Development] alen1901:
Thats little. One time i had 335. So im up to beat that record. So no flashing for me for few weeks. :P

Sent from SpeedMachine i9023
[Nexus S Android Development] kalinusa:
I have to say I had two reboots at the end of phone calls. I hit the disconnect button and then the phone stops....and immediately reboots with google logo.!!! I am on 7.1.3, and I did not notice this on 7.1.0.

I am gonna try to see if it is a kernel issue because I did recently change to a KI radio file instead of the KD. But how will a radio cause a complete phone reboot. Usually just signal issues.

So yes 2 reboots when hitting END phone call. I will try with 7.1.4
[Nexus S Android Development] gabling23:
Which is the default kernel of the slim rom 3.1?

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] Basche:
the default kernel would be whatever comes with the ROM, but i believe the marmite CM version should be the correct version to use with that ROM.
[Nexus S Android Development] ej8989:
Slim ROM has marmite as its default kernel. I believe what he wanted to know was the exact version of marmite in that ROM.

I might be wrong.
[Nexus S Android Development] gabling23:
Exactly!

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] :
Uh, it's version 7 with some extra ram IIRC.

The next version of slim bean will be 4.2 based and will likely have v7.2
[Nexus S Android Development] :
Can you patch your kernel with powerhal?
[Nexus S Android Development] :
Here's an experimental version with gamma control. It doesn't have custom IO control so it won't work on slim bean, cyanogenmod, strawberry or mdo. If you set gamma below 0 I think you might see a flash when you power the screen on and off
[Nexus S Android Development] superng888:
Sorry for the noob question but what is gamma?
[Nexus S Android Development] :
What's the benefit?
[Nexus S Android Development] :
Noob questions are always welcome :)

It applies a function to rgb values to change their intensity... by how much depends on the original value
[Nexus S Android Development] Cuyi02:
Wow, 7.1.4 already... You just keep them coming... I think I'm falling in love lol.
[Nexus S Android Development] VerminX:
I'm running it on rasjelly and wow I forgot how much I miss this feature since Ics. It makes my amoled that much more beautiful.

Any chance for a 411mb version ?

Thx
[Nexus S Android Development] :
I may get around to doing one prior to 7.2
[Nexus S Android Development] caliban2:
Hey bedalus, any chance we'll see extra mem again? :)
[Nexus S Android Development] :
That's what I meant. I'll do one before 7.2, but 7.2 itself won't have it.
[Nexus S Android Development] caliban2:
Sorry, didn't read carefully... :D
[Nexus S Android Development] elnahir:
Thank you for saying this. :) Can I also ask what am I doing wrong, since I'm on CM 10 Nightlies (12/02), I've just flashed 7.1.4 and I can't enable Deep Idle. This is my first time digging into your kernel (quite stable on i9023, I should say!) and I've seen other people in the thread posting screenshots with the Idle option on.

Could someone tell me what do I need to do to enable it on CM 10 Nightlies? I've flashed the CM-tweak version of 7.1.4, btw.
[Nexus S Android Development] :
Deep idle isn't available. It would be nice if it worked reliably, but unfortunately all attempts to fix it have failed. It's unlikely it will ever work. But I haven't ruled it out completely. I'd like to see if I can come up with some sort of hybrid between deep idle and IDLE2, but this is going to be extremely difficult as I lack a lot of knowledge about the particular code required.
[Nexus S Android Development] elnahir:
Thank you for the quick response, bedalus! I've had good experiences with deep idle in the past but I can see the limitations of developing for an old device such as ours. So thanks for taking the time anyhow, and for doing so much already!