yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] hiphopboy:
OMG, so fastest ever with 7.1.6

Thanks bedalus so much :X
[Nexus S Android Development] :
There's an app you can use to reset the battery stats, but you'd still need to reboot. The charging thing sounds like a ROM issue.
[Nexus S Android Development] elnahir:
i9023, CM 10 Nightly 1206 freshly flashed > flash v. 7.1.6 > flash 4.2 Gapps. Video (natively + YouTube) works but sometime (over WiFi and 3G) it just goes round and round in circles.

Also, quick question: when I install NSTools and open it.. there's nothing there. As in - it's a black screen and nothing shows up. Also, the SuperSU app won't open - it asks for update, but never manages to complete it, and I can't open it.

These issues repeated themselves while flashing CM nightlies from the CM updater AND CM Delta. I flash the ROM, delete cache + dalvik, flash the kernel, flash the 4.2 Gapps. Any suggestions as to what am I messing up here?

7.1.6 seems stable for now, but I'll test it thoroughly today and report later.

Bedalus, thank you, man!
[Nexus S Android Development] alen1901:
I went back to 7.1.2. Transitions in opening apps are kinda smoother in 7.1.2. Maybe because i didnt reflash my rom. I might try clean install, but not for now. :)

Sent from SpeedMachine i9023
[Nexus S Android Development] JerryPi:
After installing the latest nightly you have to wait for supersu to get root access from superuser. Then go through installation of supersu, and remove superuser with some kind of root Explorer.

Nstools probably has issues because it doesn't get root access from supersu.

That's how i update: download the latest nightly from cm update, reboot into recovery flash it, flash gapps, flash the latest kernel and then wipe cache and dalvik cache.
[Nexus S Android Development] skinner12:
Hi,

I'm with aosp rom and I don't understand if I have to install kernel on column c or d.. Thanks

Nocerino's rulez..
[Nexus S Android Development] rockerblood:
if ur rom is cm based yhen u have to dl cm nightlies
[Nexus S Android Development] Blackcrx:
Sounds good. We'll be waiting.
[Nexus S Android Development] atxbang56:
any idea?

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] :
Sorry, yes, it might be something to do with bigmem. Someone posted a patch by rcrdbrt several pages back... but it's not my priority right now. I'll give it another look soon.
[Nexus S Android Development] madd0g:
Kernel source is supposedly out ;] The correct ones ..

JB kernel with bigmem, BLN and Voodoo would be excellent.
[Nexus S Android Development] atxbang56:
this?

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] JokerAce:
I agree that releasing kernel too often can be a bad idea. It increases your risk, although all people here knows that brick or damaged device is not borne by dev but user themselves, keeping your high standard reputation is the risk you would take.

Anyhow, I think the benchmarks you did were are rounds and rounds of testing right? Yeah, perhaps like what you say, after you have tested enough and gave yourself a margin of safety.. Release for tests... and release to public. :)
[Nexus S Android Development] KrisMurdrum:
So it appears that I had a random crash/reboot at some point earlier... Here's my last_kmsg thingy
[Nexus S Android Development] :
Unfortunately (or fortunately I suppose) there's nothing in there from my code. But thanks for posting it, and if you experience further reboots, post again! :)
[Nexus S Android Development] :
Okay, I've got a radically new tactic. JB is the future, so I'm going to move on to that source. As an experiment, I've created a new branch based on edoko's air kernel for JB, to see if I could get MTP working. No problem there, MTP works on JB just fine, tested with AdamG's AOSP.

So now, I just need to revert everything that edoko has done that I don't want, and then add all the same changes that I made to the cm base. But the first thing I'm going to do is check and see if Deep Idle will work, particularly with a fixed frequency. Obviously I need to check with edoko before I release any test versions of this.

EDIT: Happily edoko (r_data) says it's fine!

I'll get a workable version up, then start on the DI stuff.
[Nexus S Android Development] madd0g:
Might not be directly related, but I'm wondering if someone is already working on bigmem to work on the JB kernel source ?
[Nexus S Android Development] Randomwalker:
http://xdaforums.com/showthread.php?t=1469842

Remember kiddo: The solution is usually just a few threads below ;).
[Nexus S Android Development] Articudos:
Bigmem version released by r_data, but No ETAs for highbigmem :/

(Maybe kalim already made it..)

@Bedalus

Can't wait for that!

:p
[Nexus S Android Development] madd0g:
Yeah, just noticed it, it's hard to follow 3 different kernels at the time ;] How big is bigmem vs highbigmem (398mb)?
[Nexus S Android Development] Articudos:
As far as I remember,

When I was using AOKP m3, Free ram(which is displayed in Apps>running) was about 180~185MB.(@1st boot)

And high bigmem was 210~220MB(rascream)
[Nexus S Android Development] :
Here is a Jellybean only experimental version with DI @800MHz

v1.5(TEST): http://d-h.st/R2q

It may still reboot. I'd like to know, is init.d d working? If so, what ROM are you on?

Big thanks to edoko (r_data) for allowing me to post this, using his version as a jumping off point.
[Nexus S Android Development] doublewong:
Wrong Post
[Nexus S Android Development] sdhanjal15:
What features are missing. And I think brain masters jb ROM does. It has supercharger
[Nexus S Android Development] :
Thanks for the info.

About the missing features, compared to air, I've removed SIO scheduler, all governors apart from performance, and added my own tweaked ondemand and smartassv2.

I've also removed custom voltage, live OC, and my OC limit is 1.2GHz.
[Nexus S Android Development] sdhanjal15:
So far so goood. Will continue testing. BTW. If it reboots what should i do
[Nexus S Android Development] :
Collect the file /proc/last_kmsg and zip it up and upload it here if you can.
[Nexus S Android Development] Nemesis2k9:
Just flashed v7.1.6 all good so far.
[Nexus S Android Development] polobunny:
AOSP based rom or stock?

IF AOSP, C

IF STOCK, B

D is for Cyanogenmod based roms.

Last night my phone had a fit and the screen dimmed beyond acceptable levels, after 250 hours of CM kernel. I guess I can update my rom and test other things now that my uptime is broken. :p
[Nexus S Android Development] peepee999:
Dear Bedalus please can this kernel be made for Htc sensation running cm 10/aokp?

Sent from my Htc Sense Beats
[Nexus S Android Development] :
Sorry, different device with different quirks. I would have to own one to test
[Nexus S Android Development] :
Not many soft reboots being reported since either moving to any-kernel format, or updating the binder code. Probably the ramdisk was causing problems.
[Nexus S Android Development] xxxMADxxx:
7.1.6 flashed to MinlRoid ROM is the best for me..:thumbup:
[Nexus S Android Development] DjoeN:
7.1.6 Flashed on CM Nightly 2012-12-07

(Updated from CM 10 Nightly 2012-12-06 with 7.1.5 Kernel, through CyanDelta)

Everything i daily use, works fine (as before)
[Nexus S Android Development] polobunny:
No no you misunderstood me. CM kernel, not CM marmite kernel. :p

So now I can test some stuff. Just wanted to see how long I could run the default CM kernel before having an issue.
[Nexus S Android Development] :
Yes, I remember your test. I meant that the soft reboot issue may be solved here if you are testing marmite again.
[Nexus S Android Development] polobunny:
Oh haha. I will probably check marmite soon enough, kinda busy lately so it's sort of a good thing I backed away from crackflashing kernels. :p
[Nexus S Android Development] ranadroid:
Hello everyone. Can anyone tell whats the best settings for saving battery thanks. And what happened to deep idle?
[Nexus S Android Development] :
It's best to stick with the provided settings for saving battery. Deep idle will require some kind of serious mission to get working reliably.
[Nexus S Android Development] KrisMurdrum:
Reached about 170ish hours with v7.1.4 on my i9020t (XenonHD) when my three year old rebooted my phone. Never had anything but buttery smoothness and snappyness, so kudos to you Bedalus, kudos³ in deed ;)

Dork Víkings Magic Rune Stone
[Nexus S Android Development] :
Ah, I like a good report. :)
[Nexus S Android Development] shivasrage:
[/COLOR]hello bedalus

I have a question...better some questions...

Whats wrong with 4.2.1...?

Every thread i read everybody is talking about that 4.2.1 has this issue or this is messed up....whats going wrong with this release??

This has nothing to do with your kernel ...i know that but I would especially you to answer me in understandable words what the hell is the problem with 4.2.x that everybody is speaking of...?? I read things like google should fix the f****** issues. Now I´m a little bit confused can you explain ?

BTW flashed 7.1.6 CM without any problems....:good:

thanks S.R.
[Nexus S Android Development] polobunny:
Short:

Google stopped supporting the Nexus S, so 4.2.1 isn't optimized for the Nexus S but rather a "hack", people built it and try their best to make it work properly.

The last official version for the Nexus S is 4.1.2, that one has no problem whatsoever.
[Nexus S Android Development] shivasrage:
yes I allready know that...thanks for the answer but i thought there is a "allover" problem with 4.2.x

it was only a written thought by me....and have full respect for the guys that build 4.2.x for our device..

and its really cool what the do for us.........

greets S.R.
[Nexus S Android Development] migueldbr:
bedalus, what model of the NS do you have?i9023?i9020?
[Nexus S Android Development] polobunny:
Nope not at all. It's just that without Google help with the proprietary things regarding the phone, ROM devs have to hunt left and right for somewhat hackish solutions. They find workarounds more often they found the solution to problems.

The quality is still very good though, 4.2 is not completely different from 4.1 so we're not talking about day and night.

Unrelated note, flashing latest marmite right now. =)
[Nexus S Android Development] alen1901:
He has i9023

Sent from SpeedMachine i9023
[Nexus S Android Development] polobunny:
Random:

At the lowest brightness setting possible (1!), green only appears and stay at -11 green on the gamma in voodoo while using Marmite 7.1.6.

For reference (useless though), the red and blue channels are very tolerant to changes before giving you a color flash in the NS, red going down to -28 and blue down to -39.

I don't think one need to change the gamma values however, this is only asking for a green flash if you're going lower than -10 at minimum brightness.

Let the uptime commence.
[Nexus S Android Development] Jamalsid:
Not sure about that. He lives in the UK so he probably has the 1920T like me. The one with the AMOLED screen.
[Nexus S Android Development] DallasCZ:
hi everyone,

have a noob question. Do i have to flash the rom when i had 7.1.2,then tried air kernel and now want to go for 7.1.6?
[Nexus S Android Development] dirt:
Just flash the kernel. Wipe cache & dalvic if you want. No need to flash rom again, unless you want to.
[Nexus S Android Development] Nexus HAL:
you're right.. but proper gamma on amoled screen is just too good to give up :D

i'm trying something different.. instead of decreasing the brightness which tends to increase flashing.. i'm using 40 as lowest brightness point and applying screen filter app over it at 50%. apparently, it did something as i'm seeing a lot less green flash since. the tradeoff is ~4mb ram that the filter keeps to itself.

anyways.. now on 7.1.6 and couldn't ask for more.. bedalus.. you are the most selfless person i've come across here, specially now that i hear you actually own a i9023.. man.. nothing but respect for you! you are the best.. :highfive:
[Nexus S Android Development] alen1901:
My bad, i meant to say i9020. My fingers were trolling. :D

Sent from SpeedMachine i9023
[Nexus S Android Development] polobunny:
The issue with screen filter is that it decreases contrast, thus you're not really winning anything.

The default settings of 0 on the gamma and nightsky's 7500k on the multiplier settings gives decent colors already.
[Nexus S Android Development] Nemesis2k9:
Quick question. Do you guys get ghosting on superAMOLED displays?
[Nexus S Android Development] ReVo_007:
The new v7.1.6_CM working great on i9023 @1096mhz with default voltages . No soft reboots or freezing so far, been using it for more than 12 hrs now . Good work mate :) .

BTW can anyone tell me the best way to test the working of the voltages ? Previously the clock used to work good on benchmarks but gave random reboots. What is the best way to detect and eliminate that.
[Nexus S Android Development] superng888:
What do you mean by ghosting? I :confused:
[Nexus S Android Development] rockerblood:
Marmite V7.1.6 Initial test

i flashed marmite from 7.1.3 to 7.1.6, initial test as follow;

USB monting - OK

Deleting apps - OK

WIFI signal - OK

Multi tasking apss / games - OK

Camer / Video - OK

Bluetooth Transfer - still testing

I will post some test for daily use later :)

@bedalus - take some rest sir :) i know this last version are stable...
[Nexus S Android Development] :
I have amoled i9020!
[Nexus S Android Development] :
Yep, all the time. It's on a par with the pentile arrangement for minor annoyances, but overall it's a very nice display, and pretty good even in sunlight.
[Nexus S Android Development] :
I would wait until my battery is lower than 20% and use ondemand governor so the frequency will keep going in and out of max. If it reboots, try adding 25mV, if it reboots again, try -25mV. If it reboots again, try +50mV, if it's still rebooting, try -50mV, and if it's still rebooting, I suppose you could try +75mV, but at this point it's likely that your phone can't handle OC.

You might have to go through the same process with INT voltages too: open and close something like nenamark to get the GPU running.
[Nexus S Android Development] :
I use the XDA app quite a lot, and it loads up with a sort of brown/orange splash screen. The first moment this screen appears, you can see the 'ghosts' of the icons from the launcher.
[Nexus S Android Development] alen1901:
Yes i know, i fixed my answer, my fingers didnt obay(i guess it writes like that) to my order.

Sent from SpeedMachine i9023
[Nexus S Android Development] :
Uh, this thread is catching up with cyanogenmod 9 for the number of posts. I find that highly odd, and probably means I post too much! :p
[Nexus S Android Development] :
"Obey" as in "obedient"

English is a stupid illogical language and I admire people who learn it after their own.

What does this say? "Ghoti"

Looks like gotty right? WRONG!! It says "fish".

How's that?

gh in cough sounds like f

o from women sounds like i

ti from motion sounds like sh
[Nexus S Android Development] alen1901:
i meant to say, didnt obey, like, they didnt listen my brain orders. :D You must hear my language, its way more funny and strange than english. :p

Sent from SpeedMachine i9023
[Nexus S Android Development] Nexus HAL:
you missed my point, i am trying to achieve similar lower brightness level as CM color without the green flash. a display technology with a constant black-point is supposed to lose perceived contrast level with every bit of decrease in brightness. inevitable. that being said, not all filter apps are same, i found the one from haxor to be quite neutral.

default setting have decent colors but contrast is off. gamma test charts show it roughly at 1.6.. not a big issue for a phone display if used only as a phone. you know what i mean. what would've been ideal is the availability of at least two hardware calibration points- one for dim setting another for normal. any idea how're the newer genration samoleds in this regard?
[Nexus S Android Development] Nemesis2k9:
Yea I love the display but as you said, the ghosting is kinda annoying. To add to that I have noticed that the black status bar is now burning in a permanent mark at the top of the display.
[Nexus S Android Development] jayjay3333:
Yeah I have a I9020A and get get some ghosting. It doesn't bother me as much as @Nemises said about the status bar. I often hide it with Nova/Apex or use Extend Desktop option if the ROM has it (Slim). I see the time burn on most lighter screens. I often have a dark screen going to save battery but some apps or browser it is very clearly seen. I should have hid it day 1 (if it existed then??) and maybe it wouldn't have burnt in. :cyclops:
[Nexus S Android Development] jojoost:
@Bedalus

please take a look at this! is it the same as your kernel??

http://translate.google.nl/translat...n&u=http://bbs.ligux.com/thread-1935-1-1.html
[Nexus S Android Development] ReVo_007:
Thank you will try it .. the 7.1.6 just rebooted once but i was on smartassV2 .. now will try the way you suggested .. but nenamark is working good .. its just sometimes randomly .. anyway it will be sad if it wont be OC :( .
[Nexus S Android Development] alen1901:
Bedalus, i tried clean install with ROM and marmite 7.1.6cm, than the same with 7.1.2cm and 7.1.2 is way smoother in opening apps and switching between them. Guess my phone doesnt like 7.1.6. Ill stay with good old 7.1.2 ;)

Sent from SpeedMachine i9023
[Nexus S Android Development] csdibiase@gmail.com:
I've run into an interesting problem. With either 7.1.5 or 7.1.6 it seams that the modem crashes. This'd results in no data access and missed calls.

I've tried resetting to factory defaults, reinstalling cm10 stable. I'm starting to think its my phone :(

With 7.1.4 I get random reboots. Sadly I've not had the time to grab dish's from either the modem or reboot failure modes
[Nexus S Android Development] leap_ahead:
ohh same here the modem crashes
[Nexus S Android Development] nelars:
7.1.6CM working fine on Jelly Shot 4.2.1 for the last 35 hours and counting @ 1096 MHz - 9020T.

Excellent battery life, no reboots whatsoever.

Bedalus, thanks for your hard work and dedication.
[Nexus S Android Development] caliban2:
7.1.6cm was stable, no reboots, no modem-crash, no nothing. But I can confirm that it lacks in performance, especially app-switching is bogged down compared to previous versions. Now back to 7.1.5 and everything's snappy again.
[Nexus S Android Development] skinner12:
Is it better ondemand or smartassV2?

Nocerino's rulez..
[Nexus S Android Development] AzN MusiQ:
I set it to SmartassV2 because it going up and down only step for step.

Gesendet von meinem Nexus S mit Tapatalk 2
[Nexus S Android Development] invd:
Interesting, I made the exact opposite experience. 7.1.5 was ok, but 7.1.6 is really running, esp. with multitasking...
[Nexus S Android Development] dinos3:
7.1.6 + cm10=stable

Can you add deadline please? I see very good results in Antutu with deadline!
[Nexus S Android Development] :
I think this is an Android forum in another country where someone has independently decided to raise awareness of marmite. This kernel gets a lot of downloads in Italy. More than Britain I think! Here's some Google analytics: http://goo.gl/#analytics/goo.gl/HvUrp/all_time
[Nexus S Android Development] :
Did you let it settle in for a few minutes?
[Nexus S Android Development] :
I'll look into these modem issues.

Any other multitasking problems for anyone in v7.1.6?
[Nexus S Android Development] elnahir:
No multitasking issues on 7.1.6 (CM 10 Nightly 12 08 here), but I did get a random reboot. I'm on 1096, ondemand, otherwise everything is set to default. :)
[Nexus S Android Development] dinos3:
Me too!

1200mhz*
[Nexus S Android Development] Sucky1983:
No reboots or glitches with 7.1.6. Looks stable for me. Gaming, video, browsing etc. Without any errors in jellyshot 0.5.2

Sent from Nexus S with jellyshot 0.5.2, marmite 7.1.6cm
[Nexus S Android Development] alen1901:
Ofcourse i did. And restored apps with titanium backup, the same procedure with both kernels, two times. (I had some free time before i went to pick up my gf :D)

Sent from SpeedMachine i9023
[Nexus S Android Development] :
Hmm. That's quite interesting. I hadn't noticed any difference in the multitasking. I'll revert the backported code again, but keep the extra memory for one last version before 7.2

Let me know if it improves.
[Nexus S Android Development] elnahir:
Second reboot in 10 hours here. I could see some "snowflakes", just white dots flickering on the screen before the phone rebooted. Don't know if that's related, but I'm updating the CM nightliess via CyanDelta. I'll do it the old fashioned way today and report errors if I see any.

What I did was: flash the Nightly, wipe cache + dalvik, flash 4.2 Gapps, wipe..., flash 7.1.6, wipe. Only thing I change is that I OC to 1096.
[Nexus S Android Development] Sky-Net:
Hi all

If i overclock to 1096 using ondemand governor, system is stable

If i choose smartassv2 and try OC, i get a random softreboot (sometimes with snowflakes too)

I use stock voltages over cm nightly 20121206 and marmite 7.1.6 cm

Thank you all!
[Nexus S Android Development] _yaz_:
please, do ! i haven't mentioned this problem because i thought it's something with my providers (ip a/o pp). the signals are quite unstable and often drop to zero. sometimes even the pad is popped in to re-enter the pin but then the system restores without any intervention from me. i have several radio dunps which i haven't experienced since ages. i checked the signals with an other device and all perfect, so, i must say it's something with my crespo. (i'm on strawberry 4.1.2)

thx !
[Nexus S Android Development] bravo04:
want to report, i had 2 freeze with 7.1.6 + cm10 stable (i even got bootloop in this) and 7.1.6 + AOKP jb milestone 1.

OC to 1096.
[Nexus S Android Development] :
What radio are you on?
[Nexus S Android Development] _yaz_:
baseband is i9023xxkd1 (if you meant this)
[Nexus S Android Development] :
That may be why. You could try kb3 or the most up-to-date one, which I think is KI1
[Nexus S Android Development] :
v7.1.7 and v7.2 are here: http://goo.gl/HvUrp

No additions, just reverts of the backported code. See if multitasking is improved and feedback please! The only difference between the two versions is the memory. v7.2 has less and will be compatible for everyone. If you like more memory, use v7.1.7.

I was unable to solve the BLN issue with cyanogenmod's own toggle, because it can have an internal name which is either going to be compatible with nstools, or compatible with cyanogenmod's own system. It can't be both unfortunately!

Around five people in the last couple of days reported reboots, but

a) were over-clocking

b) didn't report their ROM

c) didn't report their device

d) didn't report the kernel version

e) didn't supply a last_kmsg OR

f) all of the above

Please, if you're trying to help me solve issues with the kernel, you need to report properly, and if you are over-clocking, I'm not going to be interested because the most likely source of instability is the CPU and/or FSB being pushed past their spec. Thanks!
[Nexus S Android Development] rzgomba:
Bedalus you have provably the best kernels for the Nexus S. I use only yours for my work phone. How about marmite for the GNEX ?
[Nexus S Android Development] Warren_Orange:
Hi.

What would be the best stable kernel version for stock 4.1?

I tried running v5 but got reboots when using streaming apps like Tunein radio.

Currently running Thalamas kernel.
[Nexus S Android Development] :
Version 7.2 all other ROM version will work.
[Nexus S Android Development] koeylondon:
So just to recap:

7.1.7- as many stable upgrades as possible, and it displays more free memory, though when using extremely resource intense processes, it seems to become unstable. Is that inaccurate?

7.2- Super stable, works for everything, a bit less memory. Correct?

Edit- I love when my son interrupts me and I forget to write in what I intended!

I did a search and couldn't find a good answer: Are the Scheduler/IO handlers optimized by default? I seem to remember noop being slightly more efficient in screen off situations (the vast majority of my usage).