yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] :
Unfortunately it's very difficult to say. Only a few last_kmsges have contained actual kernel panics, and now that i think about it, a lot of them were probably submitted from people who were over clocking. The majority of them seem never to contain any info from the kernel, which i suppose is a good indicator that there is a faulty app or part of the ROM.

I think a good way to eliminate problems is to take a preventative approach. Start again with a full wipe including the SDCard contents (backup first) and install a stable ROM version. Reinstall your apps from the market, try to keep it to just the ones you need. Then set up your phone how you like it, and do a nandroid. Then you know you've always got a good jumping off point to get back to if you start having problems.

I personally have had something like 2 reboots on my kernel, one of which was due to an programming mistake, the other was unknown.

While I'm on the subject of stability, the interesting thing that makes marmite so smooth is this: https://github.com/bedalus/marmite/...bc5895de5b95c/arch/arm/mach-s5pv210/cpufreq.c

...see line 154, there are a collection of values that tell the system how to switch to 200mhz.

In every kernel available for the nexus s, this line starts 3, 3, 1... Except for in Mathkid95's. If I set this to 3, 3, 0 (i.e. stock) the smoothness is gone. This value relates to the HCLK_MSYS variable, and is only ever 0 at 100mhz.

I don't know what this variable does exactly, but i know it relates to frequency scaling. Nor do i know where mk got this tweak from, because it's not in his git history.

Anyway, messing with the clocks is tricky, various timers need to be reset and set again in the right order for the frequency scaling to work without errors.

The reason I like mk's tweak is for the smoothness. The reason I don't like it is because it appeared from nowhere without explanation, it isn't stock, no checks exist to see if whatever it does with the clocks are actually possible at the time of request, and I can't shake the feeling that you can't get something for nothing.

Instead skipping over the 200mhz step allows stock clock behaviour, and preserves the smoothness.

I'm running this version right now and loving it. I won't be sorry to see the back of that dubious hack.
[Nexus S Android Development] :
Are you on the cm kernel? Try http://xdaforums.com/showthread.php?p=33742443 it needs more testing!
[Nexus S Android Development] alen1901:
Nope, im on all other version. Using rasbeanjelly.
[Nexus S Android Development] :
Okay, fresh out of the oven: http://d-h.st/V5I (non CM version)

-fixed OC volts

-no 200MHz step
[Nexus S Android Development] BenHeng:
Thanks =)

I was starting to be anxious of a new non CM version !

I flashed it, it seems good. I hope it will improve slightly batterie life, that would be nice :)
[Nexus S Android Development] caliban2:
Are you testing this for battery as well?!

I'm back to that cm-test, no oc. Of course it's fast and smooth (as before), but it better be!!! Everything that's been done @200 previously is now done @400. I get nothing at all @100 when doing something with the phone, only during standby (and even that number looks smaller now in cpuspy - still gathering data though). While this may be desirable for gaming, I can't believe it doesn't cause unneeded batt-drain for "normal" use.

I'm using different smartassv2-settings than you, mine aim at 400/100/400, yours are still 800/800/800 I guess? So changing to yours should make it even worse (shifting load more towards 800).

Now let's see if my theoretical doubts are confirmed in praxis over the next hours. :rolleyes:
[Nexus S Android Development] beppegg:
I'm experiencing the same bug... But I'm suspecting the ROM being the culprit. Today I noticed I doing even have the "cp" command in!

Can you check if you have it, please?

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] deetailed:
Had a reboot again, this time on 6.7 Stock, kwbr's ROM+mods in his thread, no OC, while scrolling at the Playstore. Tried getting last_kmsg but it's empty. I'll flash the debug kernel and see if it happens again. Truth be told, I've been having reboots with all marmite versions I've tried (6.1, 6.2, 6.6 and 6.7), but kept trying this kernel because I like the smoothness and battery.
[Nexus S Android Development] BenHeng:
Not exactlly. I'm using my phone heavily at work (min3hours on screen time, 1/2 hours call, data on, bad signal), and every minute is precious to reach the end of the day.

I'm trying to monitor the impact of each kernel on battery life but since my use of the phone is not constant it's kinda hard to be sure.
[Nexus S Android Development] caliban2:
Jep, it

must

be the kernel then...

(Yes, sarcasm.)

I was asking bedalus, but since you're actually using your phone and not just keeping it in your pocket, please keep an eye on it. Because screen-time is exactly the area where it could/should matter. Okay, it shouldn't be that bad (cpu isn't the biggest batt-user), but still...
[Nexus S Android Development] polobunny:
So far so good. There was an instance yesterday were a few apps quit all of a sudden all at once but I believe it might have been because it was starved of RAM, so it had to kill something and turns out it killed somewhat active processes (Screen dimming app + screen orientation locking app).

Otherwise no crash of any sort. Performance seems good and I cannot really comment yet on the battery life because I wasn't really paying attention. :)
[Nexus S Android Development] deetailed:
Thanks for informing, I wouldn't have guessed what the underline bold italic hints at. ;) Anyway, the reboots happened on two different ROMs, and not happening with the 3 other kernels I've tried, so it's natural to wonder. If the kernel's fine, then for whatever reason my phone/apps/usage habits/something aren't quite compatible with it... (which sucks).
[Nexus S Android Development] polobunny:
I've had reboots with pretty much/nearly any version before this one, some right after flashing even. No overclock as always.

You guys can spare me the "dirty flash" stuff too, because dirty flash or not they happened, and staying with a stock CM kernel everything is good (just doesn't have all the features of marmite).

If this one test version can fix the reboot, I'll be happy.
[Nexus S Android Development] babe0607:
I have the last paranoid and the last cm marmite.with ns toois i have select 200/1096.how to overlock to 1100?and which is the best minimum value for 1100?

thanks in advance...
[Nexus S Android Development] caliban2:
Well, it's not about a "dirty flash", rather about a "dirty system". You're on nightlies, iirc. Well, why has this combination been stable for weeks on my phone? It has to be something you're doing and I'm not. (Not talking about how we use the phone)
[Nexus S Android Development] g33kt:
Try to fix permissions dude

I also had many reboots on different ROMs until I fixed them
[Nexus S Android Development] polobunny:
I understand, but then again why one kernel and not the other? There's no reason it shouldn't work properly. It wasn't too long ago you had the weirdest glitches and no marmite was stable. Mine used to be stable, then whoop all of a sudden marmite would give me reboots for all the following versions no matter what.

All in all, I'm just saying that in defense of deetailed. Your sarcasm is misplaced I believe, because marmite just isn't stable for everyone, even running the same rom and kernel combo. Although I don't wish it, maybe some were just lucky enough not to encounter a freeze/reboot so far in their daily use, and reboot often enough to keep the problems at bay.
[Nexus S Android Development] jojoost:
How is this doing with Hellybean?
[Nexus S Android Development] caliban2:
Look at the download numbers for the last versions and then check that against how many people claim bugs here. Also, to a certain degree it's always the same guys.

What certainly is misplaced here is your unwillingness to think about what else could be causing your reboots. You seem very determined it's the kernel, not something else. Which is funny, since at least for your ROM-series I know it's (currently) stable -> look up the download-numbers for the last 5 cm-versions and think again. (Or do you think they're all suffering quietly?!)
[Nexus S Android Development] polobunny:
I think they simply might not be encountering the issues, as stated earlier. Different usage? Maybe.

Explain to me how you had problems in earlier versions of marmite while no one else did? That doesn't make any more sense, but the issues were there nonetheless. The latest version also reverted the .35 commits to try and fix that and also as stated earlier, so far so good.

I've mentionned having issues in pretty much all the versions I have tested lately, but alas couldn't grab the necessary information either from the lack of access to a PC or from having to pull the battery. It's a shame, but at least it notifies bedalus that there might be something fishy going on.

Either way, I would like your input on what could possibly causing the screen to suddenly freeze and show oddly colored pixels or go to a black screen is it's not the kernel or the rom, and cannot be reproduced at will.

Doesn't leave much place for silly "fix permissions" or "wipe system" stuff when that has simply no correlation with the problem and otherwise the phone is working properly.

There's no reason to act holier than thou with anyone reporting bugs in the thread for the only reason you're not having these bugs anyway, which is what I was getting at. We're all able to act civil here and try to point at the issues rather than use sarcasm on each other.
[Nexus S Android Development] BenHeng:
If I may, I had problem with bln and bld so far and nothing would Fix it. Yesterday, I had trouble with sync and decided to make a full wipe (solution I've already tried for fixing bln).

Today, everything is fine, no problem with bln or bld.

So maybe there is "unlucky flash "or something?

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] aladin6:
After a humble experience period, i'm believing of a weird fact: ALL SMARTPHONES(NEXUS S in our case) ARE

NOT

THE SAME.

Something (kernel) can work perfectly in my device, but not on yours even that we have the same smartphone. Strange fact, but we have to believe :D.
[Nexus S Android Development] alen1901:
Last kmsg here, BUT, this time and first time ever, it was on 6.2. Im shocked. :D i was sending message in inbox to my girlfriend with chrome, than it got reboot. Stock settings, all in my desctiption.

http://db.tt/gmpPvgX8
[Nexus S Android Development] :
I'm not certain whether or not the kernel has issues. But I'm happy that I'm slowly chipping away at things that might be sources of instability. I'd like to think that one reason a lot of bugs get posted is because I've been encouraging everyone (with caveats) to post their issues.

About the battery life without 200mhz. We want to keep the frequency at 100MHz as much as possible, to benefit from the reduced bus frequency. Working at 400mhz will mean that 100mhz speed can be returned to twice as early. This would save battery. However, there is the factor of voltage. While doubling the frequency doubles the battery drain, but halves the time required to do the work, the extra voltage required presents another overhead. How much? Roughly, V squared.

V@400 squared / V@200 squared = 122%

...so roughly speaking, doing a job at 400 costs 22% more battery compared to 200. But if the extra time spent at 100mhz saves more than this 22%, then it's a win.

My guess is that it's going to be a small difference either way, and it'll be buried in noise from the other systems (namely screen on time and cellular reception quality) and varying usage patterns.
[Nexus S Android Development] :
Try the latest version on the download page before you try the debug version. They're a bit out of date anyway.
[Nexus S Android Development] polobunny:
Very much agree with you, and if I'm still here testing every version I can it's surely because I can see the problems getting rooted out while being able to use a kernel with the features I want. Bleeding edge sometimes has a cost.
[Nexus S Android Development] :
Get onto the new version, I'm sure it's got at least two very real sources of instability removed.

There's nothing to indicate a kernel problem... But thanks for posting it. I'm assuming no OC... What phone and ROM please?
[Nexus S Android Development] BenHeng:
So far:

-5h since i started testing

-1h44 screen on (restored some apps, taptalk, agenda, gmail, sms)

-51mn @1Ghz

-12mn @800

-16mn@400

-55mn @100

-rest of deep sleep.

I'm on BB6, with all battery tweaks form PmR, "pure" on demand governor from marmite.

It seems pretty nice: it's really smooth (except with chrome, gone back to the good old browser), and doesn't seems to use too much the 400mhz step compare to the others.

Once again, thanks :)
[Nexus S Android Development] alen1901:
No oc. Rasbean 1.11., i9023. Now i will flash new ROM and latest kernel, i will report if something goes wilde. ;)
[Nexus S Android Development] kiko22:
Hi bedalus :) i'm the guy of the private messages... i try 6.7.1 and I like the decision to delite the 200mhz step, work great also at 1200 (reise voltage obviusly) ! However, the problem of the gpu oc persist... some app that use a lot of CPU (like need for speed most wanted) crash.. those app has random force close (without any message).

i'm not a developer, but i follow the projects on nexus s, and the gpu boost is wonderful :) (remeber live oc on GB?).. and i'm available for test!
[Nexus S Android Development] :
If the app is closing but the device doesn't reboot, it's not a kernel issue.
[Nexus S Android Development] kiko22:
okey, but such as I say to you in PM sometime a lot of app crash. --> the issue there is only at 1096 mhz, at 1200 all is good, such as I think that the problem comes from the gpu boost.
[Nexus S Android Development] polobunny:
20 hours in with the new test kernel and still no reboot or glitch. Hope I don't jinx myself on this one. ;)

Deep sleep is the most used state, followed by 100Mhz, then 1000Mhz. 400Mhz is used a bit but 800Mhz barely gets any love. Phone feels snappy to me on ondemand/cfq.
[Nexus S Android Development] caliban2:
The good old race to idle.

After 7 hours of use, behaviour in standby looks normal, 100 is used about the same as before. But there will be definitely some penalty for screen on time, because 100 doesn't register at all there.

I just hope you stop at removing the 200 step. ^^ Reminds me a bit of when thalamus modded ondemand so it would spend 60+% @1000 and claimed the snappiest system ever. Big surprise. If you follow that through, you'll end up with performance-gov. ;)
[Nexus S Android Development] aladin6:
No jealous :p , this is marmite kernel coupled with a 3800mAh battery with a very high intensive using (games, DATA, wifi, viber,etc...).

If i light up my using of the phone, i'm sure that i can reach 6 days without recharging the phone ;)

Good work bedalus ;).
[Nexus S Android Development] aladin6:
When the screen is on i think that 200Mhz is rarely used :/. Anyway, let's test bedalus's idea and see what it can results ;)
[Nexus S Android Development] spider623:
for rasbeanjelly do i need cm or all other version, also cause i was away a week what make bed to change his mind and test a no 200 build?
[Nexus S Android Development] caliban2:
It depends a lot on gov and its settings how much 200 is used, especially with smartassv2 (too long since i used ondemand, so no idea). Bedalus always aimed high (800 and above, so less 400 and even less 200) with smartass, but that's actually not needed anymore to have a smooth system. Roms (cm in my case) and especially marmite have come a long way...

@polobunny:

My funny reboots back then - I wasn't the only one, just most of the time the first to report them. :p

This was at the early stages of v4.x, a time when Bedalus fixed a lot of stuff. Really a lot.
[Nexus S Android Development] :
Is anyone else getting this problem?
[Nexus S Android Development] polobunny:
Oh and Caliban excuse me if I sounded harsh, I had a difficult day and I now realize I might have acted upon the impulse of the moment. It's not and wasn't in my intention to undermine your opinion or facts, but simply to voice myself regarding the issues some of us are still having.

No bitter feelings I hope. :)
[Nexus S Android Development] caliban2:
Huh, harsh? Where? Hey, I can take it, don't worry. :)

I'm putting my screen on-complaint on hold. Changing ramp_down_step to 400000 brings 100 back (had it at 200000).
[Nexus S Android Development] :
This is mine with Ondemand
[Nexus S Android Development] caliban2:
Yes, me yesterday with NfS most wanted when I was oc'ing. But since I got it one time with stock speeds also, I'm not so sure what's causing it. Looked more like an app-bug to me.

Regarding your screenshot:

That's with deep sleep, I was talking about screen on. Here's mine with my new smartass-settings (just reading and typing). Before it was no 100 at all. And with 200 enabled, 200 would be roughly at 15%, taken from 400.
[Nexus S Android Development] Basche:
I'm also getting the app crash on 1096 mhz, it's the same as kiko22, even in need for speed most wanted. I will try changing governors and see the result.

EDIT: I haven't seen the 6.7.1 update, will try it and see it the problem persists.
[Nexus S Android Development] deetailed:
Got it. There's in no stock version for 6.7.1 though. Can I use the one for all other ROM?
[Nexus S Android Development] treesurf:
I seem to have the old Android OS bug running the latest CM test version posted a couple pages ago. Running latest Strawberry, no OC, 9020T.

Not sure if this is a kernel issue, or if I should go back to the previous version of Strawberry.
[Nexus S Android Development] skavis:
restart

I was asked to forward this from tchaari over at slim bean. I also sent it to your inbox. hope thats not an issue.

Thanks.

Random restart after viewing account settings. Also lumberjack force closed on first open after the reset.

here is lastmsg file. (xda says my filesize is too large so i cant upload it 900kb)

so i put it here on uploaded.to - http://ul.to/039s34hn

If youd like me to email it instead, please let me know.

Using 2.9 - fresh install, clean wipe and format of SD before installation.
[Nexus S Android Development] :
This is what I got after waiting 30 seconds then typing in capcha

You have reached the max. number of possible free downloads for this hour, please try again in an hour or purchase one of our <a href="http://ul.to/register" target="_self">premium products</ a >.

Any chance you could use pastebin or zip the file before attaching it to xda?
[Nexus S Android Development] caliban2:
Looks like I have to rework my smartassv2-settings, or I have to say bye-bye to it as an all-purpose, balanced gov. Ramp-down @400000 let's it scale down to 100 MHz when doing "normal" stuff (browsing etc), okay. But now I get lags while playing games like NfS.
[Nexus S Android Development] :
If you set the ramp down to 0 it'll work out what step to drop to based on load. See if that improves the lags.
[Nexus S Android Development] :
The Android OS bug is a tricky one. If I disable the HIgh Res timers, this seems to cause a bug in the stats (not actual drain). Currently they are enabled, so this shouldn't be the cause.

It's probably Google Now or Google Location & Search. If you've got those disabled, it could be some other Google service busy doing something. Just wait a while and see if it goes. Or reboot.
[Nexus S Android Development] treesurf:
I'm not running Google Now and I have rebooted a couple times since I started noticing this. I'll try turning off Google Location and see how it goes.

Thanks for being such a responsive dev!
[Nexus S Android Development] kiko22:
..but with every other frequency there isn't problems. At 1096 the phone is smoother than at 1200, but sometime happened that a lot of process crash; two days ago for example the stock message app was affected by this issue too (force close without message) ... i repeat that the kernel is super stable with every other frequencies, at 1200 too
[Nexus S Android Development] _yaz_:
i think, life's not so simple. if it were, operation at 100/800 would give significantly lower consumption than 100/1000 but it wouldn't. the key is not to force the cpu towards lower frequncies but to distribute the frequencies the most ideal way so as to have the lowest consumption. for a certain operation the cpu must catch the ideal frequency so as to avoid lagginess or freeze but it should spend there the time what really but only needed ... the fine art of tuning the governor ;)

the exact logic of real life. sad but true. thx !

i don't think removing frequencies is the way to go. adding some extra intermediate frequencies would help much more, i guess. especially in the lower region.

depends on what you do. e.g. multimedia (listening music screen-on or watching video) may use that frequency very extensively.

yep, the solution. just replace the battery with a stronger one. @aladin6 what battery d'you use, exactly ?
[Nexus S Android Development] :
v6.7.2 is here: http://goo.gl/HvUrp

From v6.7 this version...

-Reverts Ezkeel's bigmem (lose 4MB)

-Raises INT volts for all frequency steps affected by FSB OC (when 1.1GHz is selected) but 1.1GHz and 1.2GHz are exclusively user defined.

-Completely removes the 200MHz step

I encourage all users of v6.7 or v6.7.1 to update.

I'm not certain if reverting bigmem will improve stability, but I've seen a few last_kmsges which seem to indicate some strange stuff happening with the memory, and if I remember rightly, the number of reboots went up when I added this. I also remember Ezekeel had a rebooting issue on his kernel that he couldn't eliminate, probably due to one of his mods, possibly bigmem, and it was difficult to pin down due to the random nature of the reboots.

Anyway, I think it's a case of suck-it-and-see... I can always bring that memory back if the stability issue isn't solved.
[Nexus S Android Development] :
Oops, sorry, builds will be back up shortly. I built the wrong branch!

Anyone who managed to get v6.7.2 before I pulled it, please redownload

EDIT: done

Link: http://goo.gl/HvUrp

Changelog: see previous post!
[Nexus S Android Development] waterface:
Let's not forget that those are relative percentages. 4h and counting at 78% seems rather good to me, there doesn't seem to be a real drain there.
[Nexus S Android Development] caliban2:
... by that I'd be introducing one of the downsides of ondemand, not very power efficient. ^^

I think I'll just stay with v6.7 for the time and wait how seriously you'll take this 200-stuff.
[Nexus S Android Development] BenHeng:
Or maybe you can just re add the 200step since you're used to tinker with CPU and governor settings?

Don't know if it's possible but I suppose it is ;)

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] :
Ondemand scales down to 100 very quickly, so it's good for power saving. I'm sure smartass can be tuned to provide a good balance between power saving and performance, but I think Ondemand has that. The only reason I'm including smartass is to have a governor that can be tuned to provide very high performance for gaming. I don't rate it for general use because it doesn't make as much use of 100mhz, unless you tune it for low performance, in which case it can't compete with Ondemand for responsiveness.
[Nexus S Android Development] alen1901:
Maybe its just me but 6.7.1 seems little bit slower than 6.2. while scrolling. I flashed latest SlimBean and 6.7.1, clean install, i will test it more and report if any problems. Im not ready yet to flash 6.7.2 due to volts change. :D
[Nexus S Android Development] kiko22:
has someone the same issue? ..however today i will try new test version