yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] dsellers2:
Its wierd you can run and under volted over clocked kernel that steps close to 800 but can't do an UV at 800. What happens when you run it? Have you tryed a fresh install.

I always delete the system module folder then the etc init d folder. Goto recovery format system and cache. Delete cache and dalvik then install ROM then kernel. Then fix permissions.

Never have issues on Any kernels never have to do a fresh install. Get to keep all my setting. Out may be over kill but only takes a minute longer. And it makes sure nothing I'd lingering from past installs.
[Nexus S Android Development] dsellers2:
Not saying you have to do this but its worth a shot. ;)
[Nexus S Android Development] gotjazz:
Oh believe me I've tried all that and then some. Guess the teuv voltages are just a bit too low for my phone. After all that's what the e stands for
[Nexus S Android Development] simms22:
The latest Trinity kernels for the Nexus S and the G2x, all on one site now http://www.derkernel.com/ bookmarket it
[Nexus S Android Development] window7:
I did that once. Haha. Freak me out! With setcpu and tick of "set on boot".
[Nexus S Android Development] simms22:
haha.. fun!

did you just flash a slower kernel over it?
[Nexus S Android Development] melvinchng:
"euroskank kernels available!

morfic makes kernels for this device:

xda thread"

Is kang using uv kernel? Or stock voltage?

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] simms22:
stock cm. all the kangs include the stock cm kernel, not uv'd. Trinity is just an option that we end up taking :D
[Nexus S Android Development] mikeazores:
+ 1

Enviado desde mi Google Nexus S usando Tapatalk
[Nexus S Android Development] dsellers2:
Well, that just sucks.
[Nexus S Android Development] AndroidMilos:
Wow, love this kernel. Put in in with my NScollab1.0.4 and it is steady and rock solid stabil at 1.44 (using Proton to control the voltages). Getting consistent 4500 on the quadrant scores.

Only one problem though. The bottom 4 control buttons stay lit all the time. Anyone know what the problem may be? Thanks in advance and thank you for such a great kernel.
[Nexus S Android Development] gotjazz:
Hrm proton seems to have quite the placebo effect. (only for Netarchy ana matrix kernels)
[Nexus S Android Development] saranyan:
Have a problem, Everytime i receive a call, the screen is blue and grey stripes, and nothing is seen. If i lock and unlock the screen, It becomes normal. thought it was a ROM issue, But happened in two different roms with TEUV kernel. :(

Anyone knows why i get this problem?
[Nexus S Android Development] MarkGbe:
you guys all all big babies, LOL. I just run T144 full time and give my battery the finger. it's fantastic. :)
[Nexus S Android Development] r0adki111:
Bwaaahaha!

Hey question for morfic. On the OC kernels, does the bus speed scale up and down? Or does it stay the same? Are the voltages adjustable too?
[Nexus S Android Development] al_madd:
using TEUV...

keep lagging if i used conservative gavernor.....
[Nexus S Android Development] king23adrianc:
its always been told to use ondemand
[Nexus S Android Development] morfic:
Use ondemand if you want a responsive phone.

Conservative aims at scaling over more steps up and down.

It will never feel snappy, it wasn't meant to be.
[Nexus S Android Development] al_madd:
Is it ondemand consumed more battery than conservative??
[Nexus S Android Development] morfic:
Poorly configured it could be.

After flashing it will be both snappy and kind to your battery.

Play with the numbers and you are on your own.
[Nexus S Android Development] al_madd:
sorry...still new in this..

playing with what numbers??
[Nexus S Android Development] shubu000:
Ondemand is pretty good for me just go to advanced in setcpu.. or most CPU frequency setting apps and set the sampling to be 15000 and power up threshold to be 98

Been very good for me these settjngs
[Nexus S Android Development] Corra:
with the T144 kernel, at 1GHz the bus is still at 200MHz?
[Nexus S Android Development] Jonathon Grigg:
Running the TEUV from the OP, many times today I have had an issue where the back key "presses itself" (ie it dims and vibrates, and goes back as if you were pressing it but I wasn't touching it at all). The issue has appeared maybe once in the past, not sure which kernel though. Today its happened easily 4 times, even after multiple reboots. Now I am not sure it's a kernel issue, its possibly a hardware issue as I've had issues with all 4 keys not lighting up in the past (before Ezekeel mods I mean). Has anyone else experienced this issue? I imagine its a bit like the search key bug that was meant to be fixed in 2.3.6 if anyone has experienced that.

Thanks guys!

Sent from my Nexus S
[Nexus S Android Development] superfloup:
It sounds like an hardware issue ... I didn't experienced it.
[Nexus S Android Development] Jonathon Grigg:
Thought as much, thanks anyway.

Right for everyone else, as not to further clog up the thread, maybe only reply to my point unless you have experienced the issue yourself. It is a development thread after all, and this seems like a hardware issue. If it helps, I have a Samoled i9020T unlocked from T-Mobile, it would have been one of the first batches too.

Sent from my Nexus S
[Nexus S Android Development] Roscopcoletrain:
Decided to try teuv and i must say, I'm impressed. Pretty smooth. I'll give it a few days and see if this becomes my dd.
[Nexus S Android Development] morfic:
Major case of deja vu, until I remembered why.

Doubt you will want to give it up.
[Nexus S Android Development] morfic:
Time to rebase.
[Nexus S Android Development] matt2053:
Yes hardware issue that affects many Nexus S units. I sent mine for replacement because of this issue and fortunately my new Nexus has no problems.
[Nexus S Android Development] belair56:
major deja vu is right !

http://www.youtube.com/watch?v=XZ5TajZYW6Y

:eek:
[Nexus S Android Development] dsellers2:
I'm not following, what do you mean?
[Nexus S Android Development] morfic:
Letting cm do the feature maintenance, focusing on "building right" and UVOC
[Nexus S Android Development] mike216:
Can you tell me the exact kernel version your running
[Nexus S Android Development] JmPTaz09:
Sounds sound ;)
[Nexus S Android Development] albundy2010:
I had the same issue before. I am not sure what kernel I was running but I think it was mathkids 5.5 and a cm nightly. Phone was working fine then that behavior started rendering it useless. I nandroided back to a prior nightly with same mk 5.5 and it went away. Then restored the backup of the system with the issue and wiped cache/davlik and flashed mk.5.5 again and it still went crazy. I then dowmloaded'the latest nigntly at the time,wiped the phone and did a clean install. No issues on the stock kernel for the couple of mins I had it on and no issues with 5.5 either. I have not had that behavior since. It may not be hardware. I have no idea what actually caused the issue but a nandroid restore/clean install fixed the issue on my 9020t
[Nexus S Android Development] simms22:
sounds like a file corrupted
[Nexus S Android Development] AndroidMilos:
I am using 2.6.35.14-Trinity-G6029352. It seems to have cleared up today though. The only thing I did was to go to "screen Timeout" and reduce it to 15 sec from one minute. (Screen timout under Display settings). It might be

just a coincidence-dunno but the bottom row (4 control keys) now appear to be working right. The bottom lights now go right out when the screen goes out and no "dancing" of lites from those bottom 4 keys.

Well, spoke too soon. Bottom 4 keys lite up and did the dance hahahah. By the way I am also using NSCollab 1.0.41
[Nexus S Android Development] Jonathon Grigg:
Thanks very much, I don't think I will be able to send mine in though, but that's alright. Shipping back to America is just too expensive :(

Sent from my Nexus S
[Nexus S Android Development] morfic:
Any pre-2.3.3-voodoo color lovers who would be so kind and test a TEUV with punchyesk colors for me?

And give me some feedback on colors?

Thanks,

Daniel
[Nexus S Android Development] thedudejdog:
I'll test it, but my ns4g is really picky when it comes to teuv.
[Nexus S Android Development] morfic:
http://goo.gl/0Wixw TEUV-452-NS-24092011-lazy-punchy.zip

Lazy governor by Ezekeel included, Ondemand default.

no-frills cpu control supports governor changing.

This may very well be default real soon.

But hey i wanted you to test the -punchy aspect of it.
[Nexus S Android Development] r0adki111:
Downloading now...
[Nexus S Android Development] morfic:
http://goo.gl/xKTKs TUV-452-NS-24092011-lazy-punchy

In case your phone really hates TEUV, here is TUV 1.0GHz, meaning 200MHz (stock) bus.

Try lazy, if it doesn't slurp battery juice, it'll be default
[Nexus S Android Development] thedudejdog:
Got it booted, colors are nice. I like the punchy colors. Don't know about the lazy governor, but the colors are nice.
[Nexus S Android Development] melvinchng:
Nexus s too? And i9023?

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] r0adki111:
Everything seems as smooth and snappy as ever.

I have a screen off profile set to 100/400mhz. Normally when I turn off the screen (while leaving system monitor on to show me the history of the cpu) and turn it back on I notice that the cpu stayed solid at 400mhz the whole time the screen is off, it never actually goes any lower. Although it is going lower while just watching it with the screen on. I have always thought that was weird. The main thing I am noticing now with lazy is when the screen is off it stays down at 100mhz the whole time. Or at least for the few tests I just did, I did not try with streaming music or anything like that. Very responsive and fast still. I hope this doesn't kill battery because this may be better than ondemand.
[Nexus S Android Development] simms22:
booted. benched. running fine while tethering wirelessly to my laptop and listening to pandora :)

teuv 880/880 lazy. quadrant #6..
[Nexus S Android Development] r0adki111:
Dang! What are you doing to get 3500? I am only getting 3143 after 6 benchies.

880/880 teuv with lazy governor.
[Nexus S Android Development] simms22:
the spinich that i feed it maybe :confused:

just kidding. im running the latest cm7 kang by taichi, it looks like youre running miui. that could be a difference.

try it again after a reboot.
[Nexus S Android Development] melvinchng:
Lazy vs on demand. (1ghz)

Lazy works badly at 1000/1000 quadrant. But on demand works well.

Lazy works better on 100-1000 than on demand 100-1000

Quadrant on on demand 1000/1000

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] r0adki111:
Haha! Nice.

Seems to get better results on 100/880 rather than 880/880 with lazy that is, haven't tested it against ondemand.
[Nexus S Android Development] simms22:
hey, wait a minute.. are you stalking me and my ns :eek:
[Nexus S Android Development] SA-07:
:D
[Nexus S Android Development] thedudejdog:
this one works good. No reboots since you posted it. I've been running tuv from Aug 30th and this one matches the stability.

Good work
[Nexus S Android Development] FuZZ__:
nice! but simms22 is really the pirate droid ;)
[Nexus S Android Development] Bamdroid:
Thanks for the new kernel. You all rock.

私のネクサスSから送ら
[Nexus S Android Development] albundy2010:
Everything seems fine so far on the TUEV version with lazy. This one reboots for me as well. Others would not so yay!

The colors I do not know. I am simply not sure how to even test it to be honest. Do I change the color profile in voodoo control app to normal? Or does it use the testing colors regardless of that setting.
[Nexus S Android Development] morfic:
This was build from main branch, so what is in OP, testing wasn't so hot, I'll belay that Idea, do other stuff, like lazy.

Fyi:

Was going to add pre2.3.3voodoo colors to this, but the punchy hack looks plenty good and doesn't get rid of the adjustability of voodoo color V2. Changing whitebalance to something cooler was my main interest, this is pretty close to what I had in mind, is stupid simple, punchy default, without app.

Multipliers need some tweaking for my taste, but will be slow progress.
[Nexus S Android Development] Bamdroid:
This kernel + euroskank kang = 1 lazy skank.

私のネクサスSから送ら
[Nexus S Android Development] melvinchng:
Lazy works badly with multitasking. When I turn off my screen while doing something, it just freeze my phone.

When I'm in my car, I can't switch my screen on. Then I tried to open my cover. But now, it turn my phone on with Google.

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] simms22:
did oppenheimer speak to you? :eek:
[Nexus S Android Development] morfic:
How to test for colors:

Do you like them?

Yes:__ No:__

Please check one.
[Nexus S Android Development] tehgeekguy:
Yes.

They look a lot better than the old ones, atleast to me.
[Nexus S Android Development] simms22:
Yes:__ No:__ Groovy:

X
[Nexus S Android Development] albundy2010:
Yes. Just was not sure if I was actually looking at the test colors.
[Nexus S Android Development] melvinchng:
It speaks silently. "I'm out of fuel"

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] thedudejdog:
Yes
[Nexus S Android Development] king23adrianc:
hmm i would choose

Yes:__ No:

X

i think its too dark in a way, i m using samoled btw

so i decided to pick between 2.3.3 and punchy.. Alternate setting :cool:
[Nexus S Android Development] morfic:
http://goo.gl/YPgx8 TUV-452-NS-24092011-lazy-def-punchy.zip

Lazy default governor, not sure the color tweaks are much different, next build will tell.

uninstalled voodoo app \o/
[Nexus S Android Development] king23adrianc:
got TEUV?

i like it over TUV lol
[Nexus S Android Development] morfic:
I was going to post the TEUV link, then i remembered, you are ^THIS guy.
[Nexus S Android Development] king23adrianc:
LOL.. but ur updated one just have colour changes or actual kernel stuff??

and ur MEAN.. u just picked on me already :( lol
[Nexus S Android Development] morfic:
http://goo.gl/txJwO TEUV-452-NS-24092011-lazy-def-punchy.zip
[Nexus S Android Development] morfic:
Lazy governor is default, fixed code, it wasn't building as default before.
[Nexus S Android Development] king23adrianc:
okay! flashing again ;)

u kno what morfic... i will keep punchy for now since its all your hard work after all :)
[Nexus S Android Development] Bamdroid:
Yes:_X_ No:__

私のネクサスSから送ら
[Nexus S Android Development] morfic:
http://goo.gl/F4nz5 TUV-452-NS-24092011-lazy-def-punchy-blue.zip

slight tweak to earlier color fix, this one is going towards my taste, the slow progress i was talking about, that's one step closer towards that.

Very subtle change, most might not notice a difference, maybe you feel it's just brighter

btw, those using voodoo control app shouldn't see a change in colors as the app would restore your values just after boot up.

which is the beauty of changed defaults in voodoo color v2, doesn't break the app like using the full voodoo v1 files :), but gives me what i find "right" w/o need to run the app.
[Nexus S Android Development] melvinchng:
How about tuv 11 with stock bus?

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] morfic:
there is no such thing, this is why TUV is 1.0 GHz
[Nexus S Android Development] r0adki111:
For some reason this breaks my wifi. Says error in settings. I tried wiping everything, flashing rom again, and still no go.
[Nexus S Android Development] simms22:
did you redownload it and try again?
[Nexus S Android Development] r0adki111:
Ya, a few times. The really strange part is the first kernel with lazy governor worked and when I try to flash that to a nandroid of the same as it worked with earlier, it breaks wifi too.
[Nexus S Android Development] dario3040:
Didn't break WiFi here, just synced 300 songs on Spotify.
[Nexus S Android Development] shubu000:
Just tried lazy on fruit ninja, massive lag, no such problem with ondemand, on tuev
[Nexus S Android Development] Jonathon Grigg:
I have I feeling that this may be caused by the time in current state that is the new feature in lazy, to stop the scaling from happening so rapidly that the music 'cracks' so to speak. By the sounds of it, Fruit Ninja may have very fast and high CPU demands, which this new time delay just can't handle. I'm not sure what can be done easily for this, maybe Ezekeel can see if there's like slower steps for lower freqs and then sorter, faster steps for the higher ones, to cater for this. Just my thoughts though, don't quote me on it being completely correct.

Sent from my Nexus S
[Nexus S Android Development] dario3040:
Nope, runs without lag at 200-400 Mhz
[Nexus S Android Development] matt2053:
For me TEUV sometimes freezes when I'm watching Netflix for a while. Image freezes and sound goes da-da-da-da-da-da-da.... etc until I pull the battery. Only sometimes, and only when watching Netflix.
[Nexus S Android Development] melvinchng:
Playing need for speed hot pursuit. Give me a freeze while I was exiting my game. The freeze is a bit strange. It didn't hot reboot. It start the boot from Google.

Tuv

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] matt2053:
Wait did it freeze or did it reboot? When I said mine freezes, I mean the image on the screen is stuck and none of the buttons including power button work. I have to pull the battery.
[Nexus S Android Development] Roscopcoletrain:
24hrs running op teuv and mostly great, but got a few random reboots & frozen screens with the backlight on. Sometimes plugging it in will wake it.

May go back to tuv 11. Seemed like i had the least amount of issues with that.
[Nexus S Android Development] al_madd:
Im using TEUV..

sometimes getting freeze when im playing games(Air attack HD)

still dont improve my battery life...:(:(:(:(:(:(:(:(
[Nexus S Android Development] king23adrianc:
no freeze or lag or what so ever while just texting people, whatsapp, facebook

havent try games yet.. cuz i m at work :mad:

EDIT: i just open my restaurant cuz my food r all cooked. i m playing restaurant story haha!! but anyway, i don't see any lags in it, probably is not as high graphics as racing games or air attack lol
[Nexus S Android Development] dario3040:
:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(
[Nexus S Android Development] thedudejdog:
I like this one. Uninstalled the voodoo app. I can definitely tell it's bluer. Only slightly.
[Nexus S Android Development] coloxim:
Sometimes freeze with maps and some games..

Inviato dal mio Nexus S usando Tapatalk
[Nexus S Android Development] Corra:
I'm using TUV and seems to work fine. It would be possible to have a 240MHz bus like T144 even at slower clock speeds?

Inviato dal mio Nexus S usando Tapatalk
[Nexus S Android Development] albundy2010:
I dont think lazy is causing the lags in maps. Maps seems to just be lagging on the tuev test kernel no matter what for me.

It is lagging no matter what governor is in use. Ondemand 880/880 still lags.
[Nexus S Android Development] morfic:
Any speed you can divide evenly into 240.

If your phone doesn't like 1440 it likely wont like 1200 or 960 either.
[Nexus S Android Development] Igotsanevo4g:
Has anyone tried the latest TEUV with the NS4G? Only says ns in the link so I'm hesitant :p
[Nexus S Android Development] adewey234:
This coloring is good, but I think one of the colors might be too low, I am seeing the green screen right before the screen sleeps. This happens when I set the voodoo calibration colors too much to the left.

In respect to the laginess with lazy, I think that a 1.1ghz would probably solve that with 220mhz GPU. What do u think morfic? Also what do you think about 222mhz GPU? I think that maybe its a ratio that makes the overclocking work properly. 1.1ghz is different from stock by .1, which is 11% difference. So quite potentially 11% increase from GPU would be 222mhz. U think that would be possible?
[Nexus S Android Development] king23adrianc:
morfic,

is the new TEUV running 220mhz bus/gpu?
[Nexus S Android Development] matt2053:
Your math is a little off. 1.1 ghz is a 10% OC and so is 220 on the bus.
[Nexus S Android Development] morfic:
NS, all NS, the 4G aren't second class citizens.

Everyone is included.
[Nexus S Android Development] morfic:
Thanks.
[Nexus S Android Development] morfic:
Your ill math aside, there will be a T11, it'll likely need a different setup than the UV kernels. So won't be in TUV category.

Have you tried the -blue kernel wrt the greening?

I don't see it here ....running -blue.
[Nexus S Android Development] simms22:
for those people having reboots..

if using cm or similar, go to cyanogenmod settings, performance. make sure that surface dithering is not enabled, and that allow purging is enabled. this could be a huge difference.
[Nexus S Android Development] adewey234:
Sorry, a retarded moment. Hey morfic could you compile a kernel for me thats 1.11ghz and 222mhz gpu? Please so I can test it :)

*edit*O and yes I was using the newest kernel u posted with the blue, that happened with the green screen.
[Nexus S Android Development] Igotsanevo4g:
Awesome. No more sitting in the back of the bus lol :D
[Nexus S Android Development] khartaras:
Morfic, I made a bootsplash for Trinity. If it's crap, just tell me. You probably won't use it because it wouldn't fit well with Rascarlo's boot animation, but still...
[Nexus S Android Development] sinik420:
Posted in kang thread as well. My phone rebooted after receiving a text message, booted and had process.phone fc. After going to mobile settings, it had cdma options listed but would fc before I could get a screenshot. If its not obvious, I'm on a GSM version of nexus s. On teuv lazy

sent from my nexus s on a kang from simms
[Nexus S Android Development] dsellers2:
Loving the latest teuv with lazy
[Nexus S Android Development] formaldehyde:
Thank you very much, morfic!

The latest TEUV seems to work very well on my phone, too.

The TEUV from OP used to FC some apps and get into a bootloop after less that two days of uptime. I haven't been on this one for that long yet, but it seems and feels promising. Or maybe it's just the fact that I disabled dithering and allowed purging of assets as instructed earlier today in this topic.

Oh, and lazy governor is great, too!

What I am missing though are the BLD updates for i9023.
[Nexus S Android Development] ogbreds:
I haven't had any problems on stock deodexed 2.3.7 with TEUV using lazy governor.
[Nexus S Android Development] Roscopcoletrain:
Will try this
[Nexus S Android Development] morfic:
Get the source and build it.

Are you using voodoo control app right now?

Are you using screen off animation?
[Nexus S Android Development] pupy991:
Is it just me or is it a 'feature' of the Trinity kernels that my Voodoo color settings get disabled after locking and unlocking my Nexus S?

Every time I boot it everything (including my Voodoo color settings) is just fine, but when I lock + unlock my phone then, the colors are suddenly 'washed out' again, just the way they were before I changed them with Voodoo.

To change the colors back to Voodoo colors, I have to reboot my phone.

Any ideas?

I'm using the latest CM7 nightly with the latest Trinity 11 UV test kernel (I tested a few Trinity kernels, they always disable my Voodoo color settings after locking+unlocking the phone).

Greetings,

Pupy
[Nexus S Android Development] simms22:
do you have the latest voodoo app? mine never does that.
[Nexus S Android Development] pupy991:
Hmm strange...I'm using version 1.0.7 which, I think, is the newest one.
[Nexus S Android Development] simms22:
im using version 2.0 beta4. anyone else have this issue?
[Nexus S Android Development] pupy991:
Just did a full wipe, no difference.

I will try Voodoo Plus 2.0 now, hopefully this will fix it.
[Nexus S Android Development] simms22:
let me know..
[Nexus S Android Development] pupy991:
Using newest Voodoo Control Plus now, does not fix it either.
[Nexus S Android Development] simms22:
weird... :confused: