yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] :
Reboots may be that your phone doesn't like OC when your battery is running low.

There's no evidence of a kernel issue in the last_kmsg you posted. If it happens again, upload it again! Thanks for trying to help.
[Nexus S Android Development] :
You got your phone back yet?
[Nexus S Android Development] polobunny:
Phone has been up for 26 hours, can't wait for it to reboot. Or not reboot. :P
[Nexus S Android Development] :
:D I know exactly what you mean!

Did you go back to 4.8.2 after your reboot on 4.8.3 or did you update?
[Nexus S Android Development] mishamosher:
Hmm... battery was over 70 %... in both cases. Funny thing is that it didn't happen again, may be marmite is doing its work on my chipset :D

Anyway, thanks for the advice!

BTW, the 4 MiB extra on RAM are working great, zero troubles.
[Nexus S Android Development] treesurf:
24 hours on 4.8.3 with stock ROM and no problems. Thanks for providing this great kernel!

Sent from my Nexus S
[Nexus S Android Development] polobunny:
Using latest debug kernel. Didn't update my signature because it's cumbersome from Tapatalk.
[Nexus S Android Development] neosynthesis:
4.8.3 rebooted a few times

Hi Bedalus. After 24 hours with 4.8.3 non debug, it rebooted twice by itself last night. I'm back on the original 4.8.1 non debug for the past 18 hours without issues. If I have time over the next two days, I'll try and run your debug version to hopefully give you some useful feedbacks. Are there any special instructions for the debug version? How do I report a dump, etc?
[Nexus S Android Development] leap_ahead:
on 4.8 i can overclock to 1.2 .. with 4.8.3 my phone freeze with some apps on 1.2
[Nexus S Android Development] :
Okay, sounds like voltages then. I'll bump them up a smidge.
[Nexus S Android Development] :
After you notice any random reboot, copy /proc/last_kmsg somewhere safe, e.g. /sdcard then upload it anywhere I can view it. There's more detailed instructions via a link in the OP
[Nexus S Android Development] leap_ahead:
guys i create a fb page for bedalus kernel here : http://www.facebook.com/?ref=tn_tnmn#!/MarmiteKernelFromBedalusXda
[Nexus S Android Development] infernalMan:
i think bedalus would be a celebrity in next couple months :laugh:
[Nexus S Android Development] Articudos:
About the 200mhz problem:

http://xdaforums.com/showthread.php?p=20495078

Is this same problem? Actually, you(bedalus) thanked to ezekeel so..:p
[Nexus S Android Development] sdhanjal15:
It shows 100.
[Nexus S Android Development] :
This is exactly it. The GPU activating resets the min fq to 200. It's drops back to 100 though. That's why sometimes when you open nstools it reads 200. If you close and reopen without making changes, there's a good chance the gpu has shut off, and you'll see 100 as expected.

I'm not sure, but i think there's a possibility that trying to set the minimum by init.d makes it default to 200 permanently... But this idea needs more testing.
[Nexus S Android Development] Articudos:
Actually I don't care about it..;)

FYI,

Air 65fps version was able to set min freq. to 100mhz always.
[Nexus S Android Development] apatal:
Ok, I did some testing of my own on my current kernel:

After setting minimum cpu frequency to 100MHz via init.d scripts and NStools uninstalled, cpuspy hasn't captured any 200MHz event.

When I removed the min cpu frequency line in my init.d script, cpuspy starts registering 200MHz events.

I restored my original script and everything is back to how it was before, so I still think that line for setting the minimum frequency may be necessary still. Will report later if I still encounter any 200MHz reading.

So does matr1x. ;)
[Nexus S Android Development] migz012788:
Hello. Looking for kernel that runs good on gaming. So how was this kernel performs on games?
[Nexus S Android Development] sdhanjal15:
Maybe ask mathkid
[Nexus S Android Development] pan1980:
version 1.4 found here http://d-h.st/zcv doesn't works correctly ?
[Nexus S Android Development] niteh@wk:
Does this kernel work with the Jelly Bean SDK Port from steven76? I flashed it and it's stuck at the Android is upgrading / Starting apps for a long time.
[Nexus S Android Development] :
Not for me!
[Nexus S Android Development] pan1980:
so reflash 1.3 for testing or are you going to release new version anytime soon ?
[Nexus S Android Development] :
I doubt it. Nobody has reported it working.
[Nexus S Android Development] :
Hmmm, this needs looking at again.
[Nexus S Android Development] Blackcrx:
Quick note on charging limit. Even tho it shows 96% the changes still work. Last night I set it to 98% but stools still showed as 96% this morning after charging my phone the battery was at 98%

This was on v1.2, just flashed v1.3 and re test tonight
[Nexus S Android Development] :
You may need to select oc to 1.2GHz
[Nexus S Android Development] sdhanjal15:
MTP IS AWESOME!!! Don't even have to mount.
[Nexus S Android Development] Randomwalker:
IDK whether this is still of relevance as current version is 1.4, but for 1.2 I ran stability test (CPU+GPU) on different speed steps (200 -1200) for 20+ min. There were no problems except for 200MHz where I experienced a (hot) reboot.
[Nexus S Android Development] :
Niiiiice work! Thanks for doing that. I wouldn't worry too much about the reboot, I fixed some issues (my own faulty code) with the 200 MHz step in v1.3.
[Nexus S Android Development] :
I use BLX at 90% and it works fine.

The intended use of that mod is to lower the percentage, to stop charging sooner, and make your battery last more charging cycles.
[Nexus S Android Development] y3mita:
Explain something to me, BLX at 90 will save more battery? How? Isn't setting it lower charge less, therefore less time for your phone being on?
[Nexus S Android Development] anshumandash:
I have gone and liked the page. :) I think it's a good idea.
[Nexus S Android Development] ebs512:
bedalus, i9020 users get the splash screen, i9023 users boots fine
[Nexus S Android Development] benoit2600:
I've just got a reboot.

marmite 4.8.3CM

Cyanogen rom last nighlies

OC 1200mHz

smartass V2 - ( sleep ideal freq : 300mHz)

It happens screen off during listening music (with appolo player). It's the first reboot since I install this version, so approx. a week ago.

http://dl.dropbox.com/u/141920/last_kmsg
[Nexus S Android Development] FirePoncho86:
Will post my uptime in 6 hours! You guys are gonna like :)
[Nexus S Android Development] nightsky87:
So I haven't checked this thread for a few days and whoa... that's a lot of pages!

Anyway, with all the memory talk around here, I just remembered something. While I was accessing the framebuffer device in the attempt to fix colors, I noticed that the device maintained a virtual resolution of 480x5600. The strange thing is that the framebuffer offset switched between 0 and 800 which was just enough to address an effective 480x1600 (equivalent to two frames).

I'm not sure if the framebuffer driver actually uses the extra 3 frames or what... But if it doesn't, that might save you an extra 480x2400x4 bytes (around 4.39 MB)! Care to comment/check bedalus? :D

(Oh and I can't do the color optimization thing until I fully analyze the gamma codes which would have to wait until I'm done with school stuff... FYI :p)
[Nexus S Android Development] alen1901:
You wish. :p that damn samsung service is too slow in croatia. They said 10-15 days. now 13th day is passing and not a word. I hate them. Hoping for tomorrow, or they are waiting for the last day. O.o its not that hard to replace or glue screen. I would do it but hey, i still have warranty. :P
[Nexus S Android Development] :
Thanks! I've linked to it in the OP
[Nexus S Android Development] vraciu4you:
V4.8 works flawlessly with r_data's rom, 3 days and no reboot, charged it twice :D
[Nexus S Android Development] :
This is not a kernel error. Must be ROM or app. If you get more reboots, please continue to upload your last_kmsg! I will check them all.
[Nexus S Android Development] beppegg:
4.8 debug version is a very boring kernel. I haven't had a single issue in more than 30 hours! :D:D:D :victory:

I have to say that I'm out of 3G coverage -> Out of Internet (my data plan includes just 3G data)
[Nexus S Android Development] :
Yes! Lots of pages. I'm grateful to my testers, and try to reply to as much as possible personally. Although I encourage users to help each other, and be nice to the obvious noobs! We were all there once.

The extra 3 frames might be there for a reason. I know there is supposed to be triple buffering, so there ought to be only 2 extra frames. I suppose I'd have to see the routine that selects whether to write at 0, 400, 800, 1200, 1800. Do you know the location of the code?

Even if I can't work it out, I see no harm in a trial and error approach to reducing it.
[Nexus S Android Development] :
Is this with the new one I built for you?
[Nexus S Android Development] :
Have you got a link for that ROM?
[Nexus S Android Development] alen1901:
Yeah, i would also like to see this. Preparing list for flashing. :D
[Nexus S Android Development] leap_ahead:
+1 for flash ...really r_data rom ?
[Nexus S Android Development] :
Just had my first reboot! Yay! Looks like app or rom though.
[Nexus S Android Development] polobunny:
Wait, so this ROM has all the features from AOSP, AOKP, CM, Sense, Touchwiz and MIUI merged, right? :p
[Nexus S Android Development] meisze:
Air Rom :air.sloud.kr/2012/09/air-rom-build-5ns-gn-120916-korea.html?m=1
[Nexus S Android Development] anshumandash:
Ohhh...so this really exist. :confused:
[Nexus S Android Development] vraciu4you:
dunno if it's ment for us but this is the link :D

http://main.develoid.com:82/@ SAMSUNG/Nexus/Nexus S/젤리빈 기반/Air/

te only thing that is missing in r_data's rom is mobiledata toggle :(
[Nexus S Android Development] Articudos:
Because that's based on aokp.

Anyway, I tried it a long ago:p

R_data pushed air rom features to aokp gerrit, but that didn't merged yet..;)
[Nexus S Android Development] nightsky87:
This function in drivers/video/samsung/s3cfb.c seems to switch between the framebuffers.

static int s3cfb_pan_display(struct fb_var_screeninfo *var, struct fb_info *fb)
{
struct fb_fix_screeninfo *fix = &fb->fix;
struct s3cfb_window *win = fb->par;
struct s3cfb_global *fbdev =
platform_get_drvdata(to_platform_device(fb->device));

if (var->yoffset + var->yres > var->yres_virtual) {
dev_err(fbdev->dev, "invalid yoffset value\n");
return -EINVAL;
}

if (win->owner == DMA_MEM_OTHER)
fix->smem_start = win->other_mem_addr;

[B]fb->var.yoffset = var->yoffset;[/B]

dev_dbg(fbdev->dev,
"[fb%d] yoffset for pan display: %d\n",
win->id, var->yoffset);

s3cfb_set_buffer_address(fbdev, win->id);

return 0;
}

It seems to be called from an external source but I haven't traced that yet. Maybe you would know? But I'm doing a grep as well just to see.
[Nexus S Android Development] alen1901:
Bedalus, check this. :P

https://android.googlesource.com/device/samsung/crespo/+/android-4.1.2_r1
[Nexus S Android Development] FirePoncho86:
Well bed, you are a boss. I'm sure there are other kernels that can reach this, but not with a decent amount of the time gaming and heavy CPU usage...for instance a certain kernel came with my ROM and it gave me a reboot just because I was installing an app while gaming...but now I'm rock solid on 4.8!
[Nexus S Android Development] dimeim:
Hi and congrats on a great kernel! One question, is there really only one io scheduler? CFQ??? No deadline or noop or sio?
[Nexus S Android Development] polobunny:
Yep. CFQ gives the most constant performance. Deadline is very quick sometimes but seems to get stuck too often, and the difference isn't exactly a lot compared to CFQ. Deadline used to be there, but it got removed (without any complaint really).
[Nexus S Android Development] dimeim:
Ok fine with that :) just making sure ;)
[Nexus S Android Development] :
A hundred hours! I feel like you should win a prize or something!
[Nexus S Android Development] :
It was built 10th of September, so I don't think there is anything new in there. I've got all the commits from android-3.0/common already.
[Nexus S Android Development] FirePoncho86:
I'm just gonna keep going until I get bored of my ROM, or something.
[Nexus S Android Development] :
I'm looking at it now. The width of the y axis is a multiple of the number frames, defined here:

include/generated/autoconf.h:

#define CONFIG_FB_S3C_NR_BUFFERS 7

Lets say I bring that down to 3? Triple buffering right? 3 makes sense? Either it'll work or it won't! I'll build one and see if there's any impact on RAM. Or if it even works. :p

EDIT: Looks like that particular head is generated by some other process, so it's dynamic, and not included in my git. I'll have to find what's generating it first.

Aha, the .config file! Easy. These are definable:

CONFIG_FB_S3C_DEFAULT_WINDOW=2
CONFIG_FB_S3C_NR_BUFFERS=7
CONFIG_FB_S3C_NUM_OVLY_WIN=1
CONFIG_FB_S3C_NUM_BUF_OVLY_WIN=3

They are probably set like that for a good reason. But I'm gonna mess with them anyway...

EDIT: Yeah, that brings the RAM up. Time for a new release!
[Nexus S Android Development] CrackerTeg:
Haha. I like your style. If it ain't really broke, mess with it anyway. Lol
[Nexus S Android Development] :
Yeah! It seems to be working with 5 buffers. Got apparently 403MB RAM now. Will try 3 buffers. Maybe I'm imagining it, but Asphalt 7 seems to be running better too.
[Nexus S Android Development] CrackerTeg:
Interesting.
[Nexus S Android Development] :
http://d-h.st/cEo

Here's one just for Non-4G Non-CM based ROMs. It has 3 frames, and RAM is up to 406MB. All credit to nightsky87 for realising the extra four frames might be redundant. Seems fine on my system, please test and report back. Will upload other versions after sleep!
[Nexus S Android Development] CrackerTeg:
I'm still waiting for the debug kernel to poop out on me. Is this new kernel essentially the same as the debug but with less frames?
[Nexus S Android Development] :
It's got no debug stuff in it, so if it crashes it makes the last_kmsg file difficult to interpret. But, yeah, it's essentially the same, just with unused frame space reclaimed.
[Nexus S Android Development] CrackerTeg:
Nice. I just might give it a whirl then. Everything else has been pretty solid for me so what's it going to hurt?

---------- Post added at 08:24 PM ---------- Previous post was at 08:12 PM ----------

I gotta say, after putting my settings in, scrolling is notably smoother. Redundant frames are redundant. Props to bedalus and nightsky for this.
[Nexus S Android Development] polobunny:
Waiting for debug kernel to explode too. But it won't. :|
[Nexus S Android Development] mishamosher:
Got a second reboot, same scenario as in first case, only difference is that I was playing Asphalt 7 with AC charger plugged in and it happened at 15 minutes of playing.

last_kmsg attached.
[Nexus S Android Development] CrackerTeg:
Which version?
[Nexus S Android Development] mishamosher:
Refer to page 356
[Nexus S Android Development] 309041291a:
I missed why deadline was taken out. Isn't it the best for battery?

Nexus S (GSM i9020a)

Paranoid Android (2.1.3 - 4.1.1)

Marmite Kernel (4.7 - Bedalus)

Ondemmand (Screen On) (800/100)

Ondemmand (Screen Off) (400/100)

Deep Idle (N/A - Deadline)

BLX (98 - Inverted Apps)

Black Exodus (Stock Voltage)
[Nexus S Android Development] uncle_seuss:
Check out the legitimate Dev work. I'm really hoping a 4G kernel isn't too far behind
[Nexus S Android Development] nightsky87:
Great! Now its time to cross our fingers and hope that space really wasn't being used! :p I'll try digging around for more possibly-wasted memory when I have time.

EDIT: For the heck of it, maybe you could try 2 frames instead of 3. I haven't tried it with 3D games and such but from 2D graphics, I've only ever seen it use the first 2 frames. Though JB is supposed to have some dynamic double-triple buffering switch but hey, if it doesn't break, why not for an extra 1+ MB?:p
[Nexus S Android Development] mishamosher:
If I don't bad remember, the why is around 30~50 pages behind this.

And 2x if I don't bad remember it was taken out because cfq does a better work than deadline, it works better on 3+ I/O decisions.

And at least in the last 10 pages there are really (awesome!?) Battery durations reports with marmite 4.8+, which only has cfq, so I don't think its a big deal that deadline is gone :cyclops:
[Nexus S Android Development] granets:
deadline was taken out because it performed a little bit faster than cfq (a very little bit), but overall performance during long periods of time was worse. cfq is more stable, and to be honnest battery life with cfq and no deadline is better. also I guess not having extra things in the kernel that are not needed is better. I think this was a smart step - to remove something that is dodgy at best, and focus on optimizing something more stable
[Nexus S Android Development] alen1901:
remember me with 350 hours? :P 100 is little. ;)

---------- Post added at 12:06 PM ---------- Previous post was at 12:04 PM ----------

damn, i thought if they update to 4.1.2, they would update kernel too, but i guess no luck.
[Nexus S Android Development] :
Maybe there's some reason why the debug one doesn't crash. Sometimes there is alternative code that runs when debug options are set. It's a catch-22 situation. I need the debug code to see where the crashes happen but the code is preventing them from happening. Hmm. I suppose to be pragmatic, I could introduce a different debug option every build to see if one is uncrashable. It would take a while.
[Nexus S Android Development] alen1901:
i think you and bedauls are on the same line, try this and that, if its working, if it doesnt hurt, go more, try more. if it brokes try to fix. i like it. ;)
[Nexus S Android Development] Articudos:
Mainline updated to 3.0.45.;)

(Dunno it was included in latest test version)
[Nexus S Android Development] :
Will rebuild now. Thanks for the heads-up!
[Nexus S Android Development] leap_ahead:
ok marmite v is 3.0.45 thanks
[Nexus S Android Development] anshumandash:
I could see Bedalus updating the google docs live with 4.8.7 links. :D
[Nexus S Android Development] :
v4.8.7 is here: http://goo.gl/HvUrp

v4.8.6 was immediately deprecated by a mainline update. List of changes since v4.8.3:

-Update to mainline linux 3.0.45

-Very very slightly less red in colour

-Thanks to nightsky87 for realising that there were unused frames in the frame buffer. Reclaiming it has given us 407MB!

-Enabled CONFIG_BUG in the build configuration. I suspect this might be why the debug build never collapses.

Please feedback as per usual method. Enjoy the extra RAM! Thanks again to nightsky87, he totally called it. :D
[Nexus S Android Development] :
Yep, 2 frames works fine. Testing as usual on Asphalt 7. Good call!
[Nexus S Android Development] :
Ugh. it looks nasty. Looks like hardware error. Were you overclocking to 1.2GHz again?

I did a test build with a slight increase in voltage at 1.2GHz, but it crashed for me, so I'm back at 1300mV. I think maybe your device is just struggling to cope with the frequency.
[Nexus S Android Development] leap_ahead:
i get 408Mb free ram on 3.0.45
[Nexus S Android Development] :
I'm running the CM based kernel on a test build of Slim Bean (however, with the custom io control disabled, the scrolling is smoooooth) which may explain why there is a smidge less memory for me.
[Nexus S Android Development] capoooro:
After boring 80 hours of 4.8.3 :)

I pass to 4.8.7.

Free memory 405

Always on strawberry

No oc
[Nexus S Android Development] CrackerTeg:
I realize this is late but no. I won't.

It would've been less typing on your part to type three numbers and two decimal points.

Back OT, Dave! What are you doing to me dude! I haven't even run 4.8.6 for 12 hours yet! Yes, I rebooted several times but that was induced by my changing of the gps.conf and testing.
[Nexus S Android Development] nightsky87:
Great! Let's hope this doesn't cause any trouble elsewhere! On a different note, with the reduction in framebuffer count, I can retry my color correction by framebuffer rewriting... It should be much more predictable now!

Btw, is this the highest RAM achieved with the Nexus S so far? :D
[Nexus S Android Development] leap_ahead:
yes i remember on ics kernel 406mb max..

sorry if i am wrong
[Nexus S Android Development] :
Yes, i think so. Let me know how the frame buffer approach goes. I'm happy to build one for you
[Nexus S Android Development] mishamosher:
Yup, I'm at that freq.

With the previous voltages it didn't happen on my i9020A...

And I figured that reboots have bigger chances to happen when RAM is kinda loaded. For example, playing Asphalt 7 when the phone is freshly rebooted gives no trouble. Playing when the phone has 12+ hours up.... its a pain!
[Nexus S Android Development] nightsky87:
Sure! I'll try to build it using native code first to make things simpler. If it works, kernel integration might be good.
[Nexus S Android Development] mishamosher:
Anyway, it matters to you knowing that version?. If so, go figure on 356, if don't, stop filling the thread.

And thanks for advice, but being lazy isn't a friend at anywhere.

---------- Post added at 07:04 AM ---------- Previous post was at 07:00 AM ----------

@bedalus

Also gonna play some Asphalt without OC and 12+ hours of on-time, let's see what happens... any specific version of marmite you would recommend to give you the best error-related info?
[Nexus S Android Development] beppegg:
I've managed to break the old, debug Kernel!!! :D

Really, I dunno if the kernel was the real culprit... Anyway, I had a reboot during a phone call...

https://www.dropbox.com/s/knlm24rzstcdg05/last_kmsg_20121010_1503.txt
[Nexus S Android Development] polobunny:
It matters. This thread is mostly user supported rather than bedalus supported. While he tries to answer nearly everyone, it's better if he doesn't have to waste time answering previously answered questions instead of working on something better. Some kernels versions are known to be problematic, overclock or not, and we're all just trying to help each other here.

The kmsg you posted does not contain any version number too because it's not complete, so yeah, even bedalus couldn't know without jumping through silly hoops. It's also one of his demands to include version number and appropriate logs while reporting a problem. ;)

Edit: Your best bet is the latest debug kernel. Gives the most complete verbose of what's going on, doesn't feature latest mainline update and little extra RAM though, but that doesn't really matter since you're trying to troubleshoot your problem. Either way, it will likely crash because from what I can see, the overclock just isn't stable. It's not stable on AC, and even less stable on depleting battery, so there's little to no chance it would be better just because it's a debug kernel. :p
[Nexus S Android Development] leap_ahead:
too old kernel :P
[Nexus S Android Development] polobunny:
That's not the post 4.8.3 debug kernel is it? The version seems wrong, if I recall correctly.
[Nexus S Android Development] mishamosher:
And that's a constructive and helping comment!!, not like #3642... Thanks!

"Treat to others as you expect to be treated" - Juan Emilio Drault

Would be recommended to install the debug version on a wiped sistem? Or just flash over my current 4.8.3 marmite?
[Nexus S Android Development] anshumandash:
I too finally flashed 4.8.7 after running 4.8.3 for 84 hours. I got 407 MB on BB5.
[Nexus S Android Development] polobunny:
There wouldn't be any problem flashing over 4.8.3.

I had problems with 4.8.3 myself although not especially flagged as kernel related. I'm surprised some people are running it stable. I believe that's why bedalus reverted back to 4.8 state for the next debug, thinking he had broken something.

So far so good however, I am at 65 hours on the debug and there's no sign of weakness. no force close of any app, no lag or freeze. I am not overclocked however, I try to keep it stock until I find a perfectly stable kernel THEN I overclock, as to not mix and match problems. It's hard to troubleshoot if it's a reboot or freeze due to overclock or kernel bug, and I'm giving the man a break. :p