yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] :
https://docs.google.com/spreadsheet/ccc?key=0AntDDKv-lS6IdDhjVWYyanhBODViSWhYWG03QldYcXc

I read the changelog for gcc 4.7 and there is extra optimization support for arm v7, so after enabling it with -mcpu=cortex-a7 in the compiler flags, performance seems to have improved, as you can see in the spreadsheet above. The overall difference seems to be in the region of 1%

Also, the gcc 4.7 compiler spat out a warning that gcc 4.6 didn't. Fixed now! An uninitialised variable that actually turned out to be completely unused, so I've commented out that code.

Try out the result in v7.0.3: http://goo.gl/HvUrp
[Nexus S Android Development] rockerblood:
i have no problem on video recirding coz im using 4.2 version of camera:) gotta try the newest one im on 7.02 now

update: still doing great on 7.0.3 video recording smooth nd camera capture. the best! thanks

Sent from my Nexus S™ i9020A
[Nexus S Android Development] :
There's 3 hours of DI use today, and I've been at work, so no music. I think it's probably worth having it enabled.
[Nexus S Android Development] :
Hmm. I may try and build for JB by taking bigmem out, but i can't guarantee it'll work.
[Nexus S Android Development] caliban2:
Bah, forget fooling around with jb until it's released. Something's wrong with final 1.4, it rebooted on me. I was browsing twitter when tweetcaster and nova-launcher fc'ed. Then the reboot.

Very short last_kmsg, have you disabled practically all debugging? :)
[Nexus S Android Development] :
This kmsg is from recovery. If you reboot into recovery after a crash it overwrites the last kmsg with a recovery kmsg
[Nexus S Android Development] caliban2:
I see. Problem is: I didn't do that.
[Nexus S Android Development] Blackcrx:
Almost the same thing as what happened to me.

I still think 1.4test original with 400mhz DI is the most stable
[Nexus S Android Development] caliban2:
Edit:

*nevermind*
[Nexus S Android Development] :
Then this is a last_kmsg from the last reboot you did to recovery, and when you had a crash, your current kmsg log never got copied over that. My kernel script doesn't wipe cache or dalvic. thalamus said wiping dalvic is a myth, but you may still need to wipe cache if you get problems.
[Nexus S Android Development] Blackcrx:
I made the mistake of rebooting in to recovery. But I edited my post since you said you didn't reboot in to recovery like I did.

I rebooted back to recovery to flash the original 1.4test that we both thought was rock solid.
[Nexus S Android Development] caliban2:
You see, I'm able to read scripts and thus know yours doesn't wipe caches. That's not the problem.
[Nexus S Android Development] :
Edit: testing version for JB didn't work!
[Nexus S Android Development] Blackcrx:
no offence bedalus, i really appreciate your work on benchmarking and kernel.... but it seems your "stable" 1.4 has crashed a few times with different ppl.

i am in no way a developer but personally i feel that your original 1.4.test with 400mhz DI is the most stable out of all your kernels so far. the original 1.4.test has ran solid for over 4 days broken up in to sections (from 12-48hrs) where as all your other kernels have crashed at one point in time in less than 12hrs.

Maybe try building off of that kernel. this is just my opinion so please dont take it the wrong way
[Nexus S Android Development] polobunny:
Seems to me 800Mhz version is even more solid. Nobody had a problem with 800Mhz, right? It's fun to try and make 400Mhz work right, but what if it doesn't? :p
[Nexus S Android Development] caliban2:
Well, the mentioned 400-version has never been released to public, so you can't compare it to the 800. But I agree, it's been the most stable (as in "no problem at all").
[Nexus S Android Development] Blackcrx:
correct me if i'm wrong but if i recall all the public released versions are 800mhz DI which a few ppl have had crashes with. As caliban said, the 400mhz was a private release for a few ppl only.
[Nexus S Android Development] polobunny:
Yeah I was mostly judging from the apparent feedback. :)

Is the last available 1.4 in first post, fixed at 800Mhz, deemed "stable"? Running 1.3b so far and not having issues, so I don't really want to create some when everything's running smoothly.

Edit: I don't know, thus don't plan on taking the offer to correct you. It just seemed like all that has been happening in this thread lately was problems with the 400MHz versions, not the 800MHz ones.
[Nexus S Android Development] :
Like thalamus suggested, it'd be better still to put the new code in a function, that can be called in the right places. It's pretty obvious now, but i was too wrapped up in the minute details to see the bigger picture. Once I've done that I'll make a patch, then I'll see if any other developers are willing to try an experimental build. Or kang another kernel with my patch myself. It'll help to establish whether it's the performance DI, or something else causing issues.

There's been over 300 downloads of v1.4, so if you're one of those people please let me know if you've found it unstable. Post your last_kmsg if you can.

But if my memory serves correctly, the only problems people have experienced have been with the 400MHz version. So far I've yet to see a kmsg that points to my code. When I see one for 800MHz, I'll know whether it's a problem I've caused.

I'm looking at the modifications thalamus suggested at the moment.

EDIT: Okay I built with the modifications... now to see if it boots/works!

EDIT2: Huh. It built without telling me I'd made any mistakes, now it booted, and appears it is doing exactly what I wanted. Looks like I got it in one. Now to make the patch.
[Nexus S Android Development] :
Fun. Made my first patch, using the function idea that thalamus suggested.

Let's see if kalim will have a look.

I'll build a new v1.4 and upload it as a test version, however, if anything it should be at least as stable as the current stable, because the code is called from the logical places.

Edit: DO NOT USE, UNSTABLE
[Nexus S Android Development] N@th_OC:
For people who've got problem with the JB version of bedalus v1.4.

Please open the zip, go into "/systeme/lib/" and delete the "HW" folder.

It's due to a differnce between the drivers of ICS and JB concerning the Hardware acceleration and GPU rendering.

Since JB implement triplle buffering and vsync, those ICS drivers are not compatible
[Nexus S Android Development] :
D'oh! I forgot about that. Is it working? I already pulled the download links. If you can confirm this fixes it, I will re-upload.
[Nexus S Android Development] treesurf:
Looking forward to the extramem version of v7. :)

Sent from my Nexus S
[Nexus S Android Development] skarayala:
Why this kernel don't include anymore the Trinity color?
[Nexus S Android Development] slipkory:
which version gave highest extra mem ? :) i want to try with MDO Rom .
[Nexus S Android Development] :
Try v7.0.3
[Nexus S Android Development] :
A colour expert said my colours have a stable whitepoint, meaning that as the brightness moves there is no bias towards a particular colour. You can set your own RGB values with the voodoo app, or a script (see op)

nightsky87's thread: http://xdaforums.com/showthread.php?p=32793734
[Nexus S Android Development] rockerblood:
thats right OP after using your kernel my graphics are improved unlike before in stock kernel. white balance are more clear as in white for white thing nd black for the dark thing:)

Sent from my Nexus S™ i9020A
[Nexus S Android Development] :
I'm thinking of disabling fsync, but IIRC there was some version out where it was possible to toggle it on and off. I'm thinking of having it automatically engage at 1GHz and up to reduce the risk of data loss if there is a hard reboot.

I might also switch to BFS task scheduler for an experiment. This produced a 3% increase in performance when I last tested it. I think I'll look at BFS first, since it should be immediately obvious if it breaks stuff. http://en.m.wikipedia.org/wiki/Brain_****_Scheduler#section_1
[Nexus S Android Development] rockerblood:
okay sir no problem to us just take ur precious time. remember guys, "patience is a virtue" looking forward to ur next great updates to fit all rom in nexus s section:)

we are always here to do the test count on us....

Sent from my Nexus S™ i9020A
[Nexus S Android Development] C4SCA:
as hard is to me to say this...

today i gave a shot to marmite again and at least for stock rom its SO MUCH SMOOTHER! (1.2ghz, smartassv2, cfq, BLN)

one thing to point is that Blink BLN doesnt work for me :( fixed permissions on TWRP and i can change the settings of blink but it doesnt take effect

thanks!

byebye matr1x and lets get back to marmite
[Nexus S Android Development] jiro-kun:
I totally agree. During ICS days I'm a matr1x fan, nothing could beat thst kernel. So i thought JB was the same.. Until that faithful day.. I tried give mermite a go.. And OMG! The difference was significant. Until today.. Im still amazed by the kernel.. Putting a 2 year old phone back to life.. Haven't looked back to other kernels since mermite.. A true fanboy of mermite, i have become. lolz! :D
[Nexus S Android Development] C4SCA:
Does BLN blink works for you?

Bln works great for me but not the blink feature...
[Nexus S Android Development] kiko22:
I say the same thing in the previus pages

i'm sad, becouse i like this feature too
[Nexus S Android Development] C4SCA:
Thanks! ;)

Im less worried now...

I prefer to lose blink instead of stability.

Great job bedalus

sent from my old (but gold) Nexus S
[Nexus S Android Development] kiko22:
SURE!!
[Nexus S Android Development] rockerblood:
me toi stability than beauty:) but this rom has epically unique style..

btw the reboots happen again, tje first one is when im browsing fb nd the second is google play browsing, why this happen? how do i found log cat in here?

Sent from my Nexus S™ i9020A
[Nexus S Android Development] dekaru01:
Please don't hate on me for asking this. I'm not the noobest of noobs, but sometimes strange things do happen.

I ran 6.7.11 from the moment it got released until a few hours ago. No issues whatsoever. I even OCed to 1200, all was fine.

Until, that is, I decided to mess with the governor settings, changing ondemand values to 10000 and 85 (default 40000 and 95). Then the reboots started. At first it was with OC, so I switched to 100-1000, but I still got a reboot in less than 10 minutes. Then another one about a minute or so after booting. Not sift reboots, mind you, but 'full'.

No last kmsg unfortunately since I was on the road and needed my phone. Any logical explanation for this?

RBJ 11.06.
[Nexus S Android Development] kiko22:
try to return to standard ondemand configuration!

if reboots persist, write here again :)
[Nexus S Android Development] polobunny:
I'm at 46 hours and all is fine. No reboot soft or hard.

YouTube and video works however YouTube high quality on some video (higher bit rate I imagine) makes the video stutter a bit sometimes. I didn't get time to test if it was due to the added ram or if changing the governor could help.
[Nexus S Android Development] kiko22:
@bedalus ....do you never think to try to compile a test kernel with a little oc too, for example 1050 + gpu boost? i remember when with GB and ICS users could have good performance with only a 105% live oc. I don't know if it will be difficult or completely useless.. or that there aren't differences with 1096!!!

it's only an idea
[Nexus S Android Development] polobunny:
I don't think there's a point since 1.1GHz has GPU oc. It's too little of a difference to put efforts into it in my opinion.
[Nexus S Android Development] CrackerTeg:
Agreed. Hell, live OC was buggy iirc.
[Nexus S Android Development] alen1901:
Bedalus, 7.0.3 is super fast!! I tested with multitasking. opened about 10-15 apps and its so fast. Also animations in opening apps are smoother, no little hicups, just here and there, but much better than version before with 412mb.

Sent from SpeedMachine i9023
[Nexus S Android Development] treesurf:
Aha, I didn't see that, thanks! 109 hrs uptime on the previous extramem version, now upgrading.
[Nexus S Android Development] khaerkool:
how to flash it correctly . always get black screen after logo
[Nexus S Android Development] :
Been working on bfs today. Trying to make v0.424 work is a pain because it doesn't seem to exist in the 3.0.x mainline series.
[Nexus S Android Development] treesurf:
Sounds like you are flashing the wrong version for your ROM. Which ROM are you using?
[Nexus S Android Development] towelboy:
Bedalus, I think you made a mistake. v7.0.3 is the stable version :D. Everything is going good; YouTube, photosphere, video, temple run all work smoothly! Best of all I don't have to worry about low memory issues with 411mb!

(Even with no oc)
[Nexus S Android Development] leap_ahead:
I am the only one who cannot video recording on rasbean rom with 7.0.3 ???
[Nexus S Android Development] anshumandash:
7.0.3 on BB6. Everything is working fine including camera, video, gallery etc and its so smooth. Thanks Bedalus. :)

Sent from my Nexus S
[Nexus S Android Development] angeleo02:
Dude its working
[Nexus S Android Development] :
What model do you have?
[Nexus S Android Development] :
I think i have bfs latest version working. I'll upload soon so others can test.

Also mainline update is out.
[Nexus S Android Development] leap_ahead:
7.0.3 is 412Mb ram ..also 7.0.2 412mb ram and after videro recording i get Fc ,...so the RAM is the problem ...

408mb ram i dont have any problem ..
[Nexus S Android Development] anshumandash:
Yes, it's a ram problem. I am getting 411. May be that 1 mb is helping video recording on the ROM I am using.

Sent from my Nexus S
[Nexus S Android Development] deani77:
I remember people keep asking about CFS and BFS back in Matrix kernel ;)
[Nexus S Android Development] :
It gives a small performance advantage. It used to cause at least graphical glitches when I tried to benchmark it using Vellamo in ICS, and i thought it didn't seem as smooth in the user interface. However I'm using a more up to date version now, and it seems fine.
[Nexus S Android Development] rockerblood:
sir bedalus 7.02 nd 7.03 gives me 2 sudden reboot while browsing the net. i use the v7 stable then its all fine now, i still want the 7.0.3 on my Paranoid Android 2.54 :( any tips?

Sent from my Nexus S™ i9020A
[Nexus S Android Development] dwarf77:
I've used 6.7.10 on CM 10 nigthlies for about a week, no problems at all. Now I'm on CM 10 stable with 7.0.3. Everything's fine, even video recording with 4.2 camera. The Rom feels very smooth. Thanks bedalus!
[Nexus S Android Development] :
If you saw the google logo when your phone rebooted, then go to the OP and follow the links on how to help debug the kernel.
[Nexus S Android Development] :
Summary

BFS offers another 1% performance increase in CPU performance. Maybe more in other areas.

https://docs.google.com/spreadsheet/ccc?key=0AntDDKv-lS6IdDhjVWYyanhBODViSWhYWG03QldYcXc

Details

I finished merging The Brain **** Scheduler v0.424 by Con Kolivas. http://ck.kolivas.org/patches/3.0/3.4/3.4-ck3/patches/

I've done it by using Ezekeel's v0.413 patch, then painstakingly merging in the differences in the bfs code (which Con updated in July). Most of the changes worked fine, some didn't. This is because Con doesn't support the 3.0.x mainline kernel any more. So it's not a true v0.424 version, it's sort of a hybrid.

I'm testing it now, and it seems to work normally. The one problem I ever had with BFS was that it broke something in Vellamo benchmark app. However, this app seems to work fine, but it's been updated anyway, so I'm not sure if it is because of the updated app, or the updated BFS code.

When I've played with it for a couple of hours I'll share download links.
[Nexus S Android Development] khaerkool:
please how to flast the kernel correctly . flash it got blank screen after google logo :'( . im using cm10 stable
[Nexus S Android Development] dwarf77:
Go to recovery, wipe cache and dalvik, flash kernel, reboot.

_____________________________

Sent from my Nexus S i9023.
[Nexus S Android Development] kiko22:
did you download CM version of Marmite kernel?!
[Nexus S Android Development] rockerblood:
get the CM nightly column link, not the 4g and not the other rom..
[Nexus S Android Development] stojshic:
As said many times before, wiping is not nessesery when flashing kernel. Just flash kernel without any wipings...
[Nexus S Android Development] alen1901:
Only Fix permissions if you cant change gouverner or some kernel related settings.

Sent from SpeedMachine i9023
[Nexus S Android Development] gabling23:
I'm using my nexus s from 3 4 hours and now I noticed that I have almost 15min of kernel and partial wakelock..

I checked on better battery stats and the principal causes are: PowerManagerService, vbus_present, and connectivity service.. What are them?

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] ej8989:
What latest version still has blinking function in BLN?
[Nexus S Android Development] alen1901:
No blink, just lights on.

Sent from SpeedMachine i9023
[Nexus S Android Development] C4SCA:
i can ercord videos but when i stop recording "gallery force close", but then if i go back tothe gallery the video is there , so no problem

stock ota, v7.0.3 marmite
[Nexus S Android Development] ej8989:
yep so i was asking what was the last version that has bln blink
[Nexus S Android Development] treesurf:
Ok, for those having video problems here is how I fixed it :

Flash the camera from 4.2 and reboot. Now reboot into recovery again. Wipe cache, dalvik, fix permissions, and reboot. This fixed it for me, so you might as well try. :)

Sent from my Nexus S
[Nexus S Android Development] ziociccio:
i flashed v7.03 over paranoid rom. No proble,all's ok!
[Nexus S Android Development] :
v7.0.4 is out, download in the usual place. BFS: see my post earlier
[Nexus S Android Development] abhidoT38:
Thank you very much!! :D
[Nexus S Android Development] C4SCA:
i dont wanna bach but bfs wasnt created thinking about multicores or something like that? :s

i using 7.0.4 and my preformance is a bit worse and i get less 150 points on antutu (if that matters)

beside that i will stick with marmite!
[Nexus S Android Development] :
It was created as an alternative to the CFS task scheduler which works better on giant servers with 4096+ cores. It's designed to work better on desktops, embedded systems, mobile devices. I've already benchmarked the CPU performance, it's a 1% improvement (99.7% certainty / 3 standard deviations).

(quoted from http://ck.kolivas.org/patches/3.0/3.4/3.4-ck3/patches/3.4-sched-bfs-424.patch)
[Nexus S Android Development] :
http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.0.52

Lots of fixes for USB audio in this one
[Nexus S Android Development] :
v7.0.5 is here: http://goo.gl/HvUrp

-merge mainline v3.0.52

I'm mainly interested in whether the user experience is improved by BFS or not. Please feedback!

(BFS is also available in v7.0.4)
[Nexus S Android Development] ziociccio:
reboot after boot with v7.04 and v7.05 :crying:

(paranoidandroid rom,no oc,smartassv2)
[Nexus S Android Development] C4SCA:
flashed, booting...

---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------

no reboots yet...

i will make a antutu bench

---------- Post added at 04:03 PM ---------- Previous post was at 03:59 PM ----------

my antutu scores are back!

no issue with 7.0.5!

OC:1.2ghz

governor: smartassv2

BLN: enabled

STOCK OTA
[Nexus S Android Development] :
Can you get a last_kmsg?

My phone rebooted once with the first bfs version I installed, but with all the changes merged in (the one I uploaded) it's been working fine for 4.5 hours.
[Nexus S Android Development] dinos3:
SmartassV2 is stock governor?
[Nexus S Android Development] C4SCA:
Stock govetrnor is ondemand

sent from my old (but gold) Nexus S
[Nexus S Android Development] joeyddr:
Same here had to go back to 7.03 on slimbean 3.0 on ns4g
[Nexus S Android Development] dinos3:
OMG!!

Your kernel is awesome fast, and RAM managment is ubercool!

Now, i testing OC in Antutu, soon report :)
[Nexus S Android Development] jimdem:
Hi guys. Bedalus, i've got a problem. I've tried 7.0.5 but i had constant soft reboots that were then transformed to endless bootloops. I went to recovery and wiped cache/dalvik cache + fixed permissions. Then, it booted fine but in less than 1 minute i've had the same problem again. I'm back to 6.7.10 which i think is the best for me.

My config:

i9023, Aokp m1, default kernel values, no oc.
[Nexus S Android Development] capoooro:
I also tried wiping and fixing. The same for me. I haven't found lastkmsg. Going down to 7.0.3 that is fast and stable
[Nexus S Android Development] C4SCA:
Been on 7.0.5 for 3 h using the phone nonstop. ( youtube, music, facebook, messaging) oc to 1.2 on stock ota. No problems here

sent from my old (but gold) Nexus S
[Nexus S Android Development] atxbang56:
Is v7.0.5 bfs? and whatever the answer, how to check if it is cfs or bfs?

Sent from my pretty cool Nexus S

Phone : Google Nexus S i9023

ROM : MIUI 2.11.9 by MIUI France

Kernel : Marmite v7.0.5 by Bedalus @1096MHz
[Nexus S Android Development] C4SCA:
Its bfs cuz bedalus said so.... supposedly it will increase preformance

sent from my old (but gold) Nexus S
[Nexus S Android Development] sperelli:
Hi Bedalus,

I'm following the evolution of your work

in order to find possibly a solution to my big data problem, posted here: http://xdaforums.com/showpost.php?p=34054570&postcount=5330

Your advice for changing baseband didn't help.

Now question is: is there any chance to find a tweak/trick/solution such this

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

on our NS3s?

Or is there anyway to reset connectivity (data) to default values?
[Nexus S Android Development] :
I think for most people things need a shift of about 10% to be noticeably different. For example when you OC to 1.1GHz, you can notice a small improvement. But I reckon below that things disappear below some sort of perceptual noise floor. BFS provides such a small difference it shouldn't really be noticeable.

However, if it causes incompatibilities or other problems I'll revert it. It already looks like some people can't boot it for some reason.
[Nexus S Android Development] joeyddr:
Will you do a CFS version of 7.05? My phone reboots within a minute of boot up with bfs. I can't do anything before it happens
[Nexus S Android Development] polobunny:
Many 1% might eventually add up to 10% hopefully. :p

Really digging the test version you made me flash. Definitely good stable candidate, I'm at 65 hours and no signs of any problem whatsoever. Good thing that turned out to be v7 haha. :)
[Nexus S Android Development] benoit2600:
Hi bedalus, I've got a hard reboot during sending a sms.

I'm using the Slim bean V3.0 with the default kernel, and I overclock to 1096Mhz ( but the last_ksmg contain a backtrace )

http://pastebin.com/awsgsGJk

Edit : in fact, I've got 3 reboot like this, but I didn't save the last_ksmg of the other.
[Nexus S Android Development] polobunny:
I jinxed myself. Got a soft reboot just now. While updating apps from the play store. Uptime didn't get reset though.

Can't write much more though, typing one handed while giving blood for around 1 hour and a half. Haha
[Nexus S Android Development] caliban2:
So I leave the country for two days and you start removing RAM... Bah. :p

Just hit 101 hours with the setup from my sig, still no problems. (Didn't have internet, but I played a lot of NfS and used camera to excess)

After I read up on CM (came here first) I'll see if I continue upping current uptime or flash something new. Maybe BFS now agrees with my phone, it didn't in the past (freezes). How did you benchmark it, btw? BFS was always better for gaming and other heavy duty-stuff, but for normal multitasking CFS is the better choice. Is that where your 1% is coming from?
[Nexus S Android Development] dinos3:
Reboot on 1200, anybody have stable custom voltages for 1200?