yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] morfic:
I can benchmark/use up to 1.5.

I can run, not benchmark 1.6 when I run 1.6 with a slow bus.

Once 1.6 is slower than 1.5 on an overall system level, why bother?

So I leave 1.6ghz in the simms-zone, no need to punish him just because my silicon is not as good as his ;)

Many seem to think any amount of free speed is bad if someone else runs a higher clock speed then them.....sorry, then I am not your guy.

I am not designing the hardware from the ground up. I am squeezing out as much of the reserves designed into the chip as possible, while maintaining the highest amount of happy users.as possible.

I am trying to find a good middle ground on everything from clock speeds, voltages, gpu speeds, interactivity to boot logos noone complains about ;)

My next target is a UV-Vmax combo, the less individual builds there are, the more time I can shift from building the kernels to working on the source.

I have not yet released a kernel I couldn't run at full UV or up to 1.5ghz myself. Everything turning out to be lower results are differences in the chips, their assembly, age/quality/method of installs.

I would love to bring 1.6ghz to everyone, it just seems to not be a good effort/payout point.

Having said that, when building the UV kernel I made one version where nenamark showed the same fps as I can reach at 1.5 and 1.3ghz.

Again compromises, max cpu speed is cool if all we do is run linpack.

But we don't, so I aim at a overall "well rounded system".

I am thrilled to see how many enjoy it at so many different speeds, different roms.

To check messages in tapatalk and see thank yous amongst the concerns is pretty thrilling and it motivates me to make sure I can improve on the current version to make it more enjoyable for more people, even if it already works great for me.

Thank you for sharing in the fun of this phone, this kernel, with the rom of your choice.

Looking forward to making more of you lurkers and active users happy in the future.

Thanks,

Daniel

Sent from my Nexus S
[Nexus S Android Development] jlevy73:
Thanks Daniel. You've made owning my NS much more enjoyable and appreciate the time and effort of putting out so many updates. You do this for the love of it and have much respect for you and all the devs out there doing the same.

Now can you pretty please make me a Vmax CFS kernel :p
[Nexus S Android Development] morfic:
Ok mighty murph, you are just too cute.

BFS has been suspended for a few releases now, so all recent "su issue fixed kernels" are CFS.

<3

Sent from my Nexus S
[Nexus S Android Development] simms22:
mucho gracias amigo :D
[Nexus S Android Development] jlevy73:
Simms that little whore :p
[Nexus S Android Development] simms22:
priceless :p
[Nexus S Android Development] Jayrod1980:
To anyone with the browser and lockup issues associated with it, big props to burnfire for suggesting moving flash to SD. I don't know why it works but it really does. Now I can OC to whatever I have the guts to set and I don't have the browser lockups and drains and restarts that I was experiencing before with the recent morphic kernels. Thanks much burnfire. They need to integrate the thanks button on the xda app.

Morphic, do you have any idea why flash and browser would work when mover to SD but lock up without? Could the ext4 hack mount method used just not like my phone?
[Nexus S Android Development] morfic:
it's an interesting subject. Almost tempted to try to boot without the ext4 mount option added. Just to see if it relates, the fs certainly changes in this process.....

But I'm trying to squeeze out the UV v1.2 series right now. It's a neat kernel.

Anyone interested in the uv kernels planning on doing any heavy gaming? If not I think we'll want refresh of display lowered, less updates should translate into, less power consumed.

Sent from my Nexus S
[Nexus S Android Development] jlevy73:
I definitely do a lot of heavy gaming. Be interesting to see how a UV 1.2 would hold up to such conditions.
[Nexus S Android Development] kenvan19:
Bah...given my testing I've decided to come back to the trinity kernel. I find it odd that I can easily run Max at 1.6 but just setting my phone to 1.6 on VMax reboots me.
[Nexus S Android Development] simms22:
on vmax try this...

when you open set cpu, set the scaling to powersave before changing to 1.6ghz. then slowly move up to 1600.
[Nexus S Android Development] kenvan19:
Perhaps I should give it a shot when I'm at something more than 6% battery life lol...it went down to 100MHz and was painful to use. I'll give it a shot in the morning.
[Nexus S Android Development] morfic:
Vmax 1.1 or 1.2? Both?

Sent from my Nexus S
[Nexus S Android Development] kenvan19:
Didn't try 1.1 ill give it a shot in the morning when I have a little more battery life

Sent from my Darkginger CM7 Google Nexus S!
[Nexus S Android Development] alturismo:
after a browser freeze in the morning i just tested the flash external thingy

same issue again, so flash on external doesnt solve it here.

running cm7 1.22 v96
[Nexus S Android Development] morfic:
The experimental UV BB kernel is to see what people think.

Works for me quite nicely.

UV 800 and below, with a little extra GPU UNF at 1GHz for the 3D lover amongst us.
[Nexus S Android Development] morfic:
clear data after move yet?
[Nexus S Android Development] jlevy73:
My phone didn't like the experimental UV you just put up. It would FC and reboot on nenamark and hard froze each time I started dungeon hunters
[Nexus S Android Development] bananis:
i'm getting the same.

came run games and seems very unstable even at 1.0ghz.
[Nexus S Android Development] willverduzco:
And ironically, despite being the person who asked for it first and has probably bugged morfic the most for it, after the latest 1.2 vmax, I'm not so sure we need a CFS. :eek:

I'd still love to try out any CFS developments in the future, but 1.2 vmax is great for me. I've tried BFS kernels from different devs on many platforms and have never liked them for multitasking, but somehow, morfic's works well.

With 1.1 and 1.2 vmax, I can only stably reach 1.4. I can stay at 1.5 for about 30 seconds before it locks up and I have to hold down power for a minute / remove battery.

Also, thanks :)
[Nexus S Android Development] avetny:
:o thank you Daniel!!!!!!!!!!!!!!! know i understand everything !!!:o

Our phones without your trash :D and I am very glad that you are with us!!!;):o
[Nexus S Android Development] kenvan19:
No problems on the experimental. 2852 in quadrant so it's pretty damn smooth.

Also @morfic I was able to run at 1.6ghz on vmax 1.1 but it was still pretty unstable.

I'm going to run the experimental and see how it manages for a day. Some more benchmarks:

Neocore 48.7fps

Linpack 14.38mflops

Nenamark 45.7fps

SmartBench 1124/2681

Sent from my SubCyan CM7 Google Nexus S!
[Nexus S Android Development] kicknik:
Lag while playing megajump and apps opening up kinda slow on Max 1.2 clocked at 1200 something wrong...?
[Nexus S Android Development] AllGamer:
using the new kernels for the MAX series

how do we go about controlling the CPU speed for OC if we don't install SetCPU ?

because in the past, for each CPU speed level 1.2 Ghz, 1.3 Ghz, 1.4 Ghz, each of them were in a separate Kernel

so if i want to only run 1.3 Ghz with the MAX series, how do i go about setting that speed?
[Nexus S Android Development] simms22:
you dont. use setcpu or a similar app.
[Nexus S Android Development] sufibravo:
Don't be too disheartened by the negative reviews of the experimental UV kernel morfic. Running it now, multitasking with music and browsing with no hiccups thus far. Playing Asphalt HD is also surprisingly smoooth!! :D
[Nexus S Android Development] AllGamer:
>.< ... hmm.. not exactly what i wanted to hear.

oh well... guess i'll have to re-install that again then
[Nexus S Android Development] alexis_p3300:
Just finished testing all kernels on r10 conclusion faster 1.5b stability 8/10 vmax stable up to 1.4 stability 9/10 max stable up to 1.2 my choice 1.3v2 excellent performance stability 10/10 great work morfic
[Nexus S Android Development] jlevy73:
Something I didn't realize until simms pointed it out to me is that 1.2Vmax is a CFS kernel :)
[Nexus S Android Development] morfic:
Thanks, long day today, left house at 5am, left work at 7pm, little use but usual 30 minute lunchtime screen on use. 65% after 14 hours is best I got thus far. Considering data comes and goes out there in the sticks.

When I check the number of downloads compared to the few complaints, it's a nice ratio.

But even simms' god phone likes oc more than uv :)

I like a 1ghz kernel getting same nenamark score as it's 1.4ghz sister ;)

Thanks for the feedback,

Daniel

Sent from my Nexus S
[Nexus S Android Development] jlevy73:
I loved the uv kernel right up until the time it crashed murph's phone :p

Too bad it wasn't stable for me because it was fast as hell.
[Nexus S Android Development] morfic:
I use sl4a, if it works for you, you soon have icons to custom shortcuts running the scripts, to go from "profile" to profile in a tap.

Basically a nice shell/script environment.

If you are interested, I send you some (really tiny) scripts to see what I do with it.(max clock, min clock, governor changes)

But you can add perl and bean shell stuff to even do gui dialogs through it.

I like that nothing runs when the scripts exit. I like idea of "no payload" of this.

I am using setcpu right now, so I have it for testing'

Sent from my Nexus S
[Nexus S Android Development] Jayrod1980:
I've tried out the UV kernel. I ran quadrant and the phone rebooted. After that, quadrant did fine. Scored a 2850 on one of the runs. Smartbench crashed once but didn't reboot. Managed to run it again but productivity index was like 971 but games was pretty high. Everything else so far seems to run alright. Data takes awhile to sync up when I start the phone as well but webpages load up fine. Every since I moved flash to SD the phone seems to work with any of morphics kernels. Great work. I love overclocking but can't wait till a stable UV kernel is done. Any chance having a nice 1.2 UV kernel in the works? What i miss most about the bionix Roms on the vibrant were the mildly overclocked kernels that had excellent battery life. These kernels aren't bad, I'm getting about a 5% or a little more drain every 7 or 8 hours. On the bionixs 2.1 roms I was getting only a few percent drop overnight. Maybe too much an apple to orange comparison since the hardware isn't exactly the same and its a different version of android but those Roms and kernel combined drastically changed the battery life of the vibrant.
[Nexus S Android Development] morfic:
Core was a fun kernel, to stabilize things I have to raise voltages sooner the higher we go.

I think up to 1.3 ghz we could build a fun kernel. Run 100mhz to 800 mhz as UV, 1ghz stock freq/bus/volts. Then 1.2/1.3 slightly raised until stable for majority of people.

That's my idea of a perfect kernel.

Safes battery and is faster.

Just so easy to get off track when everyone wants 1.6 :)

Source......i am waiting to see that materialize for vibrant and 2.2 :/

Sent from my Nexus S
[Nexus S Android Development] willverduzco:
Sorry, but I feel dumb right now. It's actually CFS? That would explain why it works SO much better for me than 1.1 did. The main page still says BFS...

Edit: I just rechecked the main page, and apparently it doesn't say BFS or CFS. I was wondering if morfic could chime in?
[Nexus S Android Development] jlevy73:
Yeah it's really CFS. I became a little suspect when I wasn't having su issues then simms confirmed it with me later that night as I was too dense to figure it out myself. I think morfic snuck it in there to see who would notice.
[Nexus S Android Development] jlevy73:
See post #1535 :)
[Nexus S Android Development] sufibravo:
All I have to say is truuuuee dat!!!
[Nexus S Android Development] avetny:
I hope Vmax 1.3 gonna run 1.4ghz stable like befor.....other wise I'm gonna change my phone :(

(Btw even reboot with 1.3ghz on vmax 1.2)
[Nexus S Android Development] willverduzco:
Gotcha. Thanks for the clarification. My not-so-perceptive self is very appreciative.

Perfect kernel for me... Now I know why, lol.

Sent from my Nexus S
[Nexus S Android Development] kenvan19:
Still using the experimental UV kernel and its working great. Haven't had a single FC or random reboot. I'll probably switch back to one of the OC kernels tomorrow though because I'm having dinner with my family this weekend and my sister's boyfriend will be there and he thinks his Droid X is the bomb. I want to show him just how pathetic it is in comparison to a real piece of hardware =D

Oh thought I'd mention that regardless of following the BT fix procedure, my BT is still broken.
[Nexus S Android Development] dario3040:
You better show him what real hardware is >;)
[Nexus S Android Development] willcpfc:
Trying the bb experimental kernel now. Loving your work morfic, keeping me in zip installs :)
[Nexus S Android Development] dario3040:
For me the BB reboots once i unlock it and type the pincode.

But at least it seemed fast x]
[Nexus S Android Development] gadjet:
Great addition to my Cyanogen ROM-Thank You!

I have installed the cyanogen nightly build 35 first, then installed ROM Manager premium, then stuck the Team Whiskey Trinity-Max-CM7-1.1 on top..phew it flies.

When a new cyanogen nightly update comes out will I need to re flash Trinity-Max-CM7-1.1 again?

Thanks in advance..:)
[Nexus S Android Development] simms22:
yea. youll need to reflash it(kernel) after every rom update. the rom overwrites the kernel with its "stock" kernel.
[Nexus S Android Development] gadjet:
Great cheers for that simms22.
[Nexus S Android Development] willcpfc:
Liking this new kernel! Very stable and absolutely no browser hangs which I had with all other ones I have tried. Impressed :)
[Nexus S Android Development] MaliceOmega:
1.3 ghz working beautifully. morphic says that BT fix is coming soon :D
[Nexus S Android Development] teledude:
3450 in quadrant

49 fps in nenamark1

48.7 in neocore (limited i think?!)

Super smooth and stable - can we have 1.4 or 1.5 asap please :D
[Nexus S Android Development] irishrally:
Is everyone comfortable with the voltages being used? Should one feel comfortable running the phone at 1.3GHz all the time?
[Nexus S Android Development] Tyruiop:
Hello,

As far as I am concerned, I use SetCPU and only allow OC under certain conditions (a limit of 800Mhz is set otherway).

Great build, looks stable for the moment, thank you !
[Nexus S Android Development] FaithCry:
did anyone else get a bootloop when they flashed it?

i am supposed to flash it right after the rom or is anytime fine? because when i flashed it a couple days after running bionix, i got a bootloop =\
[Nexus S Android Development] Michigan Jason:
ut ohh...

I had the version 1.3, running at 1.3 all time, and it was running, then all the sudden i noticed the phone was off. I had to pull the battery to get it to turn back on. Turned it back on, and right after booting it did the same thing. Guess I will have to go back to the working version. Anyone else had this happen?
[Nexus S Android Development] willverduzco:
Does anyone even know what the voltages are at all speeds? Last I remember, morfic said that he was running 1.3 GHz at 1.35V.

Morfic, I was wondering if you could tell us what voltages you used for 100, 200, 400, 800, and 1000 MHz and how they compare to the stock voltages? Thanks!

The reason I'm trying to figure this out is that I'm trying to determine what to set my minimum speed to in SetCPU. On my Nexus One, running the wildmonks AVS kernel, 422 MHz used just as little power as at 128 MHz (950mV), and this helped responsiveness greatly when set as the minimum frequency. In fact, with that used as the minimum frequency, ADW Launcher EX actually ran smoother on my N1 than my NS.
[Nexus S Android Development] unremarked:
Running great on 1.3ghz, seems very stable thus far.
[Nexus S Android Development] jroid:
Wow. I don't care much about benchmarks, but I just got 18.36 consistent in linpack and 3222 in quadrant running the 1.3 trinity

:eek:

Sent from my Nexus S
[Nexus S Android Development] irishrally:
Holy crap I just flashed the 1.3ghz kernel and my phone exploded ...

... exploded into awesomeness!!!!
[Nexus S Android Development] SS2006:
can I flash the 1.3 zip on stock gingerbread 2.3.1
[Nexus S Android Development] nezek:
Request....

Can Someone Please Upload an 1.3Ghz Upscale ScreenShot?
[Nexus S Android Development] DebauchedSloth:
Awesome work!

Any chance you could publish those source patches?
[Nexus S Android Development] irishrally:
I don't know for sure but the the first kernel before bionix was for the stock ROM. It works on MCR r3. You could nandroid backup and flash it to see. If it doesn't work just recover your backup. No harm done.

What exactly are you looking for?
[Nexus S Android Development] Doug8796:
To op: could u make an 65fps galaxy s (captivate fix) ? I will glady paypal you if possible.
[Nexus S Android Development] morfic:
If you give me a second, i can make one.
[Nexus S Android Development] deez1234:
another great release! morfic, your the man. talk to you later in the underground lair...
[Nexus S Android Development] morfic:
http://db.tt/65o8zMG

For those willing to confirm it works on a stockrom

If it gets confirmed, i can move it to the OP or its own thread.

Need to run do some stuff else i'd confirm.

Whoever tries this and has Quadrant Advanced, what's your IO score on this?

I am hopeful this scores close to Bionix NS1 even without the files in /system/etc/init.d/
[Nexus S Android Development] hkoutso:
Really would like to try your kernel over stock 2.3.1 to contribute on the stability front (as I am still watching the scene and I am pretty satisfied with the stock kernel at the moment).

Kudos for your work ;)
[Nexus S Android Development] hkoutso:
wow stock kernel posted while I was typing.

Thanx morfic.

EDIT:

Just flashed the kernel on stock 2.3.1 through recovery but stuck in the boot logo. Have to remove the battery to reboot.
[Nexus S Android Development] morfic:
There will be other things I will do before vmax 1.3.

But I think I will make a oldschool trinity13 and trinity15 also.

Now where there is a sleep fix and voodoo-sound it'll be worthwhile to have a redo.

Sent from my Nexus S
[Nexus S Android Development] simms22:
very nice! old school trinity16 with voodoo also? pleeeeeease ;)
[Nexus S Android Development] avetny:
Yeaaaaahooo ;-) thank u for good news! U best:p
[Nexus S Android Development] jlevy73:
Lol, it's a good day when 15 just isn't enough.
[Nexus S Android Development] G1_Lucky:
GREAT JOB

Looooove the kernel morfic, the only one I use! :)

Thanks for all that you have done.

Guys I'm looking for 1 or 2 GOOD graphic designers for a HUGE android theme for the Nexus S! If interested send me a PM
[Nexus S Android Development] kenvan19:
I'd be interested in testing. I'm a failure at Photoshop. Lol

Sent from my SubCyan CM7 Google Nexus S!
[Nexus S Android Development] G1_Lucky:
Lol I'll keep your name in mind! Just to give you a little preview. Its going to be a group of people hopefully maybe like team-douche and we can perfect the theme, make a sick website! And then work on the next one lol :P

Only time will tell! :) I love this community
[Nexus S Android Development] sloppy1:
running the uv kernel running very well for me ,,,thx,,,,if you could do a 1.2 uv with voodoo mmmmmmm ONE WORD ,,,,XMAS TIME
[Nexus S Android Development] simms22:
two words :p
[Nexus S Android Development] alexis_p3300:
Can't wait for 1.5 old school version!!
[Nexus S Android Development] dario3040:
What about:

1.7 GHz very high voltage.

Voodoo-sound

Sleep-fix.

Undervolt under 1 GHz.

and 50 MHz steps like: 1GHz, 1.05Ghz, 1.1 Ghz

That would be awesome :rolleyes:
[Nexus S Android Development] simms22:
ive gotten it to boot and run for 25 seconds max, at 1.7ghz. it freezes when i open any application :eek:
[Nexus S Android Development] dario3040:
What kernel is that?

Probably won't even boot on mine.

But it might be worth a try :rolleyes:
[Nexus S Android Development] simms22:
it was just a test kernel to see if 1.7ghz would boot.
[Nexus S Android Development] dario3040:
where do you even get those kernels? xD
[Nexus S Android Development] bratfink:
Happy Me

I think i have one gifted Sexus S, because i can stay at 1.6GHz for days with the Trin-Max kernel (not VMax) and dont have a single tiny little problem!! I think i might even beat u simms :P!
[Nexus S Android Development] avetny:
tern on music

tern on live wallpaper

go to browser (xda samsung nexus s) play 5-7 min....

surprise !
[Nexus S Android Development] morfic:
Get started on it, looking forward to testing it.

Sent from my Nexus S
[Nexus S Android Development] morfic:
http://db.tt/nRtSufA this WILL destroy murphic phones

Sent from my Nexus S
[Nexus S Android Development] simms22:
haha.. i didnt want to post it. i didnt want to be responsible for the epidemic of fried phones that will occur ;)
[Nexus S Android Development] jlevy73:
LMAO, priceless
[Nexus S Android Development] jlevy73:
Woot, it boots perfectly. How come I can't make phone calls though :p
[Nexus S Android Development] kenvan19:
Running fine here. No service though was the call thing serious lol

Sent from my Onyx CM7 Google Nexus S!
[Nexus S Android Development] morfic:
Luckily there are not that many murphic phones.

Sent from my Nexus S
[Nexus S Android Development] kenvan19:
Scratch that. Setcpu kicked in ans I went on a bootloop lol
[Nexus S Android Development] morfic:
And yes they all boot and run a flawless 1ghz.....but you knew that.

Sent from my Nexus S
[Nexus S Android Development] simms22:
fresh screenshot trinity17. it runs great at 1700/1400(or lower), even makes phone calls :p but at 1700/1700 all i get is about 25 seconds before it freezes.
[Nexus S Android Development] jlevy73:
Is it stable enough to bench @1700/1400?
[Nexus S Android Development] simms22:
trinity17 1700/1400

1950 quad

37.7fps nenamark

19500 an3d
[Nexus S Android Development] antiochasylum:
Thats pretty low. My tab does 2300 @ 1.4 in quad. Something isnt rite with those numbers.
[Nexus S Android Development] simms22:
this kernel wasnt meant to perform. it wasnt even meant to run. it was just a proof of concept that 1.7ghz could boot.

we have the 1.6 and 1.5ghz kernels for performance :D

1600/1600
[Nexus S Android Development] irishrally:
"Don't Fu*k with the Jesus"
[Nexus S Android Development] dario3040:
xD I don't think I can do that o.o
[Nexus S Android Development] kicknik:
So im gonna be returning my nexus s and getting a new one cuz of a cracked screen and i have warranty.

So how can i make sure to get my nexus to run at the highest speed possible. Does it actually help to slowly move it up like 1.0 to 1.2 1.4 1.6 or is it already decided in the beginning just if im lucky enough to get a simms-esque nexus s?

thanks :]
[Nexus S Android Development] simms22:
luck i think.
[Nexus S Android Development] kicknik:
Hmm so u just went striaght to 1.6?
[Nexus S Android Development] simms22:
i went from 1.4 to 1.5 to 1.6. but i dont think that makes a difference. if 1.6 was available, i would have gone straight to it. there are just to many variables involved, thats why i think its luck.
[Nexus S Android Development] KnightMAREcrow:
Deleted, answered by email with morfic
[Nexus S Android Development] jboy15:
howz the battery life on this?!?!

any help.. im new to nexus s .
[Nexus S Android Development] kid1da:
Depending on usage your battery life can be different from others. I've gotten plus 12 hours using the vmax 1.2 for cm7. Its a good kernal.
[Nexus S Android Development] fabio008:
Worked for me. Just place the .zip in the SD folder and boot into the clockwork recovery (after flashing it). Then choose the install from zip option and just find the file.
[Nexus S Android Development] dario3040:
The latest version is trinity max voltage 1.2. But the 1.1 can be used on stock roms
[Nexus S Android Development] slowz3r:
This may be something very niche, maybe its unrelated but ever since using Vmax on my NS, my battlenet authenticator app doesnt wanna work :(