yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] simms22:
try redownloading the kernel, then reflash it. wipe dalvik before you flash.
[Nexus S Android Development] pupy991:
I have to use ogdobbers kernel again, as there are no such problems in his kernel.

Although we could not find out how to solve my problem, thanks for your help simms! :)

I would appreciate if you could inform morfic about this bug,maybe he can find out its reason and solve it, as I would really like to use this kernel (including always working Voodoo colors).

Greetings,

Pupy

Edit: I always wipe dalvik-cache before flashing a different kernel.

However, I just redownloaded the kernel, wiped dalvik-cache and flashed it again, no difference.
[Nexus S Android Development] simms22:
i have let morfic know already. but you are unique, neither of us has ever heard of this issue. there is some sort of variable(s) involved. if you do have a chance to redownload the kernel and reflash, please do. it could have been as simple as the voodoo module corrupting during download.
[Nexus S Android Development] simms22:
just read your edit, now im saddened :(
[Nexus S Android Development] pupy991:
I'm saddened as well.

By the way, I would have been very surprised if it would have worked after a redownload, because I've already tried several Trinity kernels and always got the same error.
[Nexus S Android Development] morfic:
Lock and unlock.

Just pressing power to screen off and to wake phone up?
[Nexus S Android Development] roshga:
I think I know why the latest uv11 is a 'special version', my phone is charged to 100% for the first time :D

great kernel, really smooth.. battery feels a bit worse then uv11-nsu, but I have to check it again coz I have a feeling that fancy widgets did some bad things yesterday :o
[Nexus S Android Development] dario3040:
I think that only affects the framerate, but it might be worth a try :P (for him of course)
[Nexus S Android Development] tmello56:
Anyone else experience soft reboots when charging and trying to use your phone? The kernel works great as long as I'm not charging, but plug it in, and boom I get a soft reboot.
[Nexus S Android Development] Bamdroid:
12hrs n battery at 51%. Moderate usage..(was at work but still text/twitter/a little XDA n some web browsing) this UV11 special version is pretty bad ass...

Got 26hrs out of it yesterday..
[Nexus S Android Development] martinsjt:
Hello,

Great release, for me the USB issue is solved with this new special edition, also very smooth and fast.

Nexus S I9023 S-LCD Version with SuperAosp 8.6

Thanks.

Best
[Nexus S Android Development] pupy991:
Yes, that's what I mean.

After pressing power twice (turning screen off and on again) my Voodoo color settings are gone and the colors are washed out again.

Any ideas?
[Nexus S Android Development] matt2053:
I think he was just joking, making fun of himself. He doesn't really want an 11% OC kernel ;)
[Nexus S Android Development] morfic:
Bless your little kanger heart.

Which kernel do you use?
[Nexus S Android Development] morfic:
I knew that :P
[Nexus S Android Development] reddv1:
Does disabling dithering reduce the image quality or does not matter on the nexus s? What does purging do in layman's terms.

Sent from my Nexus S
[Nexus S Android Development] Ezekeel:
I am still running CM 7.03 (2.3.3) on my device and I just checked and dithering is enabled and purging disabled. However I never had any problem with reboots since I switched from the CM kernel to the one in my sig. So it seems this either is a regression with CM Nightly (was something actually changed?) or the problem is somewhere else and changing these settings just gets rid of the symptoms while the problem itself still remains.
[Nexus S Android Development] simms22:
it says right on the settings..

(btw, screenshot from my original droid)

---------- Post added at 08:09 PM ---------- Previous post was at 07:51 PM ----------

maybe so.

but i say it because ive been using these settings for better performance for a long time now, and i dont get issues with reboots. last night i was reminded by someone who suddenly started getting reboots with dithering on and purging of assets off. theyve always had the same settings as me. but, after a wipe, dithering was on and purging was off. and they were having reboots. so i thought i would suggest people with reboots try my settings :)
[Nexus S Android Development] Roscopcoletrain:
Just had two reboots. Doh lol
[Nexus S Android Development] r0adki111:
I just wanted to put this in here for the record, in case maybe anyone else has this issue.

When I use the teuv kernel with lazy gov, it breaks my wifi upon reboot (says error in wifi settings). There is one exception, if I turn wifi off before rebooting into recovery to flash the kernel, then wifi is fine when I get back into the os.

Now when I go back down for another reboot for any reason (even if I don't flash anything and just do a normal reboot) the wifi is broken upon re-entry into the os.

I can use teuv and tuv miui themed kernels stable all day long without problems. The teuv and tuv regular kernels are unstable for me, I don't know why.

I am looking forward to an official stable release of teuv-lazy. I will be all over it. :)

For now back to teuv-miui.

Has anyone compared battery life between teuv-ondemand and teuv-lazy?
[Nexus S Android Development] sinik420:
This has happened to me continuously on miui long before lazy and if you search, you can see that it is not a new issue. I do like miui, not as much as cm, but a fix would help me like it more.

sent from my nexus s on a kang from simms
[Nexus S Android Development] albundy2010:
He is speaking of the kernel with the miui boot animation. Not the miui rom.
[Nexus S Android Development] sinik420:
I've reread his message and see that mentioned no where. I am merely saying I've had that same problem on miui and miui only. Perchance he left out his use of miui

sent from my nexus s on a kang from simms
[Nexus S Android Development] r0adki111:
Sorry I may not have been clear. I am using brainmasters miui and teuv miui themed kernel. I have issues only when using the kernels with lazy governor.
[Nexus S Android Development] sinik420:
It was not unclear to me, but that's because I've had that very same problem with miui from day one using any kernel. So because it is mentioned long before the creation of lazy, I would have to say that it is not because of lazy but that it may merely carry in it the same problems that came before it

sent from my nexus s on a kang from simms
[Nexus S Android Development] khartaras:
I use TUV11. If you wanna use the image though, I'll make an improved version this afternoon.

and here it is.
[Nexus S Android Development] adewey234:
Sorry had to go to work. I uninstalled voodoo, and it still does it. I do have the screen off animation off. It does it for a second or so before it loaded the launcher, but then it stopped. I think it might be frequency related, like when it gets too low, it screws up.

And for the kernel, no I was not joking lol, yes I had a retarded moment, but I want to screw around with frequency combination between cpu and gpu. Are you talking about your kernel source, and if so, what file do I modify to change the frequency. Its been a long time since I have done anything with kernels beyond unpacking them and repacking them. Do u have a crash course on kernel compiling lol, or somewhere where I can read up on the commands and how to put modules in like ext4 and BFS and ****?

Much thanks for all the hard work you put into trinity/honity etc. I've been following your work since the beginning of your NS adventures.
[Nexus S Android Development] Kraenesk:
Some day Morfic will make my dreams come and and adjustable voltages for set CPU. Or maybe not. Its his kernel. I love everything about them...except my phone can't seem to handle the voltage with the bus changes.
[Nexus S Android Development] coloxim:
The last teuv 200 Hz bus..and 1ghz was perfect...i love the color too..but sometimes freezes my phone

Inviato dal mio Nexus S usando Tapatalk
[Nexus S Android Development] al_madd:
TEUV with 1Ghz??interesting....

can you give me the link please..
[Nexus S Android Development] catchsomezz:
has the past few nightlies (203-ish and above) broken the backlight dimmer from ezekeel. the touchwake still works, but i can't seem to get the backlight dimmer to work after nightly 203 or so
[Nexus S Android Development] dario3040:
I wouldn't count on it...
[Nexus S Android Development] treUse:
Wow, morfic, thank you :D

Using the 1109-T144 my phone isn't only flying. The battery life is amazing as well, at least for a 1.44 ghz kernel.

And one more thing. One of the primary gripe I had with trinity was the god awful splash screen, but now it's more minimalist and I actually quite like it :). Keep it this way!

Oh, and it's the first time a performance kernel hasn't crashed my phone. Not to mention the uptime is over 20 hours without a crash.

Thank you ;)
[Nexus S Android Development] MarkGbe:
so what is the deal with the interactive gov? Is the only downfall that it eats battery? My phone is pretty snappy with interactive, and no other issues. Been using T13-Any-NS+4G-30082011.
[Nexus S Android Development] kenvan19:
After initially getting phenomenal battery life from the experimental TEUV kernel with the lazy governor a few odd things have happened. First, yesterday when I went to work my phone was at 70%. While I'm at work, I don't use my phone at all. It sits in my pocket with data enabled and yesterday was not a particularly eventful day. Maybe three texts and no push notifications yet when I went to have a cigarette and read some news on my phone it had dropped down to 37% in 2.5 hours with no use. This morning, after taking my phone off the charger it started dropping relatively quickly. It was down from 100% to 88% in about 30 mins but then I again put it down while I was at work. I again went out for a cigarette just now and its down to 34%. So far this morning I've checked XDA once and read half of a cracked article. Its been set to min 100 max 880 with the lazy governor and this is probably the first time since I bought this phone that I'll have to charge it midday just to get through the day, including all the time I had it OC'd to 1.6GHz. Not sure whats going on but wow.
[Nexus S Android Development] simms22:
sounds like crackflasher syndrome(from flashing too often). poor guy :eek:

let the battery drain all the way, then delete the batterstats.bin file and charge all the way. that should take care of it.
[Nexus S Android Development] treUse:
Any news on an update of t13? Can't stand the splash on that one :p
[Nexus S Android Development] sinik420:
Lol I guess morfic can rest easy knowing the biggest complaint is the bootsplash

sent from my nexus s on a kang from simms
[Nexus S Android Development] treUse:
Haha, true... t13 is rock solid on my phone, and performance stellar, so yeah... nothing else than the damn bootsplash...
[Nexus S Android Development] jjhrrsn:
How does one locate this I have es file explorer
[Nexus S Android Development] simms22:
/data/system/batterystats.bin/
[Nexus S Android Development] morfic:
I was gonna offer you a khartaras kernel, but I'm not building any TUV that are 1.1ghz right now.

1.0 for khartaras kernel with this logo?
[Nexus S Android Development] morfic:
Are you setting it to 1.44ghz, for safety it boots up 1.0ghz.

If not, you ran 1.0 ghz and loved it, in which case TUV would be what you want.

Just asking, sometimes people don't look at bootup frequency.
[Nexus S Android Development] khartaras:
oh my god. TUV10 with 220mhz bus? Special khartaras edition?

Sign me up!

Also, could you make the kernel info thingie (I forgot the name) khartaras@othris #666?

That would make me explode with content. :D
[Nexus S Android Development] morfic:
do you have this as png? .jpg makes it look pretty bad, redo it and save it in .png instead of .jpg if you have to
[Nexus S Android Development] morfic:
There is no 1.1 GHz with stock bus, nor a 1.0GHz with 220MHz bus.

But there is your TUV (1.0GHz/200MHz)

http://goo.gl/LQ9RL

I think it lacks a good ol' mushroom cloud.
[Nexus S Android Development] simms22:
what.. no takers? :eek:
[Nexus S Android Development] SA-07:
Start a bid ;)
[Nexus S Android Development] SA-07:
Never mind.... :/
[Nexus S Android Development] treUse:
I changed it :)
[Nexus S Android Development] melvinchng:
Trying it now. My xda app can't sign in for almost 24hour. Feels like dying...

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] khartaras:
Morfic, this thing is insanely fast :O

I love it more than anything.

:D
[Nexus S Android Development] martinsjt:
Hello,

So with T133 or T144 at 1Ghz the bus will always be at 200 MHz! Right?

Best.
[Nexus S Android Development] treUse:
Yes, that is correct.
[Nexus S Android Development] al_madd:
which one do you used?
[Nexus S Android Development] khartaras:
My special edition TUV 1.0GHz with 200MHz bus.
[Nexus S Android Development] coloxim:
Wow..very nice kernel..good!!!

But I've always the freeze when i play a game..

Inviato dal mio Nexus S usando Tapatalk
[Nexus S Android Development] shubu000:
hey morfic

i was just reading the nightly changelog and there's a bucketload of changes for the nexus S

are there anything that is going to be in their kernel that isn't in your epic kernel yet?

just wondering cos i've never seen that many nexus s related changes in a nightly before

thanks
[Nexus S Android Development] lgalkis:
there any change to see the 1,5 kernel for the nexus?
[Nexus S Android Development] r0adki111:
What would be the benefit of this over the tuv with 220mhz? I believe the miui themed one is 1000mhz/220
[Nexus S Android Development] Corra:
CPU clock = bus clock * multiplier

I don't know if it's possible to set 4.54545454545454etc. as multiplier (I guess not) but it's more likely 200*5=1000

Gesendet mit Tapatalk von Nexus i9023
[Nexus S Android Development] al_madd:
couldnt ask for more...

really impress with new TEUV..super fast,super save battery

just getting error with ezekeel mod, touchkey backlight dimmer...using spark mod manager..

kind of lagging...dont know how to describe...just dont like it..

Ok...i just plugged my phone to USB..and my phone reboot....!

before i charging my phone,my battery level is 20%,after reboot it suddenly become 40%..weird
[Nexus S Android Development] melvinchng:
The latest version is not stable. 260911 tuv... always give me a freeze when I'm trying to play hot pursuit

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] Naa Laa:
Morfic,

When are we getting new stable (OP kernels) updates for TEUV (08092011)?

I am reading good things lately with new add-ons (tweaks), cant wait for the stable version.
[Nexus S Android Development] iceman-001:
runs flawless here. Quadrant 3634 :-) with nightly 207.

Not bad for a UV-kernel with 1Ghz.
[Nexus S Android Development] melvinchng:
240911 tuv10 quadrant 4020.

No lag or freeze in any game.

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] khartaras:
Which game?
[Nexus S Android Development] dsellers2:
So Morfic od Simms, what's the verdict with the lazy governor? Is it staying as default? Has anyone been able to determine if its better than on demand?
[Nexus S Android Development] morfic:
Actually the CPU frequency is done first, then divided from there are all the other clocks for various areas of the SoC.

And the dividers are not float/double.
[Nexus S Android Development] morfic:
I tweaked lazy, the simms and khartaras versions serve as testbeds for those tweaks.

From 10000/90 to 15000/95 which is closer to ondemand.

Also tweaking min time in state.

So far it seems to serve battery better and will in a similar version be in regular Trinity, as default.

I might further simplify it.
[Nexus S Android Development] dsellers2:
Where might I find the Simms version...or the teuv version of tweaked lazy? Up for consumption yet?
[Nexus S Android Development] ellesshoo:
Are there links yet for builds that incorporate these tweaks? The TUV-blue from 2409 has been rock solid stable just like the TUV10 from August.
[Nexus S Android Development] morfic:
He is committing anything he can get his fingers on, most we already have, some don't help anything.

I was considering to rebase off of cm-kernel, but scrapped the idea, I didn't need cm-kernel as base for the last 9 months, not going to start now.

I will evaluate commits and use any I find useful. Right now he mostly turns it into a buzzword kernel, not every buzzword passes test of time.

Items like BFQ are outright atrocious to user experience, so I'm not wasting my time on it.

Others are frowned upon but people end up loving it if they don't know about it.

I recently said smartass ain't happening. I thought about it, I think I only tried v1.

That will never happen, but I will include SAv2 for people to try.

Feedback will tell if it's worth keeping.

But bottom line is, I don't care if I lack buzzwords, I won't include it just for the sake of having a stupid long feature list, no, not if it does nothing or impairs user experience. I am not going to exclude anything just because they are buzzwords either.

Hope this answer somewhat helped.

Daniel
[Nexus S Android Development] morfic:
Simms posted his on G+
[Nexus S Android Development] dsellers2:
Nevermore morfic, I found it on g+. ;) do you plan on doing

teuv? I thought I remember you saying that would bee the only one you under volt.
[Nexus S Android Development] petrochemicals:
How do I get rid of this boot animation and splash screen? I liked it how it was.
[Nexus S Android Development] Roscopcoletrain:
splash you cant, boot you swap the bootanimantion.zip file for one you want.
[Nexus S Android Development] petrochemicals:
Okay, is there a version of this kernel without the splash and bootanimation. It's a nice kernel, but I like to keep the stock look on my phone.
[Nexus S Android Development] Roscopcoletrain:
I'll say no, as Ive never seen it.
[Nexus S Android Development] treUse:
It's not possible unless you compile the kernel yourself.
[Nexus S Android Development] khartaras:
So these weren't one-off kernels? Do you plan on doing more Simms and khartaras editions? That would make me the happiest man in the world.

Also, lazy works great.

Just found out that Touch Wake is outdated. Please update it as the bugfix is pretty important. :-)
[Nexus S Android Development] treUse:
Looking forward to a T13 with lazy :)
[Nexus S Android Development] shubu000:
Thanks for the reply Morfic,

given the performance of your kernel that's what i suspected too
[Nexus S Android Development] ellesshoo:
Well, I like the idea behind lazy but after 2 days of using it on demand feels a good bit more "natural " or how I expect my phone to respond. Willing to keep trying lazy as it gets tweaked but for now it feels a bit too lazy for me.
[Nexus S Android Development] cheech87:
I have to agree. Every now and then I get a sporadic 1 second lag in window transitions, and have had a few reboots while using it every few hours or so. However, the reboots could be due to the recent updates to cm nightly (NOT bln related), so not blaming the governor on that just yet. testing nightly stability with on demand for the past 6 hours or so and it definitely feels smoother and more responsive, just like all of Morfic's previous kernels. (TUV-2409)
[Nexus S Android Development] al_madd:
I think we have the same problem here...
[Nexus S Android Development] JmPTaz09:
Getting strange BLN behavior on recent trinity kernels, including most recent test kernel from Simms22 google+... anyone else getting this and is there a fix? Running the latest kang, seems to blink properly on other kernels... otherwise seems to be running fast and smooth, but I need bln to work...

Thanks!

p.s. I have bln pro but uninstalled since it was baked into CM7... currently blinks a few times then turns off... or will go solid for a bit then turn off...
[Nexus S Android Development] morfic:
It's not baked into cm7 without their kernel.

You use Trinity. You control it how you used to.

If they modified bln in a way their control bits in rom interfere with another kernel that always had working bln, then what's broken? Not the kernel that had it first.
[Nexus S Android Development] morfic:
This thread is for Trinity kernels. You do the math :p
[Nexus S Android Development] cheech87:
This is currently a cm7 problem affecting nightlies after 203 (I believe) and any kangs based off them. See the discussion in the nightly thread.
[Nexus S Android Development] simms22:
im so glad that i dont use bln :p
[Nexus S Android Development] morfic:
I think I've seen people mention they build Trinity from source, you could ask who would hook you up with one with stock bootlogo.

I'm not even ruling out to add it as a build option back in. But not right now, I have enough to do just working on the things I'm interested in. But that sounds like a build option I'd eventually add.
[Nexus S Android Development] JmPTaz09:
That's the problem, seems they did such. Flashed your kernel right after system format fresh flash of the latest kang. Even without bln app installed, it blinks a few times then turns off. Installing pro gets it working but flashes crazy style. Seems it was working fine with a different kernel and I'll check again, but just seeing if anyone knew a fix.

P.s. funniest thing is that it seems to have worked itself out and is blinking again!
[Nexus S Android Development] noobiekins:
My phone can run TEUV and T144 fine but TUV11 has problems. any suggestions?

edit: Running CM7 RC1. Anything in the performance tab of the CM7 settings doesn't affect stability. In the TUV11 I get random reboots and freezes while on T144 my phone is snappy and has uptime of over 50 hours. When I'm on TEUV, My phone feels like 1ghz but with better battery life but I want the extra boost of speed that 1.1ghz gives over TEUV while not battery draining like T144
[Nexus S Android Development] stiffspliff:
Run teuv or t144 :)
[Nexus S Android Development] tehgeekguy:
I hear ya. I'm in the same boat. I see how it's useful, it's just not for me.
[Nexus S Android Development] omongo:
sampling_rate_min should be 10000 (same as ondemand, more tuneable, lazy default) and tweak only min_timeinstate, sampling_rate, up_threshold.
[Nexus S Android Development] chrlswltrs:
I just got used to knowing if I had a notification by looking at my phone without turning on my screen. I still miss having a colored LED but BLN is better than nothing.
[Nexus S Android Development] JmPTaz09:
+1, very helpful function, can't believe they built a phone without a notification indicator, kinda silly.
[Nexus S Android Development] morfic:
Noone touched the min, it doesn't do anything but limit your choices.

I feel like I missed the point you were trying to make?
[Nexus S Android Development] simms22:
Two Trinity Special Edition kernels for testing. Lazy is the default governor. Ondemand is not lazy :eek:

T144-CFS Simms22 Special Edition Kernel Nexus S/NS4G http://goo.gl/mELJo

TEUV-LOS Simms22 Special Edition Kernel Nexus S/NS4G http://goo.gl/dS9Am

there can be only one

thank you morfic!

see it boot before you try it --> http://www.youtube.com/watch?v=swSVWRzNv8M
[Nexus S Android Development] Bamdroid:
Phuck which do I try?!? Its like staring at two hot chicks with double D's n they both want you but only can choose one..grrrrr.

私のネクサスSから送ら
[Nexus S Android Development] simms22:
in this case, you can have both. just not at the same time :p
[Nexus S Android Development] morfic:
and NO, cfs does not relate to cfs/bfs, it occure to me too late that the acronym happens to sound like the scheduler.

acronyms are just for me to keep test kernels apart if there are more than one in the wild i want to know which gets better remarks and WHY it got them, usually not worth asking about what they spell out.
[Nexus S Android Development] jjhrrsn:
Testing teuv :)
[Nexus S Android Development] Bamdroid:
Dammit..k. Playing with 144 first..love it so far. And the new boot ani is sick!

I see the 666 kinda hidden...nice touch ;)

私のネクサスSから送ら