yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] invd:
Seems to work good right now (smartassv2, 1096/100) - playing a bit (Angry Birds, Asphalt 6), surfing with WiFi on - responsive (esp. gaming, browsing not too much) and quiet fast! No reboots (yet ;)).
[Nexus S Android Development] caliban2:
Yep
[Nexus S Android Development] capoooro:
For me the os android problem is OK with 6.0

Always with strawberry.

I didn't tried yet 6.0.2.

No sod no freez...give me a motivation to do it :)
[Nexus S Android Development] kiden:
I'm glad you found the high Android OS bug! I guess a problem did exist after all! I will be testing the newest version out shortly.

You rock man!

- Sent from my Nexus S.
[Nexus S Android Development] ebs512:
Not pressing for time waiting for 6.1, I hope I have enough time to test it before bb6 releases
[Nexus S Android Development] azrealsoh:
I have no reboots or crash with 6.0.1 ram test. Running smooth with 1.2ghz. But the extra ram not actually boost a lot, just 4mb more :/
[Nexus S Android Development] towelboy:
Just rebooted on test 6.0.1 with extra ram for cm. Had 9hours up time & was playing guns'n'glory when it rebooted
[Nexus S Android Development] JokerAce:
Pull some last_kmsg man. It's da map to treasures for Bedalus. Go to my link in OP for pro-tip on pulling the map for him
[Nexus S Android Development] Jamalsid:
Init.d script is not running at boot
[Nexus S Android Development] Accidd:
I found 6.0.2 much more battery hungry than 6. I have 77% after 44 minutes off charge. Yesterday I had excellent battery results running 1.2ghz than today with 1,1.

Sent from my MIUI Nexus S Jelly Bean.
[Nexus S Android Development] Articudos:
Plz check ur PM.
[Nexus S Android Development] mustatir:
Can u help me how to sure that your init script is work? Sorry for bad english
[Nexus S Android Development] :
44 minutes of screen on time?
[Nexus S Android Development] muller37:
Got a freeze with fuzzy lines on screen on 6.0.2 while writing a SMS.

I've hopefully attached the last kmsg for you.
[Nexus S Android Development] Accidd:
Yes. I just woke up, picked my phone from dock charger and I started to browse net and Tapatalk. Screen time was pretty the same as time from disconnect.
[Nexus S Android Development] :
This doesn't look like a kernel issue.
[Nexus S Android Development] muller37:
OK no worries. It was the first reboot I've had for a long time so thought It might be related to the kernel. It could be the oc my phone doesn't like. Newest version seems the snappiest so far!
[Nexus S Android Development] gregorypeg1000:
I have these freezes also all the time if i oc my phone at 1200mhz no matter the voltage.Now i am testing with 1096
[Nexus S Android Development] muller37:
That was on the new 1096 by the way. Don't usually over clock but was tempted by the gpu overclock and can say that it does make a difference. Temple run was unplayable due to the lag before but now its super smooth. :)
[Nexus S Android Development] :
The GPU is OC'd at all frequencies. If your phone can't handle CPU OC, stick to 1GHz, and it will probably be fine.
[Nexus S Android Development] muller37:
Didn't know that. Thanks man.
[Nexus S Android Development] aladin6:
The min frequency is now 400Mhz by default, I put it to 200Mhz as always... But a min frequency of 400Mhz all the time(when screen is on) i think that will be "hard" for the battery.
[Nexus S Android Development] :
That's not something I've done. Go into CWM recovery and fix permissions.
[Nexus S Android Development] hiphopboy:
i think need 1.2 Ghz come back :D
[Nexus S Android Development] Articudos:
Plz chek your PM:)
[Nexus S Android Development] :
I expect they'll be sued by Apple for it in some way. Didn't Apple invent watching tv? First they invented watching, then watching things came later. Then movement. I moved around a little bit yesterday, and I'm a bit worried because Apple did it first. j/k*

*Apple invented kidding.
[Nexus S Android Development] Warren_Orange:
Hi.

I have just rooted and unlocked my device.

I have just flashed Marmite v5 Stock kernel zip via CWM.

In settings I have no options to control any kernel functions. Is this correct??

The colour of the screen has changed slightly though.
[Nexus S Android Development] :
I can see I've made an omission in one of the bus frequency checks. I'll correct it, but it doesn't seem to have affected anybody. No complaints yet anyway.

I'm going to attempt to be more conservative with the bus overclock, and limit it be active only when at the OC frequency. That way users can have a completely stock experience when the upper frequency limit is selected to 1GHz. However, it might not be possible. I'm having a look now.
[Nexus S Android Development] jayjay3333:
Some ROM's do. SlimBean 2.7

What did you flash?

I also use ROM Toolbox it has an awesome new CPU controls and kernel tweaks.

There are lots of options. Setcpu, No Frills Cpu, etc. Also learn init.d script in OP.
[Nexus S Android Development] caliban2:
I have to say that 6.0.2 seems to be a great one, so please be gentle with changing stuff. Running for 14 hours now, including me being 7 hours in deep sleep (which means the phone was too). Since getting up I've watched a two hour video (yt, via WiFi), made two calls (10 minutes total), browsed the web for more than an hour (it's a lazy Sunday in the sun, in case you haven't noticed), took some shots and videos to test camera. I'm now at 46% battery, absolutely no lag or stuttering, no problems. The ui feels smooth no matter what I do.

Of course, after just 14 hours the big crash might still lie ahead, but so far this is the first out-of-the-box great version since v5 or v5.0.1. I've deleted all old zips and will keep 6.0.2 as my new fallback-kernel.

PS:

These are my settings, you see I'm not overclocking. I'm even tuning smartassv2 down compared to your settings, yet it still is pure butter. :)

#!/system/bin/sh

echo 1 > /sys/class/misc/backlightnotification/enabled
echo 1 > /sys/class/misc/backlightnotification/blink_finalstate
echo 0 > /sys/class/misc/backlightnotification/in_kernel_blink
echo 0 > /sys/class/misc/backlightnotification/max_blink_count
echo 100 > /sys/class/misc/batterylifeextender/charging_limit
echo smartassV2 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 400000 > /sys/devices/system/cpu/cpufreq/smartass/awake_ideal_freq
echo 100000 > /sys/devices/system/cpu/cpufreq/smartass/sleep_ideal_freq
echo 400000 > /sys/devices/system/cpu/cpufreq/smartass/sleep_wakeup_freq
echo 200000 > /sys/devices/system/cpu/cpufreq/smartass/ramp_down_step
echo 200000 > /sys/devices/system/cpu/cpufreq/smartass/ramp_up_step
[Nexus S Android Development] Warren_Orange:
Hi.

I'm still on stock 4.1.2. I haven't flashed a custom ROM. I just want voodoo sound and stability, that is why I stayed on stock.

I can see the kernel in the about phone settings. Everything seems really nippy as well.

Its just when I couldn't see any kernel options in settings I panicked that the kernel hadn't flashed properly.
[Nexus S Android Development] kwibis:
Bedalus somehow you managed to make my phone run at 1200 mhz. Something that was never possible. Now you switched to 1096 with gpu oc. How come this is not possible with 1200? I see also morfic has the same.

Sent from my Nexus S
[Nexus S Android Development] gregorypeg1000:
You can oc the cpu with 2 ways.With multipliers and by overclocking the fsb.So in order to oc the fsb(front side bus) he must use a different clock divider than 1:1 that is normally used.Cpu freq is fsb*multiplier.So you get the idea.
[Nexus S Android Development] :
@Caliban2: Yes, there does seem to be a conspicuous lack of bugs. I'm just tested my fix for the omitted code, and that seems fine. So now on to the FSB OC. I'm restoring it to the stock frequency of 200MHz because while it's nice to have 220MHz, I don't think there's any point it being there unless the system is under significant load. People can have 220MHz FSB as long as they select to 1.1GHz on the CPU, and only when that frequency is actually being used.

Anyway, if it causes problems, I can always go back to 6.0.2 and leave it as it is. But there is already code in there that dynamically changes the FSB fq according to current CPU frequency step, so this is just same principle applied at a different frequency.
[Nexus S Android Development] :
I tried it, but I just got reboots within minutes. I'm not releasing a kernel that I can't personally use!
[Nexus S Android Development] blakmazk:
Wtf, stability...

No more fun?

:(

Sent from my Nexus S..
[Nexus S Android Development] caliban2:
No, this actually is fun. Every few unstable releases you need a stable one, to see how it could be. Then it gets boring, ORD starts aching and you have to flash the latest, crashing stuff. After a while you want a break, just enjoy your phone for 2 days and you're back at the beginning of this post.

See? Fun all over! :D
[Nexus S Android Development] alen1901:
Haha, awesome. :p

Sent from SpeedMachine i9023
[Nexus S Android Development] caliban2:
I almost forgot, the younger generation probably needs an explanation what ORD is: http://htcpedia.com/forum/off-topic-lounge/2310-important-reading.html

So you see, be it bugs or behaviour - absolutely nothing you discover is "new". You're not special. :p

PS:

This reminds me of this video: https://www.youtube.com/watch?v=JmvCpR45LKA&feature=youtube_gdata_player Still gold! :rolleyes:
[Nexus S Android Development] dinuvali:
There might be a chance that Marmite 5.2 has a memory leak. I had been playing Cogs for 30mins and suddenly it started lagging and i couldn't do anything about it but reboot it. How would i go about diagnosing the problem?
[Nexus S Android Development] :
Nenamark2 results (three runs):

v6.0.2 FSB = 220 all Fqs (not 100MHz)
1096MHz 29.8
1000MHz [b]27.0[/b]

v6.0.3 FSB = 220 only for OC@1096MHz
1096MHz [b]30.2[/b]
1000MHz 25.6

...so for the imminent v6.0.3 release, I've limited the FSB boost only when you are at 1.1GHz. As a little bonus, it looks like something I missed in v6.0.2 has also given a slight boost to the FPS. Now, if you don't overclock, then the FSB remains at 200MHz, and as you can see, compared to v6.0.2, the FPS drops back to stock levels.

I've just played a few rounds of Asphalt 7 to test, and with smartassV2 the CPU was at 1GHz for 1 minute, and 1.1GHz for four minutes, indicating probably a few thousand transitions between the two states, and my phone is still running.

I'll upload shortly.
[Nexus S Android Development] caliban2:
I've read it 3 times, but I still get the impression non-overclockers (CPU) are being punished...?! :p
[Nexus S Android Development] :
It's not me. Non-overclockers are masochists.
[Nexus S Android Development] caliban2:
That's bull, and you know it. ^^ The real masochists are those who flash everything you toss at them, widening your test-range and providing you with data.
[Nexus S Android Development] dinuvali:
Don't be ignoring my post!
[Nexus S Android Development] caliban2:
Why not? People who bump their one posts after 16 minutes ask for getting ignored. Or did I miss something and you're actually paying for immediate support here? Can we do that now, pay a monthly fee and demand stuff?!

To answer your question:

See if it's reproducable. Check if it happens with other apps as well. And stop tossing around words you don't know what they mean ("mem-leak").
[Nexus S Android Development] :
It's possible. But since 5.2 there have been quite a few mainline updates. There's a link in the OP if you want to help find bugs.
[Nexus S Android Development] polobunny:
Where's 6.0.3 already? I'm still on v5 at 156 hours and I'm getting bored. That means rom flash plus kernel update, and I don't want no oooooold 6.0.2! :p
[Nexus S Android Development] :
You're right, I didn't see your post. But I would have seen it at some point, because I comb through the posts pretty thoroughly to make sure I haven't missed anything while I was posting.

Try to keep the thread friendly. Release coming shortly.
[Nexus S Android Development] :
here is v6.0.3: http://goo.gl/HvUrp

-Stable candidate. Just needs testing!

Please see the changelog for info. I encourage all users to update and feedback! Enjoy :D
[Nexus S Android Development] :
Get ready to experience :D ^
[Nexus S Android Development] caliban2:
Immediately after first boot it doesn't feel worse than 6.0.2. :thumbup: Now let's see how it behaves, maybe there really isn't a penalty for non-ovedclockers.
[Nexus S Android Development] gummie:
Hmmm I skipped other new releases after 5.2 since I get stable results on it, I even ran my device for 10hrs and I got 4hrs screen on time w/ all those heavy playing and browsing. Been shifting to ondemand 200-1000Mhz (normal usage) and smartassv2 200-1200Mhz (gaming) and it payed well as I have no reboot since installing 5.2 and I got good battery life on it.

As per 6.0.3 if it actually made it on stable I might as well flash and try it out. So for now I'm still gonna stay on this setup and enjoy it for a while.
[Nexus S Android Development] BenHeng:
Just so I know, are the LCD screen more power hungry than the amoled one? It may be that my battery is an old and battered one, but I'm having a hard time keeping the phone alive more than 12h with 3h screen on time.

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] alen1901:
flashing 6.0.3. Damn i cant even calibrate my battery how much releases are there. :p :thumbup:

Sent from SpeedMachine i9023
[Nexus S Android Development] caliban2:
With 3h screen time I really don't see where there should be a problem... It only would be bad if for the other 9 hours you had it in standby, all connections disabled and not one app trying to sync. (Making it a desk clock with a screen, which you never turn on)
[Nexus S Android Development] alen1901:
My phone really doesnt like GPU oc, so i will try with 6.0.3 at 1096mhz without voltage up to see how it goes. ;)

EDIT: Yeah, reboot. I thinks its GPU oc. Last_kmsg with your name. While using XDA.

Sent from SpeedMachine i9023
[Nexus S Android Development] BenHeng:
It's a (little) problem since i'm having roughly 12 hours shifts and need a sync on 2gmail accounts a least :p

However I wasn't complaining , I was just curious about the battery life of others reporting incredible screen on&off time :)

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] :
Combination of things... Aging battery, heavier OS, triple buffering...
[Nexus S Android Development] alen1901:
Oops sorry i didnt post last kmsg. Here it is.

http://db.tt/vpaOEUSX

Sent from SpeedMachine i9023
[Nexus S Android Development] :
Doesn't look like a kernel error. Try OC on some games?
[Nexus S Android Development] towelboy:
Its been a while... how do you do that again? Darn your rock stable kernels :D
[Nexus S Android Development] caliban2:
No no, you didn't complain. It's just that with the numbers you gave, it doesn't look like "yes, there's definitely smth wrong". But you can always try to tweak it. Okay, so you need gmail, but what other apps are synching in background? Do you need 3g? (2g only saves a lot) Bad reception (phone & WiFi) uses more battery. What about GPS and Bluetooth, are they off? Might try a different radio (can make it worse too). but don't expect huge improvements by a single step, it's about the sum of all them.

You get it, it's batt-saving 101. But as I said, 3 hours screen in 12 hours total sounds like a normal smartphone. :)
[Nexus S Android Development] :
There's instructions in the OP
[Nexus S Android Development] CrackerTeg:
I have bad news bed. These latest ones are unstable for me. Regardless of what I'm doing app wise, I get freezes followed by soft reboots. I reverted to 5.0.2 with the super high mem as that was the last snappy, stable version for me. I apologize for not pulling kmsg with these last versions.
[Nexus S Android Development] alen1901:
Its not a kernel problem, its GPU oc problem. I used 1096mhz for about 10min, played bad piggies, browsing and than i was going to xda report to you that that oc kernel is super fast, but then.. you know the rest. :p its super stable on 1ghz though. Its my phone, cant handle GPU oc, and CPU only to 1200 max and maybe it will reboot sometimes.

Sent from SpeedMachine i9023
[Nexus S Android Development] anshumandash:
My phone was butter smooth and fast with 6.0.2. I tried few games with ondemand and I was amazed. I am going to flash 6.0.3 now.

Sent from my Nexus S
[Nexus S Android Development] g33kt:
Thx for the great work dude! You did a great job by oc it to 1.1GHz but why you no try to make Marmite132 or Marmite144 like morfic?
[Nexus S Android Development] VerminX:
Gotta reboots on 6.0.2

Gotta first reboot on 6.03

Which version will give me solid stability on rasjelly? The kind I used to get with Trinity kernels but with no extra RAM and no voodoo
[Nexus S Android Development] CrackerTeg:
Because this isn't trinity and he's not morfic.
[Nexus S Android Development] caliban2:
What, all of them? Each and every version since 5.0.2?! Oo

Can't be, one or the other has been stable.
[Nexus S Android Development] CrackerTeg:
I didn't flash the ones between 5.0.2 and 6.0.3 or didn't have them long enough. These last two or three were instantly unstable for me using my usual settings. 5.0.2 was the one that stayed longest and was most stable. Kinda odd.
[Nexus S Android Development] :
Unless I see a last_kmsg it's hard for me to say whether it really is a kernel problem. Try and get one!
[Nexus S Android Development] gregorypeg1000:
I had a reboot on 6.0.3 while i was downloading an app from the market. Slimbean 2.7 i9023
[Nexus S Android Development] :
That's really odd. There's definitely a kernel issue there, but it didn't dump the stack after the oops, so I can't tell what caused it.
[Nexus S Android Development] ebs512:
I had a reboot when talking on the phone less than 5min, I need to be directed on how to do a last kmsg incase it happens again, is that like a logcat?
[Nexus S Android Development] caliban2:
Bedalus, reaching 5 hours with 6.0.3 and still smooth. Looking very good, despite the penalty on paper. :p :)
[Nexus S Android Development] dinuvali:
You go to /proc/last_kmsg and pull it. Careful not to reboot the phone in between.
[Nexus S Android Development] tchaari:
You need root explorer or any other file manager with root permissions and just grab the "/proc/last_kmsg" file.
[Nexus S Android Development] ebs512:
Thanks, bedalus here is the last kmsg I hope it helps http://db.tt/AOTNQVFn
[Nexus S Android Development] gregorypeg1000:
Had one more reboot.Is there a possibility that my phone needs more than 1400mv for 1096mhz?
[Nexus S Android Development] :
That's a good one. I'll investigate it tomorrow. I need some sleep!
[Nexus S Android Development] :
That's probably a lot more than you need. But I don't think it's voltage causing the problem. What ROM are you on?
[Nexus S Android Development] ebs512:
I didnt mess with any voltages, I had overclocked to 1096, it seems with users that dont overclock have no issue

Edit:

One of my testers has been on the phone for almost 10min overclocked to 1096 with no reboot so I'm not quite sure what the issue was, I also forgot to report, 30min after I flashed the kernel, I had it charging on the usb on my laptop with the screen off, I turned the screen on and a random reboot
[Nexus S Android Development] KrisMurdrum:
After being on stockv5 since an hour after it was posted (on a single uptime :eek:), with it set to: 200-1200 onscreen, 100-800 in call, 100-400 off screen (all ondemand); I decided to try the v6.0.3 today... And after adjusting to 200-1096 onscreen... Just.. >.<!!

First I had two instances of not being able to turn the screen on and had to pull battery twice. Each time the phone booted as soon as the battery was popped back in. No last_kmsg either. Unabled all profiles and set it to 200-1096 ondemand... Had been using as my calculator but jumped into the pizza app to order dinner. Half way through the screen doubled, not unlike old 3d movies with a blue hued picture on the right and a red hued on the left. Ten seconds later it rebooted.

Set the phone back to 100-1000 ondemand and pulled the following last_ksmg

Carved into the void with my Magic Rune Stone
[Nexus S Android Development] unlinker:
14h standby with on 6.0.1 with sync on, 3g on, wifi on and only 16% drain. Absolutely amazing.

Thanks for your work! :o
[Nexus S Android Development] alen1901:
Guys, who ever uses 1096mhz OC, remember that gpu is oc'ed too at this frequency. Bump up voltage for 1096mhz by +25. It should work fine than. Test it, your phone might reboot on lower battery levels though. You need to play around.

Sent from SpeedMachine i9023

---------- Post added at 01:31 AM ---------- Previous post was at 01:29 AM ----------

I talked 35min with girlfriend on your rom+m6.0.3, hang up, and after 5min another call that latsted 10-20min. So, your voltage needs to go up for oc. ;)

Sent from SpeedMachine i9023
[Nexus S Android Development] LibertyMonger:
I been testing and was using gtalk and the phone froze for a minute and rebooted here is last kmsg I had to zip it
[Nexus S Android Development] LibertyMonger:
Forgot to mention I was overclocked to 1096

Been testing for ebs512
[Nexus S Android Development] anshumandash:
9 hours with 6.0.3 on bb5, 200-1096, ondemand. Its running really smooth. Thanks Bedalus for such a wonderful kernel.

Sent from my Nexus S
[Nexus S Android Development] treesurf:
Had a freeze and reboot instantly upon changing to 1096. Running latest kernel on Radbeanjelly, i9020t. Posting from my phone so sorry no kmsg.
[Nexus S Android Development] KrisMurdrum:
Hey bedalus. Just noticed that in Rom Toolbox I am able to edit voltages on not only the previously stated oc freq but on all frequencies. (stock 6.0.3 Flo's 100.1% Stock Rom)
[Nexus S Android Development] ej8989:
i always get reboots whenever I OC. Tried 5.1, 6.0.2, 6.0.3

i use NSTools.
[Nexus S Android Development] gregorypeg1000:
[/COLOR]

Latest slim bean

Στάλθηκε από το Nexus S μου χρησιμοποιώντας Tapatalk 2
[Nexus S Android Development] atxbang56:
for those who have reboots : have you tried to increase voltage of the OC CPU Freq? try 1325 and then 1350 mV, for me 1325 is necessary to avoid reboots.

Sent from my AwEsOmE Nexus S

Samsung Nexus S

Android 4.1.2 Jelly Bean

ROM : MIUI 2.10.19 by MIUI France

Kernel : Marmite v6.0.3 ( CFQ / SmartAssV2, 1.1 GHz)
[Nexus S Android Development] Jamalsid:
I think the biggest issue people will be be having with the OC is not the clock frequecy but rather the FSB overclock. I remember Morfic having to spell it out for people in his thread that a lot of people just wont be able to run much if any OC on the FSB. Not sure of how users can test if it is the FSB OC or the clock frequency OC that isthe problem though tbh.
[Nexus S Android Development] dinuvali:
No reboots or freezes, but High Android OS usage on 6.0.3.
[Nexus S Android Development] VerminX:
I'm going to stay on 6.0.3 until next reboot and I'll make sure to post the last_kmsg. Thx for all your work!
[Nexus S Android Development] :
Have you disabled Google location & Search?
[Nexus S Android Development] dinuvali:
I always use Autostarts to Disable all the Maps events and some GSF (only the GTalk related ones).
[Nexus S Android Development] :
I've got 4 hours screen on time and 17 hours have passed since I charged it (to 90%)

In that time I've been OC'ing, playing a bit of asphalt 7, XDAing, I flashed a new version of Slim Bean, so I'm very happy with the power consumption and stability of the voltages.

If people are having trouble with the OC then you either need to

1) increase arm and int

2) increase arm and decrease int

3) decrease arm and increase int

4) decrease arm and int

...and do it methodically and in 25mv steps.

You may find you can never OC because your device can't handle it. In this case stick to 1GHz max.
[Nexus S Android Development] caliban2:
Bedalus, since you're here:

In this changelog, the two green marked kernel-commits - something you need to know about? http://changelog.bbqdroid.org/#crespo/cm10/1350859035

One never knows what they did this time... ^^