yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] simms22:
try it this way. boot into recovery, make a backup, do not wipe cache, do not wipe dalvik, flash nightly #12, flash gapps, flash trinity14b 3.0cm7.
[Nexus S Android Development] jlevy73:
What's also worked for me is to go into recovery and flash cm7, gapps then reboot the phone. After the phone reboots go back into recovery and flash the kernel.
[Nexus S Android Development] LordPhong:
Gtfooh, I can't believe that worked. Funny that I tried the same thing with cm build 8 and it didn't go too well. Anyway, it's working great so far. Thanks jlevy73.
[Nexus S Android Development] simms22:
i should change that to flash nightly #13 since it just hit ;)
[Nexus S Android Development] LordPhong:
I used build 13.
[Nexus S Android Development] simms22:
any luck??
[Nexus S Android Development] jlevy73:
14b keeps on going ;)
[Nexus S Android Development] simms22:
yup! im still using it too :)
[Nexus S Android Development] LordPhong:
For a while my phone was hot but using on demand with setcpu cooled it down.

Smartbench was higher with bionix, though.
[Nexus S Android Development] simms22:
heres a special treat from morphic http://goo.gl/B0hdB

its the Trinity15b v1.1 cm7 kernel. overclocked to 1.5ghz and compatible with CM7.

make a backup before flashing!
[Nexus S Android Development] avetny:
Yeaaaaaaaaaaaaaaaaaaa!!!!! Today is a good day :D
[Nexus S Android Development] avetny:
i got 4134 !!!!!!!!!!!!!!!!!!!!!!!!haahahaha
[Nexus S Android Development] wuyanks:
good news: this kernel works on my phone, while the 1.4 didn't... does that make sense? did you tweak the voltage or anything?

edit: had my first reboot, 15 minutes in.... maybe not as stable as I had hoped.
[Nexus S Android Development] rb9228:
Could I flash this over 14b? Or do I have to flash everything all over again?

Update: I went ahead and flashed over 13b without wiping data or cache. Seems to be running ok.
[Nexus S Android Development] avetny:
wuyanks- "edit: had my first reboot, 15 minutes in.... maybe not as stable as I had hoped"

it's ok dude: Sometimes it seems that you open the CPU one step above....give him the maximum load on the processor, with intermittently (it stops laggy)....... as 1.6 will be soon
[Nexus S Android Development] avetny:
just flash over 1.4b...don't worry...
[Nexus S Android Development] Guitarfreak26:
Mine often freezes on then reboots, it did this on 1.4 and 1.5 :(

Is that because my phones crap? lolll!
[Nexus S Android Development] rb9228:
I noticed that when I flash Trinity, under About phone, the Mod version becomes 'Unknown' and CM7 nightly version is gone. Anyone else experience the same?
[Nexus S Android Development] simms22:
thats because its edits your build.prop file, puts the trinity info there. morphic hasnt updated that part. if you like you can edit your build.prop to say anything you want.
[Nexus S Android Development] tempera:
I'm on 1.5 but the quadrant results are lower than 1.3!! I get 3400 on 1.3 but on 1.5 Max I got is 2600?

WHAT THE HELL?
[Nexus S Android Development] avetny:
yeaaaa man u right !!!!!!! im gonna try !!!
[Nexus S Android Development] simms22:
check this out :D
[Nexus S Android Development] tempera:
Tests are still under 2600 running 1.5? Whats happening? I've had no reboots or anything yet running for few hours but quadrant is low.
[Nexus S Android Development] dario3040:
Title ^^

When will you post the source code?
[Nexus S Android Development] simms22:
try just rebooting.
[Nexus S Android Development] Guitarfreak26:
Jealous of all you guys who have working kernels... mine stopped after 1.3
[Nexus S Android Development] kenvan19:
Does you phone feel slow? If not, quadrant doesn't matter. If your phone feels fast then scores don't mean s***.
[Nexus S Android Development] tempera:
No the phone is super fast man! Oh on smartbench I got 4300+!!!
[Nexus S Android Development] avetny:
dude sell you phone......and buy another one nexus s
[Nexus S Android Development] avetny:
i try to open Build.prop from phone, it opening i put everywhere 2.3.2

and when i press save, it's saved but i opening again and there same numbers 2.3.1 why?

(droid explorer on PC gives same think)
[Nexus S Android Development] simms22:
need to reboot for changes to take effect.
[Nexus S Android Development] avetny:
i believe i did it...but i will try again....THANK YOU...

did u do from ASTRO app?
[Nexus S Android Development] jlevy73:
Just use root explorer, change r/w to r/o go into build.prop as text editor, make the changes you want, save, change r/o back to r/w then reboot.
[Nexus S Android Development] avetny:
thank you my friend
[Nexus S Android Development] simms22:
root explorer
[Nexus S Android Development] avetny:
btw root explorer MUCH MUCH better than ASTRO !!!!!!
[Nexus S Android Development] morfic:
Guess it's time to remove all links to 2.3.1 kernels. Then there won't be build.prop woes.

Going to halt all releases until a patch to source is available, not that I actually write code, I only edit numbers......but gotta comply, right? Like everyone else on xda, right?

Sent from my Nexus S
[Nexus S Android Development] avetny:
People go to settings>>>about phone>>>clickit 5-6 times to "android version" = wtf is that??? Illuminati??? Android one of the:eek:m

_______________________________________________update

Jack Larson - it's Illuminati too.....

http://lucifervicarious.blogspot.com/
[Nexus S Android Development] willcpfc:
That's done my head in a bit :eek: the truth is out there....
[Nexus S Android Development] morfic:
Scares them. Anyway, I think I can take care of what I have to better another way anyway.

Sent from my Nexus S
[Nexus S Android Development] avetny:
kill them all
[Nexus S Android Development] avetny:
mr President !!!! GLAD to see u online !!!

:) do u gonna make us more happy today :D ???
[Nexus S Android Development] Guitarfreak26:
Lol couldn't be guaranteed to have a working one again though could I
[Nexus S Android Development] avetny:
People go to settings>>>about phone>>>clickit 5-6 times to "android version" = wtf is that??? Illuminati??? Android one of them

_______________________________________________upd ate

Jack Larson - it's Illuminati too.....

http://lucifervicarious.blogspot.com/

output: The terrorists are NOT who you think they are:

Secret Service / `SS` create the terror, to bring in the new world order - 9/11 WAS AN INSIDE JOB - NO TO GLOBAL DICTATORSHIP !

http://pacsteam.pt.vu/
[Nexus S Android Development] simms22:
unfortunately, thats old news. its a hidden surprise commonly known as an "easter egg" :D
[Nexus S Android Development] avetny:
u wanna fresh ??? http://pacsteam.pt.vu/
[Nexus S Android Development] avetny:
Why the Tegra2 shouldn't keep you from the Nexus S.

FROM "

Anderdroid"

http://smartphonebenchmarks.com/foru...arm-cortex-a9/

I'm sick of hearing people cry omg Tegra2 awesome. NO. It's great, but it's not going to make the Hummingbird obsolete. The Hummingbird has a better GPU. Balance it out and you get unnoticeable performance gains from a Tegra2. Not to mention the Tegra2 phones are coming out with Froyo which simply put doesn't have dual core optimizations, so in the end, it might even be SLOWER than the Nexus S.

What you should be waiting for is the Snapdragon and OMAP dual cores as well as the Orion. But these won't be out for a while, so why not get the Nexus S?

It's either or in this case. Don't choose a Tegra2 phone because it's a Tegra2. Choose it because it is the right phone you want, that will get upgades when you want, and is on the right carrier you want. Get a Tegra2 or a Hummingbird, that's all I have to say. They're about equal.

Just sick of the overpraise that the Tegra2 gets when we already have that power in the Nexus S.

Quote:

NVIDIA - they went from ARM11 (Tegra 1) to Cortex A9 (Tegra 2), skipping Cortex A8 design altogether. Tegra 2's CPU core will be competitive but its GPU appears to be weaker than even PowerVR SGX540. Heck, even Qualcomm's Adreno 205 may outperform this GPU. On the plus side, Tegra 2 is already available on the market NOW, and smartphones based on Tegra 2 will appear during Q4 of 2010. (Read this article for more details on Tegra 2). Samsung, LG and Motorola have announced their intention of producing phones based on Tegra 2 so far.

Power SGX540 = Hummingbird.

By no means am I saying to not get a Tegra2. All I'm saying is to not avoid the Hummingbird because you think the Tegra2 is that much better or something.

__________________

Look for quake3droid and quake2droid on the market!

Samsung Nexus S [T-Mobile]

Samsung Vibrant [Simple Mobile]

Motorola Droid X, HTC Magic, HTC G1, HTC Nexus One, Motorola Droid, Samsung Focus, iPod Touch 3g, iPod Touch 4g, iPad
[Nexus S Android Development] morfic:
Impossible, if I have time, it'll be spent on publishing my meager changes to samsung's published code.

I'll be looking forward to the resulting works by people who really just need the s5pc110 PDF here on xda and change a couple of numbers and compile it.....yet don't thus far........

Sent from my Nexus S
[Nexus S Android Development] jlevy73:
So no chance you'll make a CFS kernel?
[Nexus S Android Development] morfic:
You misread that, I built one yesterday, but was testing it still when I got the gpl source request from xda.

So I figured I won't release anything until after I have the patch up. Not worth getting in trouble over nothing......

Just a little delay, not sure when I'll be back at the PC. Then patch will go up, then cfs version can be released.

Sent from my Nexus S
[Nexus S Android Development] jlevy73:
Great, thanks.
[Nexus S Android Development] morfic:
Still don't see the fascination :)

But easy enough to patch -R bfs.

Aside, soon you build your own cfs kernel ;)

Sent from my Nexus S
[Nexus S Android Development] morfic:
Ever check the Nenamark result page? Too bad they sort by avg. Otherwise our 63.x fps would look better ;)

Sent from my Nexus S
[Nexus S Android Development] jlevy73:
Well I appreciate you satisfying my intellectual curiosity. With the snapdragon chip there was a noticeable difference between CFS and BFS. Maybe the same is not true with the hummingbird, but I'd like to try anyway.
[Nexus S Android Development] morfic:
NP, it's not a big request, I just like to understand. Requests for tun or cifs or higher voltages are easier to comprehend.

Sent from my Nexus S
[Nexus S Android Development] DroidRC1:
Build 14 nightly didn't boot with this kernel v15 for me..
[Nexus S Android Development] morfic:
http://db.tt/9k0jQ9F

"This" kernel?

And has it worked with previous nightlies for you?

Sent from my Nexus S
[Nexus S Android Development] morfic:
Guess it's time for a new ramdisk.

Sent from my Nexus S
[Nexus S Android Development] jlevy73:
Didn't work for me, and 1.5 worked lovely on the last nightly.
[Nexus S Android Development] jlevy73:
Another question/request. I know the NS shipped with kernel version 35.7 but there are more recent stable kernel versions that would provide added benefit. Maybe when you have time you can look at that as 2.6.37 is the latest stable kernel

http://www.kernel.org/
[Nexus S Android Development] morfic:
Boy....that's insulting

Sent from my Nexus S
[Nexus S Android Development] jlevy73:
You're kidding right?
[Nexus S Android Development] simms22:
the trinity15bv1.1cm7 kernel booted here after two tries and is running smooth. this is what i did...

1st try i did the normal - backup, flashed cm7 nightly #14, flashed gapps, flashed kernel. results - it went through the process of booting, but never did. just sat on the cm7 boot animation. no bootloop. so i restored my backup and booted up. next i went to the recovery, flashed the rom, then the gapps and booted. then i went back to the recovery and i flashed the trinity15v1.1cm7 kernel and it booted.
[Nexus S Android Development] morfic:
Half :) I still can't believe you linked me to kernel.org

Not sure whether to laugh or cry.

Sent from my Nexus S
[Nexus S Android Development] simms22:
new quadrant benchmark with cm7 nightly 14 and the trinity15bCM7 kernel
[Nexus S Android Development] jlevy73:
Wowzer, next stop, 5000 on Quadrant

Edit: I wonder what the record is for Quadrant. That has to be up there.
[Nexus S Android Development] morfic:
Cleaned up OP, kernel flashes and works fine on Bionix NS1.

Increased/changed voltages hopefully this makes other phones more stable.

Hoping the topic change is not throwing too many people for a loop.
[Nexus S Android Development] morfic:
Not at 1.4V yet, adjusted other voltages throughout, no effect on battery life i can *notice*

still stable for me

figured having a .zip makes things easier for people

reason it is for Bionix NS1, because that's what i run.

it should run on stock though

however the remounts are contained in the rom, so you would have to do the remounts in a file in /system/etc/init.d/

the build.prop i copied over when the max event edit didn't take and i got 48fps instead of 65fps. with the included build.prop, 65fps are back
[Nexus S Android Development] mortzz:
It won't boot on the stock rom for me, trying it on Bionix.
[Nexus S Android Development] unremarked:
Confirming kernel works great on Bionix! Wifi works, bluetooth works(NVM), no issues at all(NVM) and it's completely stable for me. :)

EDIT: Spoke too soon. Bluetooth will not turn on.
[Nexus S Android Development] mortzz:
Flashed Bionix and then your update.zip. I'm now running at 1.2GHz 100% stable so far! I'm only getting 48.7FPS in Neocore though. I pushed a build.prop that includes

windowsmgr.max_events_per_sec=68

too.
[Nexus S Android Development] Anderdroid:
Just don't bail on stock for Bionix! Plz support both ;)
[Nexus S Android Development] mortzz:
Bionix is mostly stock anyway. Most of the changes are under the hood.
[Nexus S Android Development] Greenarcher707:
Using stock ROM, looking good so far.
[Nexus S Android Development] morfic:
push the build.prop in the .zip
[Nexus S Android Development] morfic:
it should work on stock, proof: greenarcher
[Nexus S Android Development] mortzz:
No dice. Still capped out at 48.7FPS.

It wouldn't even get past the Google splash screen for me.
[Nexus S Android Development] morfic:
Don't use it for a while so it has a chance to cool down. Make sure to switch back to ondemand governor.

then when it is nice and cool, switch back to performance governor and run the benchmarks.

try to do it on a full charge

trying to chase this one down might be more fun than the BT one

Happy New Year
[Nexus S Android Development] mortzz:
I let it get down to 22c, set it to 2200/100 performance, and ran it again. 65FPS in Neocore, 53.9 in nenamark.

Nicely done!
[Nexus S Android Development] c_licious:
I'm only getting 48.7fps in Neocore. What am I doing wrong?
[Nexus S Android Development] 651stp:
ty morfic trying now...! i'll see if BT is working.
[Nexus S Android Development] mortzz:
Read what morfic wrote.

Push the build.prop from the zip to /system/ reboot, make sure the phone isn't too warm, set the governor in SetCPU to performance and make sure the max is set to 1200MHz and benchmark away.
[Nexus S Android Development] 651stp:
Confirmed: Bluetooth Doesnt Work With This Kernel
[Nexus S Android Development] RinTinTigger:
Bluetooth doesnt work, but the kernel works fine on the MoDaCo r3 custom rom.

Cam works fine,shutter sound is gone :)

Wifi works fine!

OC works fine!
[Nexus S Android Development] mortzz:
If I set the clockspeed lower than 1000MHz in SetCPU it almost always crashes.
[Nexus S Android Development] ranxoren:
So I have a quick question, I flashed this over the Bionix NS rom and the process went fine. Now, how do I know im OC at 1.2ghz ? Does flashing this automatically bring me up to that clock speed or should I use SetCPU ?

Thanks!
[Nexus S Android Development] asci:
It worked for me too!

Edit1: my device rebooted while performing Quadrant...

Edit2: I was able to complete Quadrant and it scored 3485

Edit3: very unstable indeed...I had a freezing&reboot while scrolling screens...

Edit4: second reboot in few mins while playing in the market...

OK tested. Reverting back to NAND backup...it was fine to complete the boot process but the device is unusable...
[Nexus S Android Development] simms22:
im on my second day using this trinity15bv1.1 kernel, not a single reboot yet. not even after like what seemed like 50 quadrants in a row with setcpu set to 1500 high/1500 low. maybe youre holding it wrong ;) normally ive been using the kernel with setcpu set at 1000 high/100 low ondemand, but set it higher when needed.
[Nexus S Android Development] irishrally:
You dirty Quadrant whore! I'm assuming you're a dude and this isn't really offensive.
[Nexus S Android Development] avetny:
people i just wanna ask you something ! ;) :confused:

:Dif I will change in build.prop "lcd_res=180" whats gonna be ? i will not crack the phone? (i got CM)....

because long time ago some one change on stock rom lcd dens to 180 and phone was got in deep black screen :eek::D

i dont wanna use app's.

Thank you for help, and answers !!;)
[Nexus S Android Development] simms22:
im a dude... and a dirty quadrant whore(that probably stems from being a crackflasher looking for a fix ;) )
[Nexus S Android Development] morfic:
You can say what you want about benchmarks, they get the CPU/system warm. Use a variety of tests, so it serves as a proof of "this phone can do more than just boot up with this kernel."

A spread of linpack, quadrant and Nenamark gave a nice idea about the system overall. I admit 0xbench is a nice addition.

A single top score means nothing if adw ex wasn't smooth as silk ;)

Quadrant needs to get updated, so people stop being confused about our 0 scores for 3D. Although not sure they are ready to add a minimum of 200 to simms' scores....

Sent from my Nexus S
[Nexus S Android Development] irishrally:
haha, keep going buddy, you'll hit that 4200 mark eventually ;) *Waits for Simms to load his 4500 screen shot*

Thanks again for digging me out of deep seeded depression when I thought my NS couldn't handle more than 1.3Ghz.
[Nexus S Android Development] avetny:
bro what are u think if i gonna change LCD density 180:o in build.prop???

is gonna work?;)
[Nexus S Android Development] jlevy73:
For those having a tough time booting try this. Do a full wipe, then flash just cm7 + gapps. Let it fully boot up. Go back into recovery (don't wipe anything) and flash the kernel.

I agree Quadrant is just one benchmark and it really needs an update. Another good one besides nenamark, neocore, smartbench, is called GPUbench.

1.5ghz on top of cm7 is quite stable for me, although I run it @ 1000/100 for daily use.
[Nexus S Android Development] irishrally:
I am only familiar with the LCD Density app that I have used successfully before (on the Nexus One). I assume the app just changes the build.prop for you but I am completely guessing. If you back up before trying the change to 180 then you should be fine. This is all speculation on my part though. Sorry I can't be of more help.

EDIT: Maybe you could email the developer of the LCD Density app. I'm sure he could fill you in on how it works and how to make the change without the app for power users.
[Nexus S Android Development] avetny:
:) ok thank you :)
[Nexus S Android Development] jlevy73:
I wonder what needs tweaking in order to get BT working with this. I compared to 1.4 and 1.5 this morning and the CFS feels much smoother than the higher clocked BFS versions.
[Nexus S Android Development] simms22:
i like posting quadrants because it has "shock" value, and people like seeing them. but in reality, for actual benchmarking i use 0xbench. it gives great detailed reports on many different benchmark tests. giving me more of a real feel of whats going in with my phones. plus if you upload them to your account, it saves them and you can compare how you benchmarked with different roms/kernels.
[Nexus S Android Development] jlevy73:
It also saves each run to your sd card :)
[Nexus S Android Development] avetny:
_________update

IF YOU WANNA CHANGE lcd density IN BUILD.PROP. DO IT BY ROOT EXPLORER !!

IT WORKS !!!!!!!!!!!!!!!!!!!!!!!!!!:D:D:D:D:D:D:D
[Nexus S Android Development] avetny:
GUYS I DID 180 !!! IT'S SOOOOOO SEXY !!! 100% :eek::eek::D:D:D
[Nexus S Android Development] simms22:
screenshot or it didnt happen :p
[Nexus S Android Development] avetny:
ok 180 nice but, when u press open windows u see orange line :)

200 ! Is perfect !!!!

Screen shots coming soon :)
[Nexus S Android Development] demo23019:
Wow flashed the CFS kernel and so much better than BFS with 3d rendering

request 1.2 CFS for nightly pretty please :)
[Nexus S Android Development] jlevy73:
+1 to that or 1.3 CFS with working BT :)
[Nexus S Android Development] MaliceOmega:
you can change it via root explorer, its also automatically makes a backup of your previous build.prop. i prefer 200 though. 180 makes it quite small and it looks pretty cramped lol
[Nexus S Android Development] irishrally:
I swear I looked but I don't see the cfs kernel link.
[Nexus S Android Development] willcpfc:
good call..... +1:D
[Nexus S Android Development] jlevy73:
Here you go
[Nexus S Android Development] irishrally:
Thanks.....
[Nexus S Android Development] bratfink:
Any chance of a 1Ghz UV'd kernel with CFS? Would be a dream :D!?
[Nexus S Android Development] gundamboy:
1.5ghz beta is rockin! :D so glad my Nightlies have support
[Nexus S Android Development] jlevy73:
Did you ever try the CFS kernel?
[Nexus S Android Development] irishrally:
I tried it with CM7 and realized quickly that it's not for CM. Ill try on bionix when I get home.
[Nexus S Android Development] jlevy73:
Lol, yeah, should have pointed that out. :o

Update: It does work with Koush's last alpha versionof cm7
[Nexus S Android Development] irishrally:
I bet it works with crackflasher #39 then too.
[Nexus S Android Development] irishrally:
1.5Ghz kernel works on latest nightly, #15.
[Nexus S Android Development] simms22:
like i said in the cm7 nightly thread... who needs duel core, we have the nexus s with cm7 and the HUGE trinity15 kernel :eek:
[Nexus S Android Development] jlevy73:
Meh, not impressed :p
[Nexus S Android Development] simms22:
id hate to be your kid :p
[Nexus S Android Development] kenvan19:
My kid won't impress me unless he can beat up superman and even then I might not tell him o.o
[Nexus S Android Development] irishrally:
Nice man ...
[Nexus S Android Development] bananis:
holy moly...

what version of CM7 and trinity kernel do i install to get that?!

(and more importantly how do i :P )
[Nexus S Android Development] jlevy73:
Simms used build #15 of cm7 with kernel 15v1.1-cm7 (which is posted a few pages back). If you already on build 15 go into recovery and flash only the kernel and reboot.
[Nexus S Android Development] alexis_p3300:
Bench &scores are really great but,is the phone ok for daily use or turned

As a demo device?
[Nexus S Android Development] icandy75:
Daily use is no problem and it gets surprisingly good battery life.
[Nexus S Android Development] alexis_p3300:
Thanks for reply, so which one suits better on stock rom?
[Nexus S Android Development] icandy75:
You may want to try this one first. http://db.tt/b5tTNDh
[Nexus S Android Development] alexis_p3300:
thanks for advise icandy75,'ll see test,and maybe go for 14 v1.0 if my device can handle it
[Nexus S Android Development] tempera:
Anyone using 1.5 kernel on modaco rom? I keep getting force closes on angry birds within 1 min¡!!!!!!
[Nexus S Android Development] Radmeister:
I can't seem to get 1.3 2.1 or 2.1.4 to work on the new CM7 15 build, everything just FCs at boot. Any ideas what i'm doing wrong?
[Nexus S Android Development] irishrally:
None of those are CM specific kernels. As far as I know, only two kernels have been offered to work with CM, 1.4b and 1.5b each with CM in the file name. I think the links below are the latest for each kernel.

1.5Ghz for CM7: http://goo.gl/B0hdB

1.4Ghz for CM7: http://db.tt/vvWnwCg

And to make your life even easier, and to paraphrase Simms and Jlevy, you do not need to wipe cache/dalvik cache before flashing the trinity kerenls with CM7. If you do a fresh install of CM7, flash gapss, reboot, then flash the trinity kernel, again without wiping cache or dalvik cache.