yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] morfic:
I had a UV, even a "big bore" UV, but noone until now asked for UV since we got 2.3.3.

UV demand is low it seems.

That's not a No though ;)

Sent from my Nexus S
[Nexus S Android Development] Jrbourque:
Gotcha ....was just wondering thread just went away lol ....thanks for quick reply :)
[Nexus S Android Development] dario3040:
I don't think its a low demand for it.

Maybe more: It was pretty unstable.

But: Is it possible to make it underlock under 1 GHz?

And i have a question

have you tried increasing the GPU frequency?
[Nexus S Android Development] alexis_p3300:
Looks like i can't overclock to 1.4 on supeaosp with honity and setcpu anyone make it?
[Nexus S Android Development] dario3040:
What is your question?
[Nexus S Android Development] alexis_p3300:
Set cpu won't let me set 1.4 as max speed,(running on superaosp and honity)
[Nexus S Android Development] simms22:
did you flash honity12 or 14? and what do you mean... does it freeze at 1.4ghz or there isnt an option for 1.4ghz?
[Nexus S Android Development] alexis_p3300:
Honity 14,the slider goes to 1.4 but cant stay there,going back to 1,maybe i'll try wipe again
[Nexus S Android Development] Rafael Cadina:
Maybe your Nexus can't handle with this level of oc. Try honity12
[Nexus S Android Development] dario3040:
I don't think thats the problem.

I think you are moving the slider on the bottom past the one on the top.
[Nexus S Android Development] alexis_p3300:
Mates the slider cant stop at 1.4 going back to 1ghz as soon as i stop holding it,like a spring hold it(won't even set to 1.4 anyway to much trouble for nothing,i'll wait trinity's come back i was stable on 1.5b
[Nexus S Android Development] simms22:
clear data for the setcpu app and reflash the kernel.
[Nexus S Android Development] morfic:
Nothing is set in stone, so the numerals equivalent to "kicks a lot of ass" may not be equal to 15.

Don't get hung up on numbers. ;)

Sent from my NookColor
[Nexus S Android Development] dario3040:
Y U Have a NookColor?!?
[Nexus S Android Development] simms22:
he bought it to watch his daughter play angry birds on....

:-P @morfic
[Nexus S Android Development] morfic:
Simms22 is right....

But I think now where I realize how puny the nexus s is....she will be playing it on there.

Seriously though, after using the nook color for a while the nexus s feels tiny, kind of how the mt3g felt after using vibrant for a while.

CM7 on a nook color is awesome, just saying, you should get one too.

There is about one nook color for every nexus s on stats.cyanogenmod.com I think you are one of the few that seem to be missing.

Simms22's clocks blink 12:00, so I don't think he can handle one....

Sent from my NookColor
[Nexus S Android Development] morfic:
He says his slider bounces back. If it can't handle it, it's not going to affect the slider.

The only time I see slider bounce is if min and Max don't agree which is then user error on my part.

Sent from my NookColor
[Nexus S Android Development] simms22:
uh-oh, 12 o'clock... better head home before my carriage changes back to a pumpkin and i lose my princess outfit. my fairy godmother will be furious :eek:
[Nexus S Android Development] jlevy73:
That reminds me of a song by Peter, Paul and Mary called Puff the Magic Dragon :eek:
[Nexus S Android Development] morfic:
I knew you had to have met him

Sent from my NookColor
[Nexus S Android Development] dario3040:
You bought it... To watch your daughter play Angry birds? :|

I want it, but i live in Europe :eek:
[Nexus S Android Development] dario3040:
I know that song :D

We had to sing it in 5th grade 0.0

like 50 times at least :3
[Nexus S Android Development] dario3040:
Thats what i said too :3

It must be an user error.

edit: i think it might also be the profiles that are doing something.
[Nexus S Android Development] avetny:
I will miss Morfics kernels

my phone on the way to Texas Samsung repair center....see u in 2 weeks friends ;)

"we are not going away forever, BUT we left BEAUTIFUL..."

my last Post: 666
[Nexus S Android Development] alexis_p3300:
wiped again and now working sliders again,back to 1.4 thanks for support friends
[Nexus S Android Development] simms22:
sweet, my lucky number.
[Nexus S Android Development] dario3040:
Really?

I hope not :o
[Nexus S Android Development] simms22:
honestly it is. so are the numbers 3 and 13. while 7 is very unlucky. btw, check the about phone in settings, kernel version(if you are using honity) :D
[Nexus S Android Development] dario3040:
I saw it :o
[Nexus S Android Development] morfic:
For a no setcpu way to OC, try "no-frills cpu control"

Does nothing but set speed one time.

No profiles we don't need, no advanced tab to mess up with.

Just plain a simple min/max/governor.

Sent from my Nexus S
[Nexus S Android Development] dario3040:
Are you making something new?

I haven't heard of the new trinity yet.

Im not asking for any ETA's, but just wondering how things work out.
[Nexus S Android Development] ogdobber:
i haven't tried it yet but isn't that basically what the cpu controls in cm settings is? of course "no-frills cpu control" would work great for other no cm based roms (modaco, stock, etc.)
[Nexus S Android Development] morfic:
of course, just quicker than menu/cmsettings/performance/yeahsurewebecareful/settingstufffinally

:P

Was waiting for the boot animation/logo, then bought the Nook Color, and while running the crap out of the new kernel work out stuff for the nook color.

Main hold up "work around the house".

Plus debating what frequency combination to pick for the first Trinity.

My problem is that i have a pretty strong conviction against flash, with that in mind i can push things harder and not care about flash and just care about everything else.

What i debate about is how much outcry that would cause, I've been using the new kernel for 4 days now and not found me wanting anything it didn't give me.

Jlevy does his usual locking up, simms22 seems to miss flash.

The activity is happening, just not very public.
[Nexus S Android Development] simms22:
dude, i had to look. it has only been 4 days. and the thing with flash, might be a flash related thing. it works most of the time. if i clear the app data for flash, i have no problem.
[Nexus S Android Development] dario3040:
Honestly, i use flash on my phone for some things, like music on youtube while multitasking.

But i could easily live without it.

Ive been using the h14 Simplified code 3 and it is stable, but the light are turning on for no reason :P

Its not really a problem because its probably fixed in the newer bln versions.

Not that i use bln anyway :P

Its fast, but i would gladly take more speed in exchange for flash any day :eek::eek::eek::eek::eek::eek::eek:

And simms: :eek:
[Nexus S Android Development] dario3040:
And Morfic: WHat happened to the LGK kernel?

I remember it never got released in public.
[Nexus S Android Development] dobber81:
I have a big demand for UV! :)

Edit: UV with BLN that is :P
[Nexus S Android Development] dario3040:
UV is nice, but would it be possible to UV under 1 GHz, and keep the overclock on the other frequencies.

I don't have a particular demand for UV, but i would gladly take it :<)
[Nexus S Android Development] gasparzim:
Is there any mirrors for H14 cm7?

Proxy @ work blocks dropbox =(
[Nexus S Android Development] dario3040:
Yes there is.

Have you checked H16?

Its in the start post, in the link with a long message about dragons
[Nexus S Android Development] diego.stamigni:
Yep but I don't know which take.. there are a lot of H16. What works well on cm7 2.3.3?
[Nexus S Android Development] dario3040:
None of them will probably work on your phone, they are very unstable, but if you really want to try: Here is the latest Honity 1.6

But you should probably try h14 instead..
[Nexus S Android Development] terryhau:
What's this simplified code stuff?
[Nexus S Android Development] dario3040:
I think their more stable, that was my case at least.

I would however take the one from the main post
[Nexus S Android Development] joshthewaster:
So as was being discussed in the uv thread..... I would love an UV no oc or UVoc kernel. With all the other goodies like voodoo, bln, etc.

For everyday use I like to run under volted for the battery life. That's me though.
[Nexus S Android Development] morfic:
noted, btw, love your location
[Nexus S Android Development] ragiut1:
@morfic Pls make an Undervolted stock kernel with Voodoo and BLN

Stock kernel performance is great, however i desperately need more battery life.

Many thnx for ur amazing work
[Nexus S Android Development] dobber81:
+1

I also find UV noOC useful.
[Nexus S Android Development] dario3040:
Why wouldn't you want to overclock?

You could just use SetCpu to max it at 1Ghz anyway, its optional...

But the UVoc, or whaterver its named sounds good to me.
[Nexus S Android Development] vickypollard:
Don't shoot me if this is a stupid question, but will this kernel work with a stock 2.3.3 ROM? I'm interested in kernels, but not in CM or any other ROM than the stock one.
[Nexus S Android Development] stavros86:
yes it will work if you use the modaco version of the kernel
[Nexus S Android Development] vickypollard:
Sadly, that doesn't seem to boot.

Edit: reverted to the previous kernel I was using. However, the boot animation didn't change back :P
[Nexus S Android Development] stavros86:
the first time i tried with modaco rom it stuck to the honeycomb animation and didnt boot, then i wiped everything and dalvik cache reflashed and then it booted
[Nexus S Android Development] vickypollard:
I might try that some time. However, I'm not at all disappointed with my current ROM and kernel, so there's no hurry.
[Nexus S Android Development] alturismo:
tried all kinda install combos to get stock rom with this kernel, always end up

at freeze on bootanmitaion start (1st pic with morfic signature buttom left)

i formatted boot, sys, data, cache, dalvik, batt stats before trying

installed stock, installed kernel, ... freeze

same issue when trying to install kernel directly after stock rom without reboot between, same ...
[Nexus S Android Development] wutang01:
Ok, I've tried everything. I've changed the bootanimation.zip, but I still have an intial Honeycomb still image that appears just before my boot animation (which is currently http://www.youtube.com/watch?v=lAFSEsEZnnE)

I believe it's stuck in the kernel somewhere, which I have no experience or expertise to remove.

I love this kernel. Is anyone able to help me remove this initial Honeycomb still image?

Sorry, I know I'm an anomaly. I know everyone else loves this boot animation, but I don't :(
[Nexus S Android Development] njiwani:
is the new nexus s i9023 supported? i have the one from rogers canada.
[Nexus S Android Development] dario3040:
Its not any newer than the other Nexus S devices, and yes it is supported, but Backlight Notifications don't work properly yet
[Nexus S Android Development] simms22:
the boot image was put there, and its separate from the boot animation, in the kernel zip. you might be an anomaly, but not in this case :p
[Nexus S Android Development] njiwani:
so whats the benefit if you cant do notifications? is there an alternative for the notifications?
[Nexus S Android Development] ogdobber:
the rogers nexus is a 9020a...it just uses the 9023 "root method" and recovery
[Nexus S Android Development] wutang01:
Thanks for answering my question!

So is it possible to somehow remove it by myself?

I wouldn't want to trouble the kernel dev, because it seems everyone else loves the Honeycomb boot animation.
[Nexus S Android Development] ogdobber:
you can't remove it, it is part of the kernel....the only answer is to flash another kernel. On a lighter note, morphic has stated that he is bored with it and his new "trinity" kernels won't have the honeycomb...
[Nexus S Android Development] simms22:
no they do not. they have a new trinity boot animation. speaking of which, im testing out a few undervolted stock speed versions of trinity right now, battery life loves it :D
[Nexus S Android Development] nickmv:
simms, how did you flash the kernel for the new 2.3.3 kang? I'm having no luck with it. 2.3.3 was working great flashing from build #7, but then I flashed Honity14, and it locks up as soon as the morfic honeycomb animation comes up. The animation doesn't even play, just sits there like a still.

I wiped cache and dalvik, but am unwilling currently to do a full wipe.

Anyways, I'm back to stock kernel for now.
[Nexus S Android Development] simms22:
i flashed the kanged cm7 from today, flashed gapps, then rebooted. after reboot, i went back into recovery and flashed honity14, then rebooted. i didnt wipe a thing.

this is the kanged cm7 2.3.3 build i flashed http://dl.dropbox.com/u/2769033/update-cm-7.0.0-RC1-NS-KANG0301-signed.zip
[Nexus S Android Development] hoseth0711:
Decided to go back to stock speed, cause there was a massive battery drain, does anyone else have the same experience?
[Nexus S Android Development] simms22:
UPDATED! Honity14-2.3.3 kernel for the Nexus S CM7 2.3.3 http://goo.gl/hwIBO hot! includes Voodoo color/sound & Honeycomb boot animation. workd great with nightly #11 :p
[Nexus S Android Development] willcpfc:
Is the stock version still in the works? :)
[Nexus S Android Development] simms22:
only mr morfic can answer that.... but im sure hes working on it.
[Nexus S Android Development] morfic:
Got tired of picking cherries, so just started with a clean slate with Honity14

Now where that is done. I suppose i could do stock, but stock is so boring...lot's of motivation required ;P
[Nexus S Android Development] brian6685:
Any chance of smartass scaling implemented?

Nexus S
[Nexus S Android Development] willcpfc:
Stock is boring and square but its highly stable and gingerbread is tasty! I am sure a hardcore, Morfic special firebreathing kernel would be a gift to community...adulation and praise would flow forth and at every boot people will think of your work when they see the funky animation. Or are you interested in bribery? :D failing all the above I may just drag myself back to nightlies and their attendant flash compulsions :)
[Nexus S Android Development] avetny:
THANK YOU ! for 2.3.3
[Nexus S Android Development] morfic:
Boot it, don't oc, pretty stock+voodoo then

Sent from my Nexus S
[Nexus S Android Development] willcpfc:
Yeah but overclock makes it edgy and special. When I see an iPhone I can smile inside in the knowledge my nexus has electric dynamite under the case :D
[Nexus S Android Development] morfic:
Just flash cm7 nightlies, instead of lingering on stock, hoping i get this to stock roms quick (my bad, i was replying thinking you are one of those stock frequency people)
[Nexus S Android Development] willcpfc:
I was on nightlies since they came out...but I got a bit bored of it. I am enjoying vanilla deodexed with voodoo. Zero reboots which makes a nice change from CM. I just enjoyed the trinity line lots. I expect I will rejoin the CM train at some point :)
[Nexus S Android Development] jlevy73:
I recently rejoined that train this morning as I wanted to try out this kernel. That being said, it would be nice to see morfic make a stock compatible kernel as stock is just more stable in the long run.
[Nexus S Android Development] simms22:
since when did you go all conservative on me? :p
[Nexus S Android Development] CB620:
I took the booanimation from the kernel but I realized later it was already a thread for it. LOL I feel like a fool
[Nexus S Android Development] jonjon68:
That wasn't unique to CM. That was a 2.3.2 bug. CM did seem like it made it worse however they are on 2.3.3 now for the nightlies. No reboots today so far and I was having multiple bounces a day previously.
[Nexus S Android Development] mtw4991:
So, is Honity a replacement for Trinity Max/Vmax? snipped

EDIT: nevermind, I read the last page for the 2.3.3 update. I'll send him the link.
[Nexus S Android Development] wutang01:
Awesome. I'll wait patiently for Honity14's successor :D

At the moment, I'm using Cyanogen 7's default kernel.

I just get the Google still image (with unlocked padlock icon), and then proceeds to my favourite Nexus One/S bootanimation :D
[Nexus S Android Development] njiwani:
so does that mean it will support the notification light?
[Nexus S Android Development] ragiut1:
it would be better to remove bootanimation all together to reduce boot time
[Nexus S Android Development] blackerwater:
+1 please

Sent from my Nexus S
[Nexus S Android Development] ogdobber:
yes BLN works on the 9020a
[Nexus S Android Development] dario3040:
Me want >(O.o)>
[Nexus S Android Development] morfic:
Get ready for trinity then. No more honey comb.

Of course it still has a logo.....

Sent from my Nexus S
[Nexus S Android Development] morfic:
Keep checking twitter I may do a crazy "when everyone sleeps" action of releasing Trinity with 1.44GHz and one 1.0GHz with UV.

I think I fell in love with the UV kernel......

Sent from my Nexus S
[Nexus S Android Development] alexis_p3300:
trinity's come back, morfic you're great
[Nexus S Android Development] stavros86:
we want trinity back :D
[Nexus S Android Development] dario3040:
That won't reduce boot time.
[Nexus S Android Development] dario3040:
In Norway its day when its Night in America >(o.o)>

And i have already tested the 1.44 Ghz kernel, it was slightly unstable :O,

But the UV kernel might be a backup for times i need battery
[Nexus S Android Development] RickROM:
I am currently testing Trinity with NSCollab 1.0.19. I haven't seen any problems so far, but I have one question about the kernel . . .

I removed your boot animation, but I can't figure out how to get rid of the Trinity splash image that displays before the animation. Is there anyway that you could remove it from the next version of the kernel?

I am trying to achieve a clean professional look on my device, and I feel that the Trinity image is a little too flashy.
[Nexus S Android Development] alexis_p3300:
Some times i miss the bomb image!!
[Nexus S Android Development] memburn:
Only kernal that allows stable overclocking to 1.4. Loving it so far. Only issue is with voodoo sound. Headphone amp not working. Couldnt load. I came from netarchy kernal. Think it had voodoo version 7. Am I doing something wrong? Should I uninstall voodoo control and try Reinstall? Torn Cause I love voodoo sound but also am digging the 1.4 overclock.
[Nexus S Android Development] morfic:
Trinity has Voodoo sound version 7, can't promise your phone will handle the high bus of 1.44ghz the same as honity14, worth a shot.

Honity as novelty is over.

Sent from my Nexus S
[Nexus S Android Development] memburn:
Oh ok that makes sense. Ill try the Trinity one that's posted. Awesome job on this one though. Running 1.4 stable. Worst case scenario just hop back to my backup of netarchy.
[Nexus S Android Development] memburn:
I searched for a change log between voodoo v6 and v7 and couldn't find one. Sound on the kernal is still great. If the only difference is the control app tweaks I can handle missing those.

I never really messed with the sound tweaks anyway except the amp.
[Nexus S Android Development] morfic:
Curio said there was not much of a change, fixed typos, but bumped version anyway, hence me not being in a hurry to build anything v7 unless I was building something anyway.

But....i also merged in a fix for wifi possibly keeping up phone from samsung/google, I.seem to have been affected, simms22, not.

Just for that I would suggest trying Trinity 1.44 or UV

Sent from my Nexus S
[Nexus S Android Development] dario3040:
Then you should learn to search better :P

http://xdaforums.com/showthread.php?t=806195
[Nexus S Android Development] jlevy73:
The DAC update is primarily for SGS, the lagfix update is only for SGS. So really updating to v7 would have a minimal impact at best on the NS.
[Nexus S Android Development] dario3040:
Yeah, its pointless
[Nexus S Android Development] alizawi:
I need a little help... my Nexus S is running 2.3.4 stock ROM/Kernel... what is required for me to get BLN.. that is all I really want, but never rooted or flashed my phone before.. thanks
[Nexus S Android Development] dario3040:
Wrong thread, go to the new one.
[Nexus S Android Development] jlevy73:
In a way yes. Right now I believe Honity is the only morfic kernel that works with 2.3.3. I don't believe Trinity is compatible with the latest update.
[Nexus S Android Development] mtw4991:
Thanks Josh...good to hear from you again. Been lurking here off n on for my buddy. I edited my post after I read page 7 from Simms with the update. I didn't think Trinity was compatible yet. Gonna send him the link!
[Nexus S Android Development] simms22:
hey, its my favorite nexus s user by proxi :D
[Nexus S Android Development] mtw4991:
yeah, I like trying to eff up HIS phone more than mine:D;)
[Nexus S Android Development] Jrbourque:
Any suggestions on what temp should be set at in setcpu before lowering the speed using profiles?
[Nexus S Android Development] jlevy73:
I don't have it setup on my NS but with my N1 I believe it was 50C.
[Nexus S Android Development] Jrbourque:
Awesome I had it 45c so that's cool ....thanks for reply
[Nexus S Android Development] barbarossa2:
Love the boot animation sweet "winning''
[Nexus S Android Development] kaimyn:
Wow - this kernel is fantastic. I was running Netarchy 1.2.7 on CM7 #11, but the switch to Honity is amazing. I wasn't able to run 1.4 on Netarchy or Trinity, but so far, it works great on Honity. Also, my quadrant score went from 2800 to 3600 and the phone clearly runs a lot more smoothly.

Great work!
[Nexus S Android Development] jlevy73:
Another satisfied customer.
[Nexus S Android Development] Serious_Beans:
So most people who can't hit 1.4 can with this kernel? Why is that, are the voltages raised even more than the VMax kernel or is it just more efficient code? or is the overclock implemented in a different way? Just curious.
[Nexus S Android Development] nickwarn:
I cant boot in to clockwork recovery from rom manager on Honity 14 2.3.3. Itryed to reinstall twice, no luck. I have to boot in from the bootloader to clockwork recovery. No big issue but i thougt it should be reported as it happens eevery time for me. Anyone else?
[Nexus S Android Development] Vulpix:
Anyone here has any comment on the battery life of this kernel? I've been having very good battery life with Netarchy, but the performance on this is much better, and my phone runs hotter too.
[Nexus S Android Development] morfic:
Now that's some feedback! Thanks :)

Sent from my Nexus S
[Nexus S Android Development] CB620:
I'm stuck at the boot screen when I flash the kernel had to restore.
[Nexus S Android Development] morfic:
unplugged at 4:15pm, got out of work (bad "Edge to nothing" reception) at 3:45am, mild use, 70% battery
[Nexus S Android Development] dario3040:
Weird...

With 2.3.2 it didn't work.

But with 2.3.3 it worked perfectly.

Im not using 2.3.3 because it has bad colors, and the 3d app drawer is blurry.

2.3.2 > 2.3.3 :eek:
[Nexus S Android Development] CB620:
no matter what rom i try 2.3.2 is the way to go. no mishaps no bugs. :D
[Nexus S Android Development] vroomr4:
I was on a long call (~1.5hrs) and phone bootlooped at the honeycomb screen (kept replaying the animation for well over 2 minutes). When I pulled the battery and turned it back on, it froze on the honeycomb animation. Had to reflash #11. Phone was clocked to 1.4ghz. Did not feel noticeably warm.
[Nexus S Android Development] Vulpix:
I am having issues with superuser not working after a few hours with this kernel. I've done a full wipe, including a dalvik and cache wipe, no titanium backup restore, but the problem still exists. Could be 2 hours, or 3 hours later, and I will be unable to get SetCPU or anything that requires superuser to work. Using the latest 2.3.3 CM7 #12 with the kernel.
[Nexus S Android Development] avetny:
I love morfics kernels......really good guy, really performance

kernels, but all kernels after 3-5 restarts gonna gives root problems....internet data some times freez for no reason.

Now i using only Netarchy kernels. No roots problems no Bluetooth issues.