yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] morfic:
It's defined as the frequency used to enter sleep.

It doesn't explain why 800 is used over any other frequency.

The s5pc110 docs are full of mentions of 800mhz as the maximum frequency.

in the same pdf they then go on explain how to do 1000mhz.

2.2 source then even has a 1.2ghz in source, sleeping at 800mhz.

I would like to know what the magic is , would make it easier changing it to something lower.
[Nexus S Android Development] Adamantbob:
Bluetooth does not work using the latest 1.4 Ghz kernel under CM7.

attached logcat

Keep up the awesome work!
[Nexus S Android Development] yungfresh:
using Trinity v13 and cm7 and have no problems so far! Bt works and setcpu is set to 800 on screen off. Great work!!
[Nexus S Android Development] k0mpresd:
stock rom. og poster hasnt provided cm7 love yet.

op: your kernel seems unstable. :(

anyways, :):
[Nexus S Android Development] unremarked:
Confirm it "works" on CM7, but it's incredibly unstable.

After flashing the first time, the phone immediately locked up then rebooted on it's own. Flashed a second time, and the phone was stable for about 60sec then lock up and reboot. Basically just long enough for LauncherPro to turn on, and me to get to SetCPU to crank it up to 1.2ghz then lockup/reboot.
[Nexus S Android Development] mortzz:
Mine will work normally until I do something graphics intensive. I ran Linpack and got 18MFLOPS IIRC. When I run Neocore it'll run for a couple of seconds and lock up. Nenamark will run a little longer, but locks up as well.

Great first effort though OP. Thanks!
[Nexus S Android Development] k0mpresd:
i got 2507 on quadrant the first time it ran using this kernel and ext4 mod.
[Nexus S Android Development] morfic:
how many of the instant lockups are from people on LP?

i abandoned LP while stabilizing DoW for froyo, LP drove me nuts and ADW didn't lock me up.

been running on this booted kernel all day, been benchmarking a lot thus posted it

based on the user experience shown here, i'll see about tweaking voltages, kind of early as it's only 1.2ghz

adb shell dmesg | grep -i bcm

i hope noone here sees bcm complain about incorrect version magic, then the module is not in place. aside from no wifi, it was quite flakey before i noticed i didn't push module to the right place. I'd appreciate some feedback on this, just to make sure i don't end up chasing a phantom later.
[Nexus S Android Development] morfic:
accidental double post
[Nexus S Android Development] morfic:
oh you should try this with performance governor. (if this score is from advanved with 2d and 3d disabled)
[Nexus S Android Development] sombionix:
Its unstable because it was made for my nexus s rom which I haven't posted yet.
[Nexus S Android Development] unremarked:
Fair enough! I'll sit back and wait for the magic to happen then. :) I was wondering to whom the OP was referring when he mentioned "sombio" hehe.
[Nexus S Android Development] qreffie:
Good to see you in the Nexus S Dev section Som. I take it TW is going to fully support the NS then?
[Nexus S Android Development] PlankLongBeard:
Thank You 4 Our First OC Kernel

I wanted to say thank you... :D I installed your "k0mpresd" zip and all went well on MoDoCo r3 Refresh :)

I am getting 1.2ghz (Amazingly Fast) and I can say there's def a bump.. w/ No Issues @ All :rolleyes:

@morfic Thank You!
[Nexus S Android Development] sombionix:
Yep. I picked up a Nexus S on the release date, just haven't posted a rom yet. Maybe I'll post something tonight.
[Nexus S Android Development] morfic:
of those that crash, who is using his boot.img and who is my more cumbersome step by step method?
[Nexus S Android Development] morfic:
good to know it "just works" on modaco r3.

since there is nothing special in the initrd, i expect it to run on a wide variety of roms

my plan was to make a 1.2 and then move over to 1.4 asap, with these initial mixed results, the 1.4 outcome should be interesting.
[Nexus S Android Development] ScooterG:
*Crosses Fingers* :cool:
[Nexus S Android Development] unremarked:
I flashed the modified boot.img originally.

Just flashed it again on a fresh CM7 install with the same results. I'm willing to give your method a try here shortly.

EDIT: Er, I'm apparently pretty fail at following your more... interesting instructions. :(
[Nexus S Android Development] dsmflyer:
Running your kernel @ 1.2GHz performance mode and tested with linpack, quadrant, and neocore 3 times each. Stable as a rock with no issues at all. Flashed via OP instructions.
[Nexus S Android Development] dsmflyer:
Was running on stock 2.3.1 with modded ext4 kernel previously.
[Nexus S Android Development] morfic:
You mean 100-800?

It's fine to set a 100-800 profile for best energy savings, but using profiles locking it below 800 is what's problematic.
[Nexus S Android Development] morfic:
<M> CIFS support (advanced network filesystem, SMBFS successor) │ │

│ │ [ ] CIFS statistics (NEW) │ │

│ │ [*] Support legacy servers which use weaker LANMAN security │ │

│ │ [*] CIFS extended attributes │ │

│ │ [ ] CIFS POSIX Extensions (NEW) │ │

│ │ [ ] Enable additional CIFS debugging routines (NEW) │ │

│ │ [ ] CIFS Experimental Features (EXPERIMENTAL) (NEW) │ │

acceptable configuration?
[Nexus S Android Development] dwang:
Yep looks good
[Nexus S Android Development] morfic:
Please test cifs on Trinity13_V2.1.

Those looking for working BT on 1.2GHz kernel, please test Trinity12_V1.0b.

CFS Trinity13 later.
[Nexus S Android Development] simms22:
flashed 13v2.1 earlier. its very stable! everything works great, but the benchmark scores are much less than before. where i was getting 3000-3200 before with quadrant, now im getting 2000-2200.
[Nexus S Android Development] avetny:
Kernel 1/10/2011 !!!

people can some one post Whats New about?

sorry never mind

Ok, now on to what this post was about: (Trinity14 and Trinity13 may not always be updated the same day.)
[Nexus S Android Development] willverduzco:
Can't wait!
[Nexus S Android Development] slugger410ft:
Same here.
[Nexus S Android Development] jwr2d2:
Flashed trinity 13v2.1 Bluetooth still doesn't enable but I don't use it though. Maybe its just me

Sent from my Nexus S
[Nexus S Android Development] morfic:
Working on optimizing aosp, i managed to include the aosp boot.img that does not call etc/init.d sorryabout that.

Scores should be normal with V2.1.1

Uploaded V2.1.1 that runs it again, which then includes the mount fix.

Left V2.1 up though, as it may work on some stock roms.
[Nexus S Android Development] simms22:
on top of 2.1.1 will let you know. and btw, definitely nothing to be sorry about, its more like THANK YOU :D
[Nexus S Android Development] jlevy73:
Thanks Morfic
[Nexus S Android Development] simms22:
still lowered after flashing 13 v2.1.1

getting from 2100-2200 on quadrant. but any issue i had with root apps is completely gone.
[Nexus S Android Development] gbhil:
link to source/patches ?
[Nexus S Android Development] slugger410ft:
Same issue as previously stated. Thanks for responding so quickly though.
[Nexus S Android Development] Highland3r:
Quadrant scores may appear low for some, but damn the new kernel feels quick (coming from bionix 1.1 - stock kernel)

SU apps appear fine, no working bluetooth currently though (however I've not wiped since applying the new kernel, not sure if that would affect??)

<edit> Not stable on this phone it appears. :( </edit>
[Nexus S Android Development] morfic:
Apologies everyone, got my ramdisks mixed up and buildscript too.

V2.1.4 uses the exact NS1.2 ramdisk as it should, got it tested, thanks Nazral!

/system/etc/init.d is now ran again.

I need to do some housekeeping on my files....

Integrating the build of the kernel for aosp it built nothing both aosp kernels, even if modules were copied correctly to the appropriate dirs. Fixed script, now building proper bionix kernels again and aosp too.
[Nexus S Android Development] slugger410ft:
BAM! So far so good on this one. Thanks Morfic
[Nexus S Android Development] simms22:
13 v2.1.4 did it. running 3000+ quadrants again! thank you very much. btw, some root apps dont like this kernel again :p
[Nexus S Android Development] The K-Zoo Kid:
Sorry if this has been asked 100 times.. But does the 1.4 work on cm7?
[Nexus S Android Development] simms22:
yes it does, unless you are using the left handed phone ;-)
[Nexus S Android Development] mrRobinson:
anyone try the 2.14 with modaco r4? i have the latest modaco and want to try to get a stable overclock on. this 2.14 looks promising.
[Nexus S Android Development] morfic:
Root rights black screens?

Just go to settings / manage applications and clear data for that app.

seems to be the quickest short term fix.

Preferably I just make this go away. Depends on time after work this week.
[Nexus S Android Development] JeffR714:
Morfic

Thanks a million for sharing the solution to the no root black screens I had it on root explorer,quick boot and set cpu and thought it was the kernel but I just cleared data and all's good thanks again
[Nexus S Android Development] simms22:
yea, but i figured that out already. thats why i wrote "doesnt like" and not "break" ;) much appreciated though!
[Nexus S Android Development] mrRobinson:
i just installed. boots fine. went from 2149 to 2698 on quadrant just by installing this kernel on top of modaco r4. I don't have setcpu do i need to buy it or is there something else? Just by flashing this kernel i'm not at 1.3ghz then right?

Edit: google earth never starts... spins wheel for a bit then closes...
[Nexus S Android Development] jlevy73:
I did try this and the Rom and kernel did not get along
[Nexus S Android Development] jlevy73:
Simms: what your setcpu settings in profiles?
[Nexus S Android Development] simms22:
i dont use any profiles. 1300/100 ondemand(sometimes performance).
[Nexus S Android Development] jlevy73:
So you're not using the 800mhz Morfic suggested for sleep :eek:
[Nexus S Android Development] simms22:
nope. i believe thats the suggested profile if youre using profiles.
[Nexus S Android Development] dwang:
cifs working great with trinity13 v12.1 and cm7.

However, Bluetooth doesn't seem to be working for me.

Seems like others are having the same issue as well.

This kernel is super smooth. Great job!

Hopefully the BT issues will be resolved soon.

EDIT: BT not working with trinity13 v2.1.4 either.

Wifi isn't working w 2.1.4 for me.
[Nexus S Android Development] jlevy73:
Lol, Trinity 2.1.4 is like Mr. Toad's wild adventures. Very unstable for me atm
[Nexus S Android Development] simms22:
lol, mr toads :)
[Nexus S Android Development] slopresto:
Bluetooth is now working on Trinity12_1.0b.

Note: I had to do a full wipe, then installed stock bionic, then install Trinity12_1.0b. After that, Bluetooth works great.
[Nexus S Android Development] slopresto:
And I almost forgot to thank you. 1.2Ghz gives enough improvement to see smooth transitions in adw ex. Now that I have Bluetooth as well, I am extremely happy.
[Nexus S Android Development] dwang:
I did a wipe and now BT is working on 2.1 (2.1.4 still gives me problems w wifi), so it looks like people need to bite the bullet and wipe if they want BT to work.
[Nexus S Android Development] morfic:
A performance governor is oddly enough just coming out of sleep at 800mhz.

best to use performance, and back to ondemand when done and you will be a much happier person i'd think.
[Nexus S Android Development] morfic:
Good news. Glad to hear the fix works for the old 1.2ghz too.

I need to compile another 1.2 soon, chances are even a 1.2ghz compiled now would be quicker a little bit.

And if nothing else, this would add the cifs module to 1.2

Too bad V2.1.4 isn't working for everyone it's a real nice little powerhouse.

So 1.2ghz, 1.3ghz and 1.4ghz all now have working BT, that's good.

cifs needs to be added to 1.2 and 1.4.

and CFS versions for 1.3 and 1.4 and a BFS version for 1.2

Then there should be a kernel for everyone.
[Nexus S Android Development] dwang:
spoke too soon on the BT issue.

After a couple of reboots, BT has stopped working for me on v2.1.
[Nexus S Android Development] jlevy73:
Thanks for all the hard work Morfic, definitely enjoying trying out the new builds.
[Nexus S Android Development] simms22:
with the latest build of cm7 crackflashers(#45), none of the trinity kernels will boot on my nexus s. and the cm7.img floating around here crashes the phone. i guess there have been some major changes.
[Nexus S Android Development] iinviktus:
Tried out 1.4 with the latest build of Bionix and it was intermittently fast and laggy :/. Didn't do a full wipe.

I miss the speed. I'm using the stock kernel.
[Nexus S Android Development] slopresto:
After numerous failures getting the 1.3Ghz running stable, it is finally there. This time, I took it all the way back to stock first. I am running modacos rom, then tried the 1.2Ghz. I booted and played for a bit to insure I had no crashes. I booted into recovery and updated to the 1.3Ghz kernel. So far, I have not had s single crash or lag of any kind.

I am curious what has been different that was causing the previous stability issues...
[Nexus S Android Development] morfic:
Fascinating, really. Adding to OP.
[Nexus S Android Development] Mr.Kakarot:
So I just tried running this kernel.... it shows the trinity screen, then my CM7 screen... then hangs, reboots and repeats... I did a full wipe/cache.....

any ideas? thx

(tried trin 14) now that I tried 13, seems to be working....

Do you need to run set cpu to take advantage of kernels...? thx
[Nexus S Android Development] fih6:
I'm a bit shocked that most of you are not stable at 1.4. I have no problems at all with it on cm7a3 and only a few phone call revolts on bionix1.2(thanks morfic).
[Nexus S Android Development] tempera:
I've just installed this, do u need to install setcpu to get 1.3ghz?
[Nexus S Android Development] Mr.Kakarot:
yea, mine would not even boot :(
[Nexus S Android Development] tempera:
Forgot to add I installed bionic with v2.0 trinity kernel.
[Nexus S Android Development] dingdonghei:
Using the 13_2.1 on stock and working flawlessly. Quick question: I've seen that google have started pushing new market to stock, and I was just wondering if the kernel will affect me getting that update?

Btw: been running this kernel without setcpu today, and the battery drainage is quite formidable comparing to stock. 100 to 45 in 7 hrs without heavy usage. With stock I would normally be at around 75%
[Nexus S Android Development] Cheeze[iT]:
I go 12 hrs and its under 25%. Stock with gmail pushing. I was thinking about flashing the 1.2 or 1.3 to get a little more performance. So just dl the kernal and flash it in recovery correct? I can flash it on my stock rom and go back to stock if needed correct?
[Nexus S Android Development] jerrycycle:
On a fresh install and using kernel 1.2b but Slingbox is not working. It opens but the picture is black and sounds like a mic keyed. Bluetooth is working for me.
[Nexus S Android Development] Xandlinger:
I've been using it without a hitch, too. On both Bionic 1.2 and CM7 Alpha 2-2.
[Nexus S Android Development] slopresto:
Sorry about this misinformation; I thought I had made some progress for a while there. (Actually did make progress in that it ran better at 1.3 than it had on ANY previous attempts)

=(

I started having problems this morning before work: Same crashing issues that I had seen previously on 1.3; they just didn't show up as quickly this time.

I reverted back down to 1.2_b. Again, things are stable; however bluetooth stops working after the phone is rebooted and can only be enabled after a fresh flash.

I am taking this back to exchange today, as I am beginning to wonder if there is not something wrong with the hardware. Based on the fact that I had a couple crashes after reverting everything completely back to stock, this seems like the most logical next step.
[Nexus S Android Development] Cheeze[iT]:
Is the stock kernal available to dl anywhere? I wanna try these but just in case it doesn't work out, I want to be able to go back to stock settings. Thanks in advance.
[Nexus S Android Development] dwang:
I don't think its your hardware. I'm having the same issues.

Going back to stock cm7, and the problems disappear. Besides the BT issues, you may want to downclock the kernel (using setcpu) to 1.0ghz and see if that fixes your crashes.

My guess is some phones can't support the higher overclocked speeds.
[Nexus S Android Development] slopresto:
Pretty sure it was the hardware, but we will see. I reverted it to stock to prep for taking it back to Best Buy. On my 30 minute drive, it crashed twice.

I am loading about to load Bionix and Trinity on the new phone now and we will see how it goes.

Who can recommend a good app to stress test this thing?

.....

update:

Can tell immediately that there is a difference. I got Trinity 1.4 to actually boot on this one, where as the previous phone would do the whole boot loop deal. With the new phone, I got to various points in the setup before the phone would lock up completely...not perfect, but progress for certain.

I am back to running the 1.3 kernel and everything is solid so far.

I was happy to get the other phone running the 1.3 last night, but this morning did not bode so well. The crashes when running stock are what really made me accept the fact that I needed to go exchange it., with the realization that I had gotten myself a lemon.

I have a good feeling this time, so let's see how it goes. =D

Update: not a single hiccup all night. In fact, seeing how smoothly this runs just points out how messed up the other device was.

For anyone who has done a clean install and is still having issues with 1.3, I'd suggest a trip to best buy. I only had 3 days left to Exchange, and am very happy I did. This is perfection.
[Nexus S Android Development] dwang:
Ok, if you are having issues with the stock rom then thats another problem altogether.
[Nexus S Android Development] slopresto:
Yeah, what a difference. I am already realizing a noticeable difference. I have had 0 latency so far and have been going since my last post.

Wishing I would have done this sooner.
[Nexus S Android Development] avetny:
nightly CM7 stop working with Bionix Kernel 1.4
[Nexus S Android Development] Guitarfreak26:
And 1.3 mate I got force close on everything with 2.0 wouldn't boot at all with 2.1.1
[Nexus S Android Development] Tyruiop:
Try 2.1.4, it should be fine.
[Nexus S Android Development] PAVNEET101:
Is the 1.4 ghz kernel safe for everyday usage? ?? Cause I am loving it and keep it for everyday use
[Nexus S Android Development] hkoutso:
If it works for you (meaning on your device) yeah why not. I got a few random reboots (1-2) per day but it is something I can live with ;)
[Nexus S Android Development] avetny:
whats wrong with updates?????????????????????????????????????? team is dead?:D
[Nexus S Android Development] Anderdroid:
Hey Trinity13 v2.1 is working perfectly for me on stock. Full bluetooth and everything. Yay :D

It seems as if the ext4 fix is missing from the kernel, though? Also adb root isn't enabled? Could you compile a version of Trinity13 v2.1 with both adb root and ext4 remounts?

I'm getting 2000~ on Quadrant with 3d running through, 1700 without.

After manually doing the ext4 fix ( mount -o remount,noauto_da_alloc /data /data )

I'm getting >3000

Averaging OVER 65fps on quake3droid with lightmaps on. Awesome!

Also if you include a less intrusive splash I'll donate.. again :D But I guess I can deal... But it would be much appreciated. The explosion is a bit much for me :P

As I posted before, this would be a lot less intrusive yet still rep TW.

Not trying to ask too much but if all this was added I'd be a very happy camper ;D
[Nexus S Android Development] RaQHoliday:
1 or 2 random reboots a day with 1.4 on CM7 Alpha3, but nothing ridiculous. Once I stopped using SetCPU everything has been running great.
[Nexus S Android Development] morfic:
My boss disagrees, he wants me all to himself though...

Time is stretched thin when i work, and Vibrant got a refreshed kernel to play with.

And due to 3D game framerate complaints i had to run extra rounds of NFS:S to make sure.....never a hiccup there. Nor Asphalt 5 Demo.
[Nexus S Android Development] RaQHoliday:
Anyone know if there's a gapps.zip somewhere that includes the 2.2.10 version of the new market yet? 2.2.7 is running fine, but I'm a bit of an update-whore lol
[Nexus S Android Development] hkoutso:
Although we are in the Kernel section of Bionix:

Why don't you try pushing the 2.2.10 market apk from the corresponding thread ?

http://xdaforums.com/showthread.php?t=909776
[Nexus S Android Development] RaQHoliday:
Whoa, TOTALLY posted this in the incorrect thread, my apologies.
[Nexus S Android Development] asci:
Just to report that Trinity13_V2.1.4 on MCR r.8 works great!
[Nexus S Android Development] bratfink:
Battery Life

Do you experience better battery life using this kernel at 1GHZ? Or can anyone else comment on battery life compared to the stock kernel :D. Thanks
[Nexus S Android Development] MaliceOmega:
i normally get about 6-8 hours but im running the 1.4 trinity kernel. on stock i had about 14-16 hours with heavy usage and 18 or so with moderate usage :D

but i work at a cell phone store so i have no problem trading speed for battery life cuz i can charge my phone whenever lol
[Nexus S Android Development] Anderdroid:
I can confirm that battery life has dropped. I'm using 1.3GHz v2.1 on fully stock rooted ROM. Before overclocking I'd get over 20 hours on battery. Now I'm getting about 13.
[Nexus S Android Development] MaliceOmega:
though you shouldnt expect stock battery life from a oc kernel in th first place. the further you go from stock speed the faster your battery is gonna drain. the exception is if the kernel is uv'd. though you can only go so far with that.

basically the end equation would be faster processor=less battery life
[Nexus S Android Development] defysword:
looks like many of us are waiting for an OC UV kernel. :)
[Nexus S Android Development] dobber81:
+1
[Nexus S Android Development] erseta:
WOWW!! Damn fast and stable, thanks!!
[Nexus S Android Development] MaliceOmega:
those of us familar with morfics kernels know that hes never let us down before. im sure they are cooking up some magic for our nexus'. we'll have even more awesomeness soon lol :D
[Nexus S Android Development] morfic:
then you are doing something wrong. not necessarily personally, but you like a rogue app.

something is causing your phone to scale up too often. as BOTH 20 hours for stock rom and 13 hours for 1.3ghz sound atypical.

however they seem to make sense if something causes your phone to scale up abnormally often.

I see it time and time again when people have high loads and are unaware of it.

in setcpu's info tab. check time in state and check which frequency is most used, which is second and which frequency increases the most while screen is off.

you don't need setcpu to see this info, but most of you prefer a GUI to check this anyway, so why not refer to that right.

OK you UVOCers. UV or OC?

I may be able to tickle out a 100mhz UV while keeping some top end OC, but above mentioned info makes or breaks this.

I you aren't using 100mhz much you won't see much from the UV.

even a 1ghz kernel would run better than stock and then we could explore voltage limbo style.

I'd need to know what top speed people expect on a UVOC kernel.
[Nexus S Android Development] kzakaria:
1.4 GHz if possible. Where is the next version of 1.4? I have the curent version running but under heavy load it reboots. Please release the new version of 1.4 ASAP.

THANKS for all the great work!!!!:)