yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] albundy2010:
In s22 05 tuev I experience a issue with touch wake. I can't pinpoint the exact scenario where it happens though. It will get a two plus second delay before it wakes.

It doesn't happen on a fresh boot. It did not happen with deep idle working initially after the boot either. I.switched governors to on demand after it happens and the result is the same.
[Nexus S Android Development] red_skittles:
Flashed about 5 hours ago and Im still seeing a lot of time awake with the screen off. BetterBattery says that its been awake for 32min with screen on for 6min. Ive lost about 30% battery in that time.
[Nexus S Android Development] Lazat:
Morfic what voltages do you set for the bus to make 250bus stable in your thermite kernel?
[Nexus S Android Development] belair56:
Similar with TEUV-S22-05112011. But mine was with docs syncing, keep awake 2h 30m 28s. 25% never had this before. I also have "all" Google data to auto sync. Docs was the only one to wonk!

Maybe I have a bad file it could not sync.
[Nexus S Android Development] benrees21:
Ok been running 0511 and I have not yet had an SOD but I'm still getting a 5 second delay sometimes waking the phone. I'm confused lol.

Sent from my Nexus S on Morfic's TEUV Kernel and some help from Tapatalk!
[Nexus S Android Development] morfic:
You flashed 05112011 like i linked right?

B has patch #14 which includes key as wakeup source.
[Nexus S Android Development] morfic:
http://goo.gl/vv41Z make sure you flash b

It's acting real good.
[Nexus S Android Development] morfic:
You can check on git. I don't memorize them.
[Nexus S Android Development] Serious_Beans:
Hoping this and Bionix Rom will make my phone super awesome today!

Will test and post results, was using the regular 05/11 but since you say b is better I will give it a try.
[Nexus S Android Development] morfic:
I'm on bionix right now, wait for today's build.

But i admit, on ui it's your typical snappy aosp build.
[Nexus S Android Development] morfic:
Try to find instructions on how to restore it with ODIN in DOWNLOAD MODE.

I never needed them, so i didn't bookmark it.

Odin has the benefit of fixing screwy partitioning.

As long as it turns on it's not dead.
[Nexus S Android Development] Rem3Dy:
The sdcard not mounting is a known hardware failure that not even Odin can fix. Samsung has been replacing the motherboard with this issue. :(
[Nexus S Android Development] Serious_Beans:
Just saw Krylons tweet, I can't wait for the next build, I just full wiped but I might do it again later if you release an update today, for some reason if I don't full wipe I can't flash your newer kernels, I wipe dalvik and cache and I just get stuck at splash screen all the time, so every time you release a new kernel I end up doing a full wipe lmao.
[Nexus S Android Development] simms22:
b is acting really nice..
[Nexus S Android Development] caliban2:
well, flashed teuv-s22-05112011 last night (dalvik- & cache-wipe only) and so far it's perfect! no crash, no sod, just runs. (min_CPU still @200) batt-life is very good, but I'm not logging yet, just saying. ^^

i had it sitting at sim-unlock this morning, but i really can't say if it rebooted or if i fell asleep after rebooting from recovery... :D

anyhoo, I'm awake 10 hrs now and nothing went wrong in that time, despite heavy use. that's new!

PS: lazy clock is not gone.

PPS: great. why did i miss that b-version? Oo
[Nexus S Android Development] morfic:
cause i linked the non be directly in a post quoting someone, when i had already goo.gled the b link o_O

http://goo.gl/vv41Z This is B
[Nexus S Android Development] Zorrich:
DIDLE Stats

I do not appear to be getting deep idles stats, however my battery life seems great. I know Franco's kernel does not show the stats, is this one similar? Looked through last few pages of posts and at first glance it seems people are posting screenshots of terminal, so I am thinking they should work. Just looking for confirmation.

I am running the S22 "b" version. I have also tried the camera on/off trick, no difference either way.

Thanks.
[Nexus S Android Development] caliban2:
jup, thx. :)

installed it now (just cache & dalvik-wipe again), min_cpu @ 100 for a change and waiting what happens next. ^^ deepidle is working without camera as usual for me. it's charging now and once it's full, i'll start batman-log - wanna know how batt-life really is.
[Nexus S Android Development] red_skittles:
Yeah Docs was the biggest culprit for me too. Could be an issue with Docs rather than TEUV and didle. Are you using v1.0.30?

With TEUV-0511, my phone pretty much stayed asleep all night, probably because I turned off Doc sync. Battery drain overnight was less than 10% and that was with BLN
[Nexus S Android Development] benrees21:
Giving b a flash now. Thank you very much.

Sent from my Nexus S on Morfic's TEUV Kernel and some help from Tapatalk!
[Nexus S Android Development] morfic:
Anyone interested in a znTEUV with CV and LO?

still has no dimmers, no voodoo, no bln, but i love it already
[Nexus S Android Development] caliban2:
dunno, how should i know?! :p

no idea what zn, cv and lo stand for.

surprisingly enough, the second line is clear to me. Oo

edit:

nevermind, i think i got it: the trick is to look for threads started by ezekeel...
[Nexus S Android Development] Lalaca:
CV = Custom Voltage

LO = Live OC

Sounds cool, morfic. (Although I'd sorely miss Voodoo and BLN. :P)

Edit: Ah, you got it.
[Nexus S Android Development] caliban2:
yeah, just "zn" is still a ? for me. :)
[Nexus S Android Development] morfic:
true true

N is for new

z is so in CWR i can go up and flash it if i pushed to /sdcard/

CV is custom voltage

LO is liveoc
[Nexus S Android Development] sinik420:
Thought you were against custom voltage?
[Nexus S Android Development] morfic:
how can you pass up adjusting dvsint?

and liveoc w/o custom voltage would be a flop

when netarchy talked about joining forces, i would have ended up with voltage control anyway

So this morning i woke up, feeling good for the first time in months and i sat down and made sure it applies and works in the newer, cleaner git repo.

Since i was mostly using it to test deep idle w/o interactions of other options, it is still nice and bare.

Haven't brought it up to 2.6.35.14 yet either, but it will come in due time

i need to build thermites with CV-LO so people can lower voltages to see if lower == stable, not every phone needs more voltage to be stable, some need less.

But i can take it out if you don't want it.

EDIT: I'll just ignore any "what voltages should i use?" posts.
[Nexus S Android Development] benrees21:
No Voodoo really kills it for me. I'm not sure how live OC works but I will look it up. I'm used to CV so that's cool. Voodoo and I'm in :-)

Sent from my Nexus S on Morfic's TEUV Kernel and some help from Tapatalk!
[Nexus S Android Development] Maximilian Mary:
Yes. I would like to take the reigning champion of battery life, speed, and stability, and slowly turn up the heat until it screams.

What I would also like is direct access to your vast database of cpu clocks & voltages vs bus clocks & voltages vs stability.
[Nexus S Android Development] morfic:
I hope you only refer to voodoo sound?
[Nexus S Android Development] benrees21:
Yes only the sound. I'm not bothered by display.

Sent from my Nexus S on Morfic's TEUV Kernel and some help from Tapatalk!
[Nexus S Android Development] morfic:
wanting my brain? that's zombie talk!

/me runs
[Nexus S Android Development] sinik420:
I really liked the colors you had before, didn't mind the change so I don't mind missing voodoo :p and bln wakes my phone too much so I got rid of it anyway. Ill take and flash whatever you throw at us
[Nexus S Android Development] caliban2:
I'm interested too.

just had a sod with b-version, so i changed min-cpu back to 200. if b is stable now, at least i know where to play with voltage. :-)

btw, that sod was followed by an immediate reboot from pin-unlock, then freeze on boot-anim. next reboot worked, but now apps like opera and Gmail kept freezing (no fc, system kept running).

wipe of cache and dalvik took care of it.
[Nexus S Android Development] morfic:
http://goo.gl/59sSX catch!

znteuv-g-di-cv-lo-06112011.zip

benrees: still no voodoo sound, but soon enough

from the next 98tweak:

#################################

##### proceed with caution ######

#### butt nipping can occur #####

####### beyond this point #######

#################################

# set liveoc percentage, default 100%

# you should test on terminal before editing this!

# if you mess up, reflash kernel to reset to 100

# you really should test on terminal before editing this!

# if you still mess up, reflash kernel to reset to 100

echo 100 > /sys/class/misc/liveoc/oc_value

vddarm is controlled by setcpu

for vddint:

# Uncomment the following two lines to use custom voltages for vddarm and vddint

# make sure you have tested them, or else the phone MAY NOT BOOT

# you should test on terminal before editing this!

# if you mess up, reflash kernel to reset to commented out line, using kernel defaults

# you really should test on terminal before editing this!

# if you still mess up, reflash kernel to reset to a commented out line, using kernel defaults

#echo "1250 1200 1000 950 950" > /sys/class/misc/customvoltage/arm_volt

#echo "1050 1050 1050 1050 950" > /sys/class/misc/customvoltage/int_volt

Just added this to 98tweak for the next release (the one with voodoo sound)
[Nexus S Android Development] dsellers2:
I'd love to try it. :)
[Nexus S Android Development] simms22:
hey, what voltages should i use.. is 666 too much :p
[Nexus S Android Development] benrees21:
Ok, no worries. I'm not sure if it is a good idea me flashing it anyway as all that live oc business is well over my head lol. 0511b is doing me good. Hope everyone enjoys the live oc kernel though.

Sent from my Nexus S on Morfic's TEUV Kernel and some help from Tapatalk!
[Nexus S Android Development] morfic:
not much will change

the kernels will boot up, at normal values as they only have

there will be the same speeds as before

just people can now create endless variations based on the differences in top speeds.

T144+ liveoc == thermite

people should try changing dvsint both ways, up and down if they have stability issues on any kernel.

other speeds will come when i get to them

during testing, TEUV is it, unless you are a simka digger and strike a nugget
[Nexus S Android Development] belair56:
Yes 1.0.30. Tonight I will try 0511b or latest that Morfic post.
[Nexus S Android Development] benrees21:
Ok, I just don't wanna get on your nerves too much as I will be asking questions because I don't understand it. Does it enable me to change the TEUV to 1ghz ? Also I understand you can change the bus speed? Maybe you can tell me what to change to get my desired setup? I want a 250 bus with the lowest voltage possible, but obviously I'm not sure what clock speed I have to use as I'm guessing 1ghz won't be enough for the bus speed. Thanks for your help, it is much appreciated.

Sent from my Nexus S on Morfic's TEUV Kernel and some help from Tapatalk!
[Nexus S Android Development] tmello56:
Have you experienced anymore SODs with min set at 200?
[Nexus S Android Development] morfic:
The math of dividers from main clock still applies.

You cant take a 1ghz kernel and give it 250mhz.

Using 125% would give you 250mhz at 1250mhz

I used 110% on teuv, gives you 968mhz and 220x1.1 bus.

Go 112% and you are about there.
[Nexus S Android Development] caliban2:
damn. 100 & 200 mhz have the same voltage. there goes my theory of just upping 100 and get a sod-free system. :D

so, i always get sod with min_cpu @ 100.

200 appears to be stable.

edit:

hehe, just after submitting this post opera froze and then the phone rebooted. so much for 200 being stable. still, voltage too low could (!) cause this, cpu calculating errors until everything crashes.

but i don't know what to make of 100mhz causing sod, while 200 at the same voltage doesn't.
[Nexus S Android Development] morfic:
What governor are you on?
[Nexus S Android Development] caliban2:
lazy.

i tend to let everything as you set it, changing stuff makes it even harder to debug. ^^

i changed 200 to 900mV, let's see if the system freezes again...
[Nexus S Android Development] benrees21:
Ok thanks. Get a release with Voodoo sound and I will give it a go. I will only have to change the live oc value to 112% ? I take it the voltage sorts itself out? Thanks, I'm looking forward to the Voodoo release.

Sent from my Nexus S on Morfic's TEUV Kernel and some help from Tapatalk!
[Nexus S Android Development] morfic:
No, you take care of voltages.

But making some autovolt in liveoc is something i was thinking about.

I'd need to see if there is a mathematical relationship to do this.

I might change liveoc to only affect top frequencies instead of across the board/or take absolutes instead of across the board changes.
[Nexus S Android Development] simms22:
you might have to tinker with the voltages too, to.get things running just right on your phone.
[Nexus S Android Development] morfic:
Then why worry about 100 or 200mhz.

If you think voltage is too low.

Change it for 880mhz as that's what lazy uses on screen off.

Unless you disabled screenoff maxfreq
[Nexus S Android Development] Dr_Ownage:
Ok ill have a look now. Because at this stage i just wanna try and get everything off my SDCARD. then maybe... (PLEASE!!!) ill be able to send it back under warranty... *Cross Fingers*

Im gonna give samsung a go today... hopefully they accept it because its a I9020T and here in Aus we only sell the I9023 sold by vodafone. :S
[Nexus S Android Development] caliban2:
sorry, I'm still new to android, but for me "screen off" isn't the same as idle and all the other power states where screen is off.

so, does this mean whenever the phone wakes up from deepidle (for sync, whatever) it runs at full speed? and how does that explain my 100/200 mhz-thing?
[Nexus S Android Development] skinner12:
Here is my stat today:
[Nexus S Android Development] benrees21:
Ok, I will just try it when you put it out and see what works. One last question, once the changes are made does a reboot get rid of it or do they stick?

Sent from my Nexus S on Morfic's TEUV Kernel and some help from Tapatalk!
[Nexus S Android Development] simms22:
i would have thought that it would have gotten rid of the change, but i just booted znteuv(880mhz) at 924mhz :eek:
[Nexus S Android Development] Rooster85:
You can see where I flashed from 11/5 to 11/5b and I am a very heavy user, over 2.5 hours screen on. Only had loss of data once but that may have just been a fluke.

Sent from my Kushed Nexus S 4G
[Nexus S Android Development] simms22:
that looks like my use, except for the facebook. and im extreme user.
[Nexus S Android Development] caliban2:
pulled a logcat this time while waiting for it to crash... here's the end of it: http://pastebin.com/tY61Dtrk

lazy-gov, all voltages @ standard except 880@1200mV.
[Nexus S Android Development] morfic:
It's the NSTool app that resets the last used values!

DANGEROUS if you go too high and it reapplies it on each boot.

Tried to email dev about it, email didn't go through.

view stats, adjust dimmers, cool, but don't liveoc with it!
[Nexus S Android Development] simms22:
i havent used it. i installed it then took a screenshot, then sent it to you. havent touched it since.
[Nexus S Android Development] morfic:
you mean your powered off, booted and you still were at 924, although the app was uninstalled?
[Nexus S Android Development] Naa Laa:
Morfic, why was TEUV 03112011.zip pulled from the simka folder? Anything wrong with it? Surprisingly, that works the best on my phone. I tried today's znteuv but wanted to have voodoo colors and bln, so reverted back to 03112011.zip
[Nexus S Android Development] simms22:
no xxxxxx :D

---------- Post added at 07:49 PM ---------- Previous post was at 07:48 PM ----------

lots of SoD happening with it.
[Nexus S Android Development] Maximilian Mary:
Did you do a normal reboot, or your instant kill-all reboot? Personally, I prefer to wait the extra 10 seconds and let the system properly end the processes as it shuts down.
[Nexus S Android Development] Naa Laa:
Which one are you using sims22?
[Nexus S Android Development] simms22:
i did a normal reboot. its the nstools app that saves it. i uninstalled it then reboot again, then it booted to 880.

---------- Post added at 08:24 PM ---------- Previous post was at 08:21 PM ----------

right now the last znteuv, the one with live oc. i have it oc'd to 924mhz(105%).
[Nexus S Android Development] Rooster85:
Hey morfic, any reason you don't include a smartass governor? Just wondering seeing I have had some great experiences with it in the past.

Sent from my Kushed Nexus S 4G
[Nexus S Android Development] morfic:
Never had a good experience with it.
[Nexus S Android Development] some_random:
did you change any of the voltages to get to 924mhz stable?
[Nexus S Android Development] simms22:
nope. thats why i only did 105%. i was at work and didnt feel like messing around with voltages. but, after using 105%(924mhz), i kinda like the little extra kick it gives over 880mhz :)
[Nexus S Android Development] Naa Laa:
How did you change that?
[Nexus S Android Development] simms22:
if you have the gscripts app, put this line in there and enable su..

change the 100 to 105 or any other figure you want(dont go too high), then run it.

or you can type this into a terminal emulator..

again, change that 100 to what you want.

the 100 is going by percentage, so 105 is 5% higher than the kernel already is. so 105% is 924mhz(5%=44, 880+44=924)

also, you can visit the Live Overclock Voltages -Community Support thread at http://xdaforums.com/showthread.php?t=1335429 started by Maximilian Mary for help with voltages.
[Nexus S Android Development] thedudejdog:
Did I just change the voltage using setcpu on a teuv trinity kernel? :eek:
[Nexus S Android Development] simms22:
i dont know, did you?

did i just change voltage on a T144 kernel ;)
[Nexus S Android Development] thedudejdog:
Yay I bumped the voltages +25 and now i'm running teuv that was posted a few pages back.
[Nexus S Android Development] simms22:
nice... :)
[Nexus S Android Development] albundy2010:
Since the last charging point on there deep idle is disabled along with Max freq.
[Nexus S Android Development] thedudejdog:
I know. I love the colors of trinity.
[Nexus S Android Development] melvinchng:
Is there any zip file that I can flash in my TUV so I can have BLX? TUV never update for a month...

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] saranyan:
+1 here. I am using TUV 5/10 with oxygen for a while now and it has been brilliant so far. I have not got even one reboot or freeze in about three weeks.

Performance has been brilliant. I am just waiting for liveoc and deep idle to be included in TUV 10. :)

This said, Think it'll only be included once its stable for teuv , So i guess once that happens it'll be implemented in other builds also.

Tuv 10 5/10 is awesome, no complaints so far.!
[Nexus S Android Development] melvinchng:
Blx is included in teuv few weeks ago.. yeah, tuv is just awesome, not a single freeze or reboot.

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] benrees21:
Morfic, get me this Voodoo release! Lol. I wanna jump on the live oc business. I might just do what Simms did and bump it by 5% so I can leave the voltages. Does the extra clock speed show in setcpu? How do we get it to stick after reboot? Thanks.

Sent from my Nexus S on Morfic's TEUV Kernel and some help from Tapatalk!
[Nexus S Android Development] saranyan:
Yes it shows in setcpu, If your using script manager then just tick on "run on boot" option.
[Nexus S Android Development] bringonblink:
So I've been out of the loop for a while. Been using teuv880 05/10 and loving the performance and stability.

Can someone recommended a newer version? Want to try my hand with live oc
[Nexus S Android Development] skinner12:
I've set on SetCPU this voltage on latest znteuv-g-di-cv-lo-06112011:

1175 1025 1000 875 875

for the moment is stable..
[Nexus S Android Development] polobunny:
With LO voltages I might be able to get TEUV perfectly stable on my phone by bumping them a bit.

*tears of joy*
[Nexus S Android Development] caliban2:
back to TEUV-S22-05112011 with min_cpu @200 and i seem to have a stable system again. *knocks on wood*
[Nexus S Android Development] catchsomezz:
according to betterbatterystats....it says AlarmManager keeps triggering the Partial Wakelock. Anyone else have that problem?

edit:sorry, looked back about 10 pages and found out the answer to my question. sounds like opening/closing camera did the trick?
[Nexus S Android Development] caliban2:
according to betterbatterystats alarm-manager triggered wakelock 778 times in the past 2 hours, for a total of 47 seconds. doesn't sound too alarming to me.

and i have deepidle working, without the cam-trick.

(i think I've read somewhere it's rom-dependant if you need that or not)
[Nexus S Android Development] melvinchng:
No problem here..my alarm not even in the list.

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] sixstringsg:
Am I just missing the setting in setCPU to configure voltage? I don't see it.
[Nexus S Android Development] simms22:
my trainride to work today, listening to music most the time, airplane mode mostly(while underground), 4% battery loss, znteuv at 924/105 ondemand. this is pretty awesome :)

---------- Post added at 12:12 PM ---------- Previous post was at 12:06 PM ----------

what kernel are you running?
[Nexus S Android Development] tmello56:
Hey Morfic,

Is it possible to get the voltages for the 11/02 kernel? 11/02 was the last kernel that was stable for me, and with the ability to adjust voltages with the most recent z-teuv I thought it would be helpful for me to start at the 11/02 voltages and try to move down from there.

Thanks
[Nexus S Android Development] sixstringsg:
Re-flashed and force quit setCPU and they're there.
[Nexus S Android Development] simms22:
cool... :D
[Nexus S Android Development] belair56:
VERY Asome dude. That's going to make me flash happy latter.
[Nexus S Android Development] benrees21:
I hope later tonight the voodoo sound build will be here. I had an SOD with TEUV0511b earlier so I've not opened the camera app to activate deep idle and I'm all good.

Sent from my Nexus S on Morfic's TEUV Kernel and some help from Tapatalk!
[Nexus S Android Development] italia0101:
Anyone had the problem where you turn the screen off and the music skips?

I was using it through Bluetooth.
[Nexus S Android Development] noobiekins:
I hate u morfic, I got bored so I tried out franco's kernel but as soon as I flashed, I instantly noticed the color differences and it looks so brown ): No reboots so far on 0511 b
[Nexus S Android Development] Dr_Ownage:
what kernel are you running?

You just running it at 105%?
[Nexus S Android Development] some_random:
I believe he is running teuv-g-di-cv-lo-06112011.zip at yes 105% which is set here

echo 100 > /sys/class/misc/liveoc/oc_value

simms can correct me if I am wrong :P
[Nexus S Android Development] simms22:
lmao! love, hate.. almost the same intensity

the latest znteuv kernel(simka folder) at 924/105. the one with live oc. yea, only 105% oc and i didnt change the voltages. this one http://morfic.euroskank.com/simka/znteuv-g-di-cv-lo-06112011.zip

but a warning, its a bare bones kernel. no voodoo, no other goodies too.

---------- Post added at 06:51 PM ---------- Previous post was at 06:48 PM ----------

you are correct. which gives us a cpu speed of 924mhz after the 105% overclock.

---------- Post added at 06:53 PM ---------- Previous post was at 06:51 PM ----------

you fixed your nexus s???