yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] debaj:
Every single CPU responds differently to overclocking. If you need 1.3 GHz, then try playing with the voltages, maybe there is a setting where your CPU is still stable on this frequency. There is a very thorough although a bit technical article about it here, it is worth the reading, if you are interested.

(My device can't even go over 1 GHz without instability, although I do not have the time and partience to fiddle with the voltages, 1 GHz is fine with me. :) )
[Nexus S Android Development] caliban2:
Bedalus, I have to thank you one last time. You made the Nexus S the great phone it is for me, extending it's lifespan by 9 months. It was so much fun flashing your numerous test-versions and report back, because we all knew/know what was waiting at the end. Thanks! *bow* :)

Written from my Nexus 4, and I really hate to say it, but it blows the NS out of the water. Speeeeeed... :what: (maybe a bit too big though) I'll look you up once I get to buy my next phone, simply because I liked your attitude as a dev so much. Hope your wife does the right thing next time and gets you a nexus. ^^
[Nexus S Android Development] ciaastek:
So as a conclusion - Mess with the settings maybe even for days or simply stay at 1/1,1GHz? Thanks, I'll pass ^^ 1,1 is fast anyway.
[Nexus S Android Development] :
Cheers buddy! Your input was much appreciated! Enjoy your new device, and hope there's some cheerful devs in that section!
[Nexus S Android Development] alen1901:
Morfic, simms, rasbean are there. :p Lucky bastard.

Sent from SpeedMachine i9100
[Nexus S Android Development] polobunny:
Rascarlo you mean. Lol
[Nexus S Android Development] alen1901:
Oops, yeah, i meant to say rascarlo with rasbean. :P

Sent from SpeedMachine i9100
[Nexus S Android Development] caliban2:
Guess I am... :D On the other hand - no marmite.

What's ridiculous about this phone: it says 1.4 gb free ram whenever I check. Oo ^^
[Nexus S Android Development] :
Probably powerful enough to compile it's own kernel :p
[Nexus S Android Development] xis123:
Have you heard of the Seeder entropy generator tweak, bedalus?

http://xdaforums.com/showthread.php?t=1987032

You should have a look at it, I think you'd really like it! I think everyone will like it!

Brainmaster has kindly enough made a version for the Nexus S: You can find it in his tweaks here

http://xdaforums.com/showthread.php?t=1454289
[Nexus S Android Development] :
Sounds a bit random
[Nexus S Android Development] FirePoncho86:
Just read about Bed getting the One X+. I believe the Nexus s development is officially dying. I remember the days when I'd decide which ROM to use because of Bed's benchmarks, and I remember countless days of testing this kernel way back when I had the time. Most of all, I felt part of a community for the first time on XDA because of this thread. Cheers Bedalus, all the best!
[Nexus S Android Development] dotlab:
Agreed, it's obvious that NS development is fading. However, Bedalus said he'll stick around for a while so we just can't expect regular updates, but when something new shows up and it's usable for nexus I'm sure someone will hook us up like Brainmaster did today. My contract lasts one more year and I'm not gaming on my phone so there is no reason for me to go for something better, I really enjoy my Nexus. When 4.2.1 matures, it will be even better ;)
[Nexus S Android Development] polobunny:
I see what you did there. :p
[Nexus S Android Development] FirePoncho86:
I agree, all joking aside, I'll keep my nexus until it's painfully outdated, i get a good deal, or development actually dies here. I'm looking forward to the future of this kernel, but I'm nostalgic of the days when i wouldn't go on xda for 2 days, and this thread would have 30 new pages
[Nexus S Android Development] caliban2:
Agreed, the Nexus S is still great. I just updated because I originally wanted the N4 for Christmas (you know, "from myself, to myself") and couldn't buy it, out of stock. Wandered into a store yesterday and there it was. Well...

I have my doubts that 4.2.x will ever run smoothly on the NS though, RAM being the showstopper. Disabling lockscreen-widgets helps a lot though.

But 4.1.2? Good for another year. And just for laughs, I got my first reboot in ages, on a phone I own for 24 hours. Isn't that great? :banghead: :D
[Nexus S Android Development] dotlab:
I remember that, ICS at prime days :)

Yeah, I use 4.1.2 as daily driver but DerTeufel's 4.2.1 looks very promising, for me it's noticeably faster than 4.1.2 with same setup. I'm just having that weird GPS issue and if that get fixed I would gladly switch. About RAM issue, limiting background processes could help us a little...
[Nexus S Android Development] caliban2:
Jup, reducing background processes will help. I just hope for you guys CM & Co will be able to optimize it. Right now the biggest performance-gain is disabling lockscreen-widgets completely. That was the last thing I tested on the NS for 3 days. Nevermind gov, cfq or row - those widgets are key right now on 4.2.x. :)

PS: I really miss the softkeys for search and context menu. Search is just nice to have, but fixed context menu at the bottom I really miss. Depending on the app it jumps from lower right to upper right, never in the same spot. NS has its advantages... ^^
[Nexus S Android Development] :
I'm still here. I'm doing some crazy stuff right as we speak! Check this craziness out:

I had ubuntu installed alongside Windows on the desktop upstairs, but controlled it via vnc on the old PowerBook G4 downstairs.

Overnight last night I ran remastersys to put the whole install onto an iso then today I installed it in virtualbox on Windows.

Last, I added the original ubuntu install drive as a raw disk to the virtual machine and finally I can build the kernel in a hybrid virtual/physical ubuntu system running in Windows via a PowerBook! Good times!
[Nexus S Android Development] atxbang56:
crazy awesome guy you are

Sent from my pretty cool Nexus S

Phone : Google Nexus S i9023

ROM : Slim Bean Beta 1 (Android 4.2.1)

Kernel : Marmite v7.2.3 by Bedalus @1096 MHz (FSB OC)
[Nexus S Android Development] capoooro:
In Italy we say going from Rome to Milan passing from Palermo:)
[Nexus S Android Development] alen1901:
Than you should flash more your nexus 4. There is also navbar search button you can add on some roms. Flash rasbean! And franco kernel, or Trinity. :p i would really like to have n4. :( back on topic.

The most stable marmite for my nexus s is 7.1.2cm. And i will probably sell it with that kernel and jellyshot rom, or stock one. :)

Sent from SpeedMachine i9100
[Nexus S Android Development] treesurf:
As it was said when I grew up in Texas: that's like going around the barn to get to the cow.
[Nexus S Android Development] alen1901:
I bet he flashed aosp or cm. :p

Sent from SpeedMachine i9100
[Nexus S Android Development] Wir3start3r:
Nexus s Factory Image and this Kernel? good combo?
[Nexus S Android Development] jayjay3333:
Yup :good:
[Nexus S Android Development] :
Yes the interface takes some getting used to. I've tried cm 10, but I'm waiting for cm 10.1 or aokp 4.2.1 to be stable. Slim Bean is available for hox so I might ask krarvind if a port is possible for hox+

The kernel needs some work too!
[Nexus S Android Development] :
I think it's just what you're used to. I got used to a very minimal stock like interface, and I'm overwhelmed by the UI here.

What doesn't make sense to me is why there are no easy access to things like brightness and rotation. I don't like automatic brightness, which is always too bright, and I don't like my screen to rotate if I'm lying down, but I need it sometimes to look at a picture in landscape... Toggles make these things much easier.
[Nexus S Android Development] polobunny:
I hear you. CM10.1 on the NS still doesn't have custom brightness and even at the lowest brightness the damn thing is too bright during nighttime. Have to use additional software to reduce the contrast, annoying.

The notification toggle for auto rotation has been somewhat broken in CM10 & 10.1. In CM9 I used to be able to check only 90 degree rotation and toggling auto rotation on from status bar would "lock" the screen in landscape, toggling it off would make it go back to 0 degrees (portrait). Since CM10, toggling off from the status bar won't make it go back to portrait, but toggling it off from the screen settings will. So much for a polished rom...

There's so many other bugs regarding CM that it really makes me want to leave it behind sometimes, but they also have some customization very few if no other rom has, such as the sound & other settings profiles. Biggest omission in Android if you ask me.
[Nexus S Android Development] Wir3start3r:
could I use this kernel with pa 2.55?
[Nexus S Android Development] caliban2:
Regarding storage you have a point there. From 16gb only 12 are actually available. Have to dig during the weekend if it's possible to change partitions, 12 is a bit too less... And from what I've read, it's the same principle with the 8gb-model. But to whatever model in this class you'll update, it will be a new experience on all levels. :)

That's why you get a nexus - no wait. :rolleyes:
[Nexus S Android Development] FirePoncho86:
Ah, celebrities and their awesome shenanigans!
[Nexus S Android Development] rg2:
I am having issues with BLN remaining on after clearing notifications and turning off the screen; this occurs randomly. I can manually disable and re-enable BLN to get rid of the problem, but this doesn't clear the problem altogether.
[Nexus S Android Development] :
No celebrity would ever admit to that folly. Today I discovered I can run my VM headless, which means no graphical overhead on the host machine. Sweet!

Does anyone know why the magic packet won't wake the machine from hibernation?
[Nexus S Android Development] :
Sounds familiar. It shouldn't happen, but does sometimes. I've no idea why. Reboot to cwm recovery, wipe cache and dalvic, fix permissions, and if it's still happening, report back
[Nexus S Android Development] spider623:
what os, if win 8 you must disable the fastboot if any other something is wrong in your bios or you don't have set a forward port to the static ip of your pc

---------- Post added at 11:22 PM ---------- Previous post was at 11:21 PM ----------

btw off topic has any one saw this app?

does it work or just placebo?

wtf i was posting this on one other forum about wake on lan how did it get here? :confused:

@bedalus the magic packet doesn't work with hibernation cause the lan doesn't expect a package when shutdown the lan is on wait state unless read up for the posting mistake but and i'n not 100% sure there is a way to set it in wait by changing the power settings of windows and modifying some value on the driver preferences of your ethernet card
[Nexus S Android Development] :
Thanks, I'll check it out
[Nexus S Android Development] ppamungk:
Hi Bedalus,

I know that you work less for this kernel right now, but if possible, do you care enough to add the workaround for the entropy seeder in your kernel like the one done on galaxy nexus??? Hope you would consider to do it.. Cheers and thanks in advance....
[Nexus S Android Development] Ron Overdrive:
That's nothing but a placebo. Google even confirmed it has no effect on ICS and Jellybean.
[Nexus S Android Development] atxbang56:
if you try with games you'll see this is not a placebo effect

Sent from my pretty cool Nexus S

Phone : Google Nexus S i9023

ROM : Helly Bean Nightlies (Android 4.2.1) + BrainMaster Seeder Tweaks

Kernel : Marmite v7.2.3 by Bedalus @1096 MHz (FSB OC)
[Nexus S Android Development] ppamungk:
The one from the original thread is filling the entropy when depleted.. But the workaround from gnex dev is removing the command to disable preempt in random.c code so that it won't lock the I/O..
[Nexus S Android Development] :
I'm keeping an on the development for the nexus s kernel. I believe DerTeufel is still doing some original development, and if his memory idea works I'll bring it here.

The random seeding will affect cryptographic strength, so it's got a downside too. I'm not convinced the current situation is particularly bad.
[Nexus S Android Development] polobunny:
Using something such a Seeder will (technically), but fixing the kernel bug eating random entropy (not sure if it's applicable to NS and mailline) + disabling entropy generation from block layer to let HW do it's thing (if NS has such capacity) won't.

I don't think it's worth disabling virtual address randomization though, even if we have yet to see an exploit out there that could affect Android and furthermore would be prevented by virtual address randomization.
[Nexus S Android Development] yongxian:
Nice kernel.

I found a problem, not sure if it is common for all MTP kernel:

After downloading something into SD card via mobile or wifi network, and then connect to PC via MTP, but PC still recognise the old files in SD card which has not been refleshed, and can not see the new files. Reboot is needed to let PC recognise a refleshed SD card.

Can the auto reflesh be combined into kernel when pluging in PC? Appreciate your work.
[Nexus S Android Development] klinker:
I don't think is kernel issue...with rasbean and this kernel all working very very good on my crespo :)

On the road with my Nexus S...
[Nexus S Android Development] polobunny:
I believe that's an issue with MTP overall because once disconnected the media scanner doesn't run by itself like it would with normal transfer.

You can workaround this by running Rescan Media once you've disconnected your phone and transfered new files

https://play.google.com/store/apps/details?id=com.addz.mediascanner
[Nexus S Android Development] :
[deleted]
[Nexus S Android Development] :
The supplied OC volts match the trinity kernel, so you should experience crashes on that too. If you don't, then morfic has something else going on that's beyond my comprehension
[Nexus S Android Development] :
I didn't change the voltage for 1.1GHz, but obviously when 1.2 was replaced by 1.32 it required a higher setting
[Nexus S Android Development] polobunny:
You remember how 7.1.6 took like 500 hours to die on me? 7.2.2 doesn't seem that stable. Just FYI.

I don't know what you keep switching on or off, but some of our phones don't like it. :p
[Nexus S Android Development] caliban2:
Just passing through for old times sake, but I have the same problem on the Nexus 4. Guess polobunny is right, this is a general problem of MTP. Somehow I have the feeling it's Windows who's to blame though.
[Nexus S Android Development] alen1901:
Well, for me 7.1.2cm is perfect. Fast, great battery life and stable as hell. I can reach 100hours easy. It depends on ROM stability ofcourse. But 7.1.2 is allways on my nexus. ;)

Sent from SpeedMachine i9100
[Nexus S Android Development] polobunny:
:good:

I'm probably going to fall back to 7.1.6, you know, just to keep the majority of problems at bay. I'll look at 7.1.2 too maybe, although that's pre-anykernel so I'd rather not.
[Nexus S Android Development] :
Hmm, I'll have to have a look at what I meddled with recently
[Nexus S Android Development] polobunny:
Don't sweat it. 7.1.6 works, so it's all good. I don't need to have the latest shiniest things, heck, still using a Nexus S. ;)
[Nexus S Android Development] treesurf:
7.2.2 has been quite stable for me, even when overclocked. Using it with HellyBean ROM.
[Nexus S Android Development] :
I'm running pretty stable on 7.1.7 (@ 1200mhz) for now.
[Nexus S Android Development] anshumandash:
I am running 7.2.2 cm @1096. Its my favorite and the best version.

Sent from my Nexus S
[Nexus S Android Development] vis80k:
I'm having a rather strange problem.

when battery falls below 5% and the warning popup to plug into power, the touch inputs don't register properly. e.g. you touch the screen element but there is no action performed for that touch input. I thought it was the touch panel dying on me, but when the battery charges up, touch inputs register normally again.

I tried setting in the developer's setting the option to show touches on the screen. the touches work. it's just that the actions get missed somewhere in the code....

on rasbeanjelly 4.2.1 + marmite 7.2.3cm. tried all other marmites as well, the same problem.

anyone else having this problem?
[Nexus S Android Development] polobunny:
Strange things happen when your battery doesn't provide proper voltage. Happens often with batteries that are old/bad quality or if you're overclocking. Are you overclocking?
[Nexus S Android Development] klinker:
No problems here with same setup.
[Nexus S Android Development] ptr347:
The nex row io scheduler is great, all is way faster, like opening youtube or phone app
[Nexus S Android Development] towelboy:
So my parents just gave me their lg g2x, too bad they only have stable cm7 :D
[Nexus S Android Development] DerTeufel1980:
Could one kindly tell me the difference between aosp and cm kernel? Is it only ram and vsync?

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Nexus S Android Development] leap_ahead:
cm kernel is for the Cm base rom ,..like yours ..cm nightly, knzo rom because use Custom iocl ,telephony ... ... aosp is for rom from source or ota ...

the ram is the same on cm and aosp kenrel
[Nexus S Android Development] DerTeufel1980:
Yes, I know. But if I want to build a aosp kernel, I need to know the difference. It is only vsync?

Edit: sorry bedalus for high jacking your thread

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Nexus S Android Development] husen4u:
Can Is Use This Kernel With Jellybam ROM

http://xdaforums.com/showthread.php?t=2063631

I Install This ROM Before Few Days..So If I use This ROM I Have To Reinstall The ROM Again?
[Nexus S Android Development] superng888:
You can just flash the kernel :cool:

No need to reinstall the ROM
[Nexus S Android Development] anshumandash:
You can just flash the kernel without re-installing ROM. Please make sure you flash the CM version of marmite kernel.
[Nexus S Android Development] leap_ahead:
+1 for 7.2.2 411mb ram !!!but i think is battery eater !!! flash now the 7.2.3
[Nexus S Android Development] vis80k:
not overclocking. could be the old battery then I guess. haven't replaced with a new one since I bought it about a year and a half ago....

---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------

must be the phone then...or the battery as commented by another person....
[Nexus S Android Development] sidnoit22:
Can you please share the link of 7.2.2 I cant find it marmite downloads.. :/
[Nexus S Android Development] polobunny:
It's possible, if everything is fine on charge or at higher battery percentages, then my bet would be the battery.

I got an experience with a cheap chinese charger that wasn't of very good quality, it would make my touchscreen go haywire. Touches wouldn't respond, or something would double press.

As soon as I used the normal charger or unplugged it, everything would come back to normal. Just to show how finnicky these things can be.
[Nexus S Android Development] leap_ahead:
Up on 7.2.1 section
[Nexus S Android Development] sidnoit22:
There are 2 7.2.1 kernels. :confused:
[Nexus S Android Development] leap_ahead:
Click on the last and u get 7.2.2 link
[Nexus S Android Development] :
What appears to be the main concern in the latest versions is a backport for memory management from the 3.4 kernel. I did it because of an issue I was seeing in the last_kmsges posted for apps being killed immediately before a reboot, and thought the two issues might have the same cause, but I think actually, the reboots were caused by the ramdisk, and that issue was fixed with the any-kernel script, so probably I need to revert the backported code. I'll do it when there's something new to add from the mainline and/or android-3.0/common, otherwise just continue using your preferred version.
[Nexus S Android Development] polobunny:
Party hard! =D

Can't REALLY say the more memory thing is the problem, because 7.1.6 was quite good to me. Might have just been lucky, but 500 hours without a reboot seems decent.

But from there on, no kernel was as stable as this one to me. I usually flash 7.2 when testing things, but I haven't attempted such a long uptime with it.
[Nexus S Android Development] leap_ahead:
7.2.3 normal battery ...with 7.2.2 my battery fast drain ..
[Nexus S Android Development] :
I reduced the screen refresh rate too. Maybe connected.
[Nexus S Android Development] killex23:
Hi guys, i'm reading the marmite7.1.2 si very stable band has a very good battery life. I ha ve tried many version of this kernel but not this. I haven't found the link of this version....can you post me this link to download it?
[Nexus S Android Development] jokkir:
Just wondering but does this kernel work with 4.2.1 properly? I flashed it on CM10.1 (latest nightly) and I seem to have lost the option to change the governor to conservative. It was there in CM10 (last nightly before 10.1) but it's gone here. This is all the governors I have left:

Anyone know how I can fix this (if possible)?
[Nexus S Android Development] polobunny:
It works mighty fine and that's perfectly normal. Governors are programmed in the kernel, and this kernel doesn't include conservative, willingly. Is there a reason why you want to use conservative?
[Nexus S Android Development] Basche:
Just like how polo bunny said, the conservative is not available, but if you're looking for battery saving, use ondemand. I read somewhere that the setting for smartass is for more performance.
[Nexus S Android Development] jokkir:
Ah, I remember having Conservative while on CM10 with this kernel. Maybe I was imagining things.

I just want Conservative when my screen is off while playing music to conserve as much power as I can (plus 800MHZ as max freq).
[Nexus S Android Development] :
I'm pretty sure on demand will use 100mhz for music. You can test it with cpuspy
[Nexus S Android Development] maarrrrr:
7.2.3 takes soooo long to boot rasbean...
[Nexus S Android Development] polobunny:
Bedalus has made some cleaning. Conservative support was dropped for it didn't prove more power efficient than ondemand but proved slower.

Pegging your maximum frequency and using a screen off profile is a bad idea anyway. They have long been proved inefficient.
[Nexus S Android Development] jokkir:
I was trying different ways to save more power and since I bought ROM Toolbox on the Play Store recently and had an option for CPU Profiling, I thought that I might as well try it. Do you have the link to show that it's inefficient? I would assume it's because the service is currently running to check if the screen is on or off thus the CPU is constantly running?

And thanks, guys! I'll try Ondemand today
[Nexus S Android Development] polobunny:
No I do not, but I believe it was Bedalus himself that did these tests. Don't quote me on that, it's a tad early in the morning and I'm under a buttload of work haha! Might have luck either checking the first post in this thread for the link OR running a search in this thread with a keyword such as "conservative".

Ondemand is a very efficient governor because of the way it operates. Doesn't tax the system much because it's very simple in its programming. Other than governor though, there's also the different governor settings you use, which can matter much more. The ones provided in marmite have been long used by a lot of us and proved to be a good balance of saving & performance.

It's good to note that other than performance, which pegs the minimum frequency at the maximum frequency, nearly ALL governors are very efficient when your screen is off and your phone is idle. Conservative, smartass, ondemand, interactive and so on all drop to their lowest frequency and then to deep sleep, thus saving the same amount of power. The difference is mostly in the time your phone is being used (screen on) or doing some background processing (screen off + stuff running).