yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] slopresto:
Running Bionix NS1, the phone is completely stable. After flashing Trinity 2.0, I get random reboots (very frequently). I have yet to nail it down to a specific event that could be causal.

Crash has occured while....

On call, making a call, opening contacts, just after reboot

I even tried taking phone back to stock and starting from scratch. I still had the same behaviour as soon as I flashed the Trinity kernel.

Anyone else have a similar experience?
[Nexus S Android Development] Anderdroid:
Will you ever post source on git?
[Nexus S Android Development] defysword:
experiencing superuser delay on CM nighly build
[Nexus S Android Development] RinTinTigger:
Working like a charm on CM7 alpha 2 (3)
[Nexus S Android Development] RinTinTigger:
Same here.
[Nexus S Android Development] RinTinTigger:
SO TRUE!! The slim Trinity splash is much preferred!
[Nexus S Android Development] morfic:
I Could brand it with a tiny logo in the corner, that's not the problem, the problem is i *LIKE* the logo as a whole. :)
[Nexus S Android Development] morfic:
When things are less in flux i will, and after i brush up my git skills, made a nice mess of the Vibrant DoW source, so what made it to github is a little older than DoW14.

And let's face it, to copy this work, you grab the source as published to git and take your sister's calculator to figure out the numbers to type into the source.
[Nexus S Android Development] morfic:
Ok all of you setcpu users with screen off profiles, STOP DOING THAT.

On a more serious note, Galaxy S/Nexus S transition to/from sleep at 800MHz, so make screen off profiles from 100-800.

I may try to find all references to 800mhz and try to make it go at 400mhz, if i find time to even look. And i'll have to read up if there is a reason why i shouldn't even think about doing that.
[Nexus S Android Development] willverduzco:
Do you think that it would be possible to make a version with a cfs rather than bfs? The reason that I ask is that while everything works now, dungeon defenders, which presumably uses multiple threads, is much less smooth than on previous versions. Thanks for all your awesome work!
[Nexus S Android Development] jeff_00789:
I have overclocked my nexus s using trinity to 1.3ghz but I am facing 2 issues. I am not able to. Browse https sites on the browser and unable to play videos on rockplayer or even u install it. Did anyone face the same issue and if u did how did u solve it.
[Nexus S Android Development] teledude:
wow :D

1.4ghz is FAST :D

3650 in quadrant so far....
[Nexus S Android Development] mamba720027:
well comeing from Bionix NS1.2 trinity and stock. After installing the new 1.4ghz kernel got booted up to the nexus logo and had random reboots. Looks like my phone wont handle the power of the beast lolz.:D
[Nexus S Android Development] Tyruiop:
Seems stable with Trinity 1.4 and Bionix 1.2. Bluetooth works.

Great job, thanks !
[Nexus S Android Development] Michigan Jason:
400max 200min on demand with screen off.

I dont mean to beat a dead horse here, but I remember being able to use set cpu and 400max 200min ondemand while screen is off and having no problem what so ever waking the screen up. Is the 400mhz step not ever going to be implicated in this kernel? I understand that you get more steps on the top end if you remove the lower ones, but I liked the 400mhz step. Just shed some light please.
[Nexus S Android Development] slopresto:
Third time is a charm. After a complete wipe....this time, I have no chrash. Been running stable since last night.
[Nexus S Android Development] Highland3r:
Any feedback on issues with apps requiring SU (i.e setCPU, titanium, adfree etc)

TIA
[Nexus S Android Development] Tyruiop:
I had to delete data from SetCPU but since, it works perfectly. Titanium seems to work well to, so does ROM Manager.

Now, there is one non-root app which doesn't work since I installed the trinity 1.4 kernel (H.a.w.x), I'll try reinstalling. And my quadrant result's are lower than with the 1.3 kernel.
[Nexus S Android Development] Guitarfreak26:
Got boot loops on cm7 with the 1.4 kernel. Sorry if its already posted or mentioned!!
[Nexus S Android Development] demo23019:
Yea boot loops for me also on modaco and also tried BIONX rom and still same think 1.3 is as far as my NS will go :(
[Nexus S Android Development] asci:
Which rom version did you use to upgrade kernel? The one with stock kernel or the one with trinity 2.0 kernel?
[Nexus S Android Development] Michigan Jason:
Anyone have some intel on this situation?
[Nexus S Android Development] Tyruiop:
The one with stock kernel
[Nexus S Android Development] d0ugie:
Argh bootloop on modaco r3. Really want a taste of 1.4GHz, woah man, so could those of you who got the new 1.4ghz kernel please note which rom you're running?

Thanks for the hard and prolific work team whiskey, you guys kick ass. Don't be shy about putting up a donation link.
[Nexus S Android Development] avetny:
haahahahahahahah 1.4 is here !!!!! YEEEEAAAA baby !!:D:D:D
[Nexus S Android Development] SS2006:
Quadrant isn't working on nexus s

How'd you manage this
[Nexus S Android Development] simms22:
after reinstalling root explorer and setcpu, everything buy drocap is working. latest cm7 kang :D
[Nexus S Android Development] simms22:
it works like 25% of the time. be patient and keep trying.
[Nexus S Android Development] teledude:
Or install Quadrant advanced and turn off the 3d test :D
[Nexus S Android Development] Michigan Jason:
quadrant works 100% of the time if you get advanced and disable the 3d and 2d as stated above.
[Nexus S Android Development] d0ugie:
update scanner

All right then it's time for cm. Thanks.

Question, what's up with Linpack scores being about half that of N1s?

Protip: For those of you addicted to checking for updates on this kernel, grab this FF plugin, open up the first post as its own page, right click, scan for updates, set it for 15 minutes or slower (5m is rude), put the sensitivity on the left, do other things in life, get an alert, flash the zip. Best bet unless there's some kind of XDA VB alert for posts being edited.
[Nexus S Android Development] jwr2d2:
My nexus wouldn't even boot up wit the trinity14 kernel, glad I remembered to do a nandroid this time

Sent from my Nexus S
[Nexus S Android Development] simms22:
flash the rom, gapps, then kernel. if i just flash the my wont boot either.
[Nexus S Android Development] willverduzco:
So I reverted to Trinity 1.3 GHz rev 1.3 to get rid of BFS, and it runs Dungeon Defenders (and scrolls in Opera) much more smoothly.

Morfic, would it be possible if we could please get a version of the revision 2.0 (or 1.4 GHz, rev 1) in CFS variety?
[Nexus S Android Development] manook:
Cant seem to run 1.4 for some reason. Tried full wipe on CM7 and BS1.2 but constantly bootloop at different stages. 1.3GHz V2 works fine so gone back to that....
[Nexus S Android Development] hoseth0711:
Got the same problem:confused:
[Nexus S Android Development] manook:
Im guessing some people are having this problem due to slight difference in hardware. Might need vcore increase to make stable for some or 1.3ghz might be the max.... time will tell...
[Nexus S Android Development] d0ugie:
Yup. Same here, switched to CM, bootloop. Apparently a hardware thing. Damnit.

Had this with my Nexus One exchange. Used to be able to run any pershoot OC kernel, then my volume down button broke, got an exchange, and then pershoot kernels would reboot when OCed whereas Wildmonk's worked even up at almost 1.2ghz, no problems. Sigh, really itching to ride this OC progress, hope whatever is different about my phone and those of others in my boat aren't stranded for good. Though 1.3ghz ain't bad... :)
[Nexus S Android Development] jlevy73:
Have you done any benchmarking at 1400?
[Nexus S Android Development] teledude:
I have - 59 in nenamark1, 65 in neocore and 3671 in quadrant is the highest so far.
[Nexus S Android Development] sombionix:
Unfortunately guys, when we start hitting these speeds, not every phone will be able to handle the overclock. For example, Morfics phone can handle the 1.4, but my phone cannot.
[Nexus S Android Development] Marmle:
1.4 works fine on my phone:D Can i get a 1.6:rolleyes:
[Nexus S Android Development] willverduzco:
Yes. This is the same problem I'm having. It's due to BFS used in the 1.3 GHz v2.0 and 1.4 GHz v1.0 kernels. If you revert back to 1.3 GHz v1.3, the problem goes away.

Edit: I've attached the CFS 1.3 GHz v1.3. Sadly Bluetooth doesn't work on this kernel, but it's better than having horrible Dungeon Defenders performance.
[Nexus S Android Development] d0ugie:
If it was an issue of a handling cutoff between two different batches of Nexuses, given that the phone boots at a slow speed, and that the loop starts on the splash, no OC taking place, would it not make more sense that there is something else about the differences between the 1.4 and 1.3ghz kernels that's tripping up some phones? Maybe it's a voltage thing?

As I said with my first nexus I could overclock anything, my replacement nexus pershoot's would reboot soon if I overclocked it but still boot and work for a bit, but this is an immediate loop. Also, when I switched to some other OC kernel on that nexus, it worked, even at speeds faster than 1.13ghz.

I'm saying there may be hope that some of us didn't just hit a wall for good. On the other hand it may require one of us lending morfic and his team a phone...
[Nexus S Android Development] nsavani:
Boot loop for me. Running bionix ns1.2
[Nexus S Android Development] PAVNEET101:
1.4 ghz kernel

working perfectly fine for me and got a quad score of 3201, 19.33 mflops and 49.33 nenamark1 score

update - after rebooting and not turning on the setcpu i got the quad score of 3549
[Nexus S Android Development] ddb540:
Is there a Kernel update how-to-guide for newbs like me? I'm running a rooted phone with the Bionix ROM. All of this is so new to me (but exciting)!

Thanks!

DDB
[Nexus S Android Development] SS2006:
Is setcpu needed to make use of this overclock or is just flashing it enough
[Nexus S Android Development] d0ugie:
Just put the zip on your phone's sd then fire up the zip the same way you flashed your rom in recovery.
[Nexus S Android Development] jlevy73:
Need setcpu
[Nexus S Android Development] jlevy73:
1.4ghz booted fine for me running it with CM7. BT works fine as well. However, as others have reported, I am seeing a significant framerate decrease when running 3d intensive games (anything by gameloft). Dungeon hunters and Sandstorm lag. I think a CFS variant would solve that.
[Nexus S Android Development] tominater12:
Very unstable at least for me the phone keeps crashing and it will not turn on again until I pull the battery. Going back to 1.3
[Nexus S Android Development] tominater12:
How long does it take you to play dungeon defenders because I can not even get it to go past the title screen.
[Nexus S Android Development] jlevy73:
It doesn't take very long to boot. The issue is when it does boot and the game starts, the players movement lags a lot. For example, swinging my sword to kill the spiders is in slow motion.

I have setcpu to 1000/100. I only use 1400 for benchmarking tests.
[Nexus S Android Development] SS2006:
Bootloop with 1.4 on cm7

1.3 is fine tho
[Nexus S Android Development] icandy75:
Just flash, setcpu is not needed.
[Nexus S Android Development] jlevy73:
To control the kernel it is. For booting up, no of course not
[Nexus S Android Development] AllGamer:
i only use SetCPU to save on battery power

it's not needed to run this kernel
[Nexus S Android Development] burnfire:
it killed my phone app after about 3 hours...kept getting force close..nothing I tried worked...maybe it was the romman...3.0.0.7 update. Can't really remember.
[Nexus S Android Development] tominater12:
No the kernel is just REALLY unstable.
[Nexus S Android Development] morfic:
It is natural to have fewer devices that can successfully run an overclocked kernel, the higher you go.

It is what it is, it's like reading Celeron 366 can do 550 and then finding out yours doesn't.

IF you have trouble with a certain speed, return to the last one that ran stable for you, as you would when you did this to your PC (there you would return to the speed in bios, not kernel, but you get the idea......or you would add cooling or better RAM, choices we don't have)
[Nexus S Android Development] jlevy73:
What voltage are you using for 1.4ghz?
[Nexus S Android Development] AaronMFeld:
Flashed this onto MoDaCo r3

C:\Documents and Settings\associate1\My Documents\Downloads\android-sdk-windows\

tools>fastboot flash boot boot.img

sending 'boot' (3256 KB)... OKAY [ 0.578s]

writing 'boot'... OKAY [ 0.422s]

finished. total time: 1.000s

Worked great. However, first boot was weird in that I had to fiddle with the airplane mode, turning it on and off to get it to connect to the cell network, then until a 2nd or 3rd boot it failed to recognize the internal sd card for a couple of boots. Running it with setcpu in performance mode without problems, wifi, gps, usb mounting etc all work. Quadrant is 3199 :)
[Nexus S Android Development] tominater12:
That is the issue even putting it back at just 1 still made the phone crash like crazy and be laggy.
[Nexus S Android Development] morfic:
0.2V more than stock (1GHz).

Some devices would run it at .15V more than stock, but a lot more devices would not.

With nightshift the last days, i had no time to work on improving this, with some time, it *MAY* be possible, no promises.
[Nexus S Android Development] jlevy73:
Thanks. Any chance you'll make a CFS version of 1.4ghz kernel in the future. Would be much appreciated.

Edit: I agree the boost in voltage, while working the chip harder, will provide more stability.
[Nexus S Android Development] morfic:
Vibrant runs at .05V less just as well, but with the scores being so much lower, maybe gets worked less hard. so dropping back those .05V would still be my goal, at least i would like to try it.
[Nexus S Android Development] jlevy73:
Can't hurt that's for sure. Wonder why the difference between the Vibrant and the S considering their virtually the exact same chip (if not exactly the same). Anyway, crashing and burning is half the fun of development.
[Nexus S Android Development] morfic:
Think about you and your desktop.

You overclock to 4ghz. Happy as can be. Playing single threaded games all day long.

You sell it to a friend. But he does not game much, instead he converts videos with multi threaded apps. Then 2 days in, he calls you a liar and a cheat and wants his money back.

What happened? Your single threaded game never taxed the CPU much. A lot was done on gpu.

His apps used the CPU to the Max. And he crashed a lot.

This is what Intel and amd take advantage of in their Turbo core cpus.

If I peg only 3 cores my 1090T scales higher than when I build your kernel and peg all 6 cores.

Why did I go here? Compare 1.4ghz vibrant with 1.4ghz nexus s CPU scores.

I don't think we compare apples to apples. More efficient use of the CPU has to be involved, otherwise it wouldn't be very similar hardware.
[Nexus S Android Development] XtremeKh:
Bootloop with MoDaCo r3. Only on Trinity14, 13 is fine... could also be limit of hardware.
[Nexus S Android Development] jthornton71707:
I Dowloaded the latest update and t14 flashed and its just stuck at the boot screen. I've tried reflashing wiping everytging and still freezes. Is there any way to fix this?
[Nexus S Android Development] aam6906:
quadrant went from 3156 to 3286........had a few boot loops when i flashed 14 but seems ok now........

EDIT: 14 is too unstable, going back to 13
[Nexus S Android Development] jonjon68:
Not for me. Well I don't have the problems with the specific games but 1.3 was extremely buggy in general on my phone. Not surprised though.
[Nexus S Android Development] helfone:
help please:

I installed cm7 alpha 2(2) and then the 1.3 v1 kernel, but im stuck at the boot image, wont go further. I hear other people having this kernel working, what am I doing wrong?
[Nexus S Android Development] 651stp:
bootloop here also, thanks for the work though morfic, i know its not your kernel and its my phone :) will stay on 1.3 or go exchange till i get it working! XD
[Nexus S Android Development] AllGamer:
i can confirm

I installed Bionix 1.2 + Trinity 2.0 kernel at 1300 working fine with both of my Stereo Bluetooth headset Jabra 8010, as well as my Car deck Bluetooth Clarion CZ509

with SetCPU on auto on demand profile
[Nexus S Android Development] andyandrwew:
flashed Bionix 1.2 then trinity v2 after a clean wipe and im having EXTREME failure on boot. it is able to boot but basically reboots and has weird errors.

and as long as i might get help, can someone tell me why its BFC. i hate BFC.

thanks in advance
[Nexus S Android Development] zps123:
funny thing is after flashing the 1.4ghz kernel, when running benchmark the marks is actually decreased (like around 1700 for 1.4 but usually get 3500 for the 1.3 ghz), but in normal uses its actually accelerated... LOL WTF?:eek:

EDIT: reboot got me a much higher score... LMAO
[Nexus S Android Development] defysword:
Able to boot, but got reboots. The superuser delay issue is still there. I'm on cm7 nightly.
[Nexus S Android Development] jwr2d2:
Ill try that

Sent from my Nexus S
[Nexus S Android Development] morfic:
There is always a chance to go higher, but it involves increasing voltages, then there is no headroom to go higher on frequencies

I'll see if i can just get cfs and bfs built one after another, neatly tucked into their own .zip, i'll let you know how that goes.

The fallout wasn't as bad as i feared, so i may risk reducing Voltage on top speed.

reminder, do not use setcpu profiles that exclude 800mhz

uninstall and reinstall apps hanging on black screen on app start

'night
[Nexus S Android Development] jlevy73:
Thanks.

What about the main setting for setcpu (you know the initial page where you select what type of governor to use). Is it important to use 800mhz there as well?
[Nexus S Android Development] morfic:
The comment was meant for those with screen off profiles and wanting to stay below 800mhz.

the easiest is to not use setcpu, battery life is great, better than stock, it scales up when needed and not otherwise.
[Nexus S Android Development] asci:
Installed Trinity13_2.0 over unofficial #33 Cyanogen 7 and everything works fine, but set CPU. But it's not a prob at all. I would try Trinity14...we will see...

P.S. OVERCLOCK WIDGET (market) works fine!
[Nexus S Android Development] slopresto:
While Trinity1.3V2 is mostly stable, I had to go back down to the 1.2 kernel.

With 1.3, I had some odd behavior, as listed below

-Problem with ADWex latency and force closes

-Problem playing movies in vplayer (Started playing and then would get a hang condition, which would eventually reboot the phone.)

-Missing text on desktop widgets. (Could have something to do with the ADW issues)

-Hangs on lock screen (pattern)

-Force close on various other applications

Back on Trinity1.2 now and everything works perfectly. I miss that little extra boost from 1.3, and yes it is noticeable (especially during screen transitions).

Would love to have a stable 1.3. Any ideas as to what the issue may be? So many others here who report 100% stable.

Thanks guys. Even if I get stuck at 1.2; it is a definite improvement over stock, so thank you very much.
[Nexus S Android Development] siberslug:
I get stuck at the boot screen on all of them

were can I find the stock kernel ?
[Nexus S Android Development] simms22:
reflash the rom
[Nexus S Android Development] jwr2d2:
I came from the stock kernel to trinity13 and when web browsing the pages won't load and I cannot input anything in the text boxes on the web page. Anybody else have this problem?

Sometimes it works fine then other times its unresponsive and I have to reboot to get it back working.

Sent from my Nexus S
[Nexus S Android Development] siberslug:
got it thanks
[Nexus S Android Development] siberslug:
so far so good at 1.4ghz.

for me everything is rock solid.
[Nexus S Android Development] morfic:
Fascinating to see people going from getting stuck on boot screen on all of them to running 1.4ghz.
[Nexus S Android Development] simms22:
my experience with other kernels(on the nexus one) is that voltage plays a key role. seems like some phones run great at lower voltages, but others seem a little "buggy". but when you up the voltage slightly, the bugginess disappears.

these kernels that you are providing run great of my NS, the only issue is a few root apps, which reinstalling them clearly helps for a short time. i wonder if a little extra voltage would cure that.
[Nexus S Android Development] Anderdroid:
/still sad that stock has been abandoned
[Nexus S Android Development] morfic:
Don't worry. I'll look into it. Working nights eats time. Worked on 1.4 before looking into stock compatibility. It shouldn't have stopped working.

I'll probably have a test. Basically rebreaking Bluetooth since it's all that changed. If that makes it boot I can see about using another command line. That both fixes Bluetooth and maintains

Working on stock. I have a pretty good idea for that.

I just have a few things to do aside working and family.

My vibrant runs Nero3 with 1.4 ghz jpx based i9000 built kernel.

Box is compiling something right now......
[Nexus S Android Development] aimfire72:
Still no BT for me on both 1.3 and 1.4, running the latest Bionix with everything wiped beforehand. So weird how BT works for some, but not others!
[Nexus S Android Development] morfic:
Works for most.

Some even said it didn't work after wiping, then it worked after wiping.
[Nexus S Android Development] jlevy73:
Starting at 1.3, BT started working for me both with Bionix Rom and CM7
[Nexus S Android Development] mortzz:
1.4 is bootlooping on my phone, I was completely stable on 1.3.
[Nexus S Android Development] intothevoid:
Getting boot loops as well on 1.4
[Nexus S Android Development] Taquitoz:
No bootloops for me on 1.4, but freezes and forces me to pull battery every 3 minutes. Back on 1.3 now. Haven't had time to test bluetooth.
[Nexus S Android Development] aimfire72:
Weird, 1.4 was very stable for me, was just the BT I couldn't get working.
[Nexus S Android Development] slopresto:
Any chance of getting a BT fix for the 1.2Ghz build of Trinity? So far, it is the only one that runs stable for me, but no BT in the car kinda sux.
[Nexus S Android Development] DebauchedSloth:
Would very much appreciate the source. Don't need a whole github dump, just the relevant files. I'm most interested in getting this working with stock/BT.

Thanks!
[Nexus S Android Development] morfic:
The fix is the --cmdline added to mkbootimg. When i am back at the pc i can paste the added part to mkbootimg commandline.

I have a booting aosp build. Worst case i can use the created boot.img from that.

but i would really like to optimize that build first.
[Nexus S Android Development] dwang:
Would you mind adding cifs.ko module to your kernel? I'd like to be able to mount smb drives.

Thanks!
[Nexus S Android Development] morfic:
Will add it for next time.
[Nexus S Android Development] mortzz:
Any ideas on why some phones won't boot with 1.4? Is 1.3 just the limit on ours?
[Nexus S Android Development] dwang:
thanks, appreciate it!
[Nexus S Android Development] morfic:
Correct. As is 1.2 for others.

That's why 1.3 goes into the aosp build. Makes sharing easier.

Plus i very much like 1.3's overall performance.
[Nexus S Android Development] jlevy73:
Yes, 1.3 is very good as long as you remember to set one of the profiles to 800 :)

BTW, what's the magic behind 800mhz. I've read and read and can't seem to figure it out.
[Nexus S Android Development] defysword:
Uninstall/reinstall root exploror just fix superuser delay, (black screen) issuse for a while on 1.3 kernel.