yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] HareyCarey:
On the new TUV11 had an awesome run with it. Took it off charge at 8:05am and at 10:30pm had 33%. But after powering down, had no service. Put it in airplane mode and rebooted, then it wouldn't go out of airplane mode. Only way to get service back was to reflash the kernel and then airplane mode, then reboot.
[Nexus S Android Development] coloxim:
about the color bug?

no news?
[Nexus S Android Development] Pitrino:
last trinity kernel is bad! with superosr i had many FC!
[Nexus S Android Development] shubu000:
Yeah I had the latest uv11 (3/8) running all day then I had a bootloop at night. When I restarted and wiped dalvik, the phone was just filled with fcs. Back on uv13
[Nexus S Android Development] steve.garon:
Does anyone knows at what temperature the NS reboots? TUV11 as been rock solid for me, all version that I try work really well with easily 2-3 days uptime without reboots.

Yesterday it was really hot outside 37 C (dont know the farenheit equivalent) and I was working on my lawn and the phone rebooted into a boot loop. When I managed to get the phone back to a stable state the battery temp was at 38C. Anything I can do to make my phone reset temp higher? Or is it just the cpu that miserably failed with cause the reboot?
[Nexus S Android Development] Dr_Ownage:
I just had another freeze of my phone. The back light on the soft touch buttons was on however the phone was unresponsive. I did however notice after I turned the phone back on that the voltage was lower then anywhere else on my graph (battery monitor widget)

Ideas? I am using the latest tuv11 with cm7 rc.

Help... I don't know why this has started happening.....up until recently my phone ran ALL trinity kernels and now i cant even run TUV11 with out the phone freezing of a night. VERY annoying... im scared im gonna miss my alarm of a morning :S

simms22 is trying to help me work it out, any help is very much appreciated... :(
[Nexus S Android Development] melvinchng:
Try to use 260711 tuv11 kernel... my system keep freezing after the august update.
[Nexus S Android Development] dario3040:
A temporary fix would be to download kernel manager from the android market and install the stock cyanogen mod kernel.
[Nexus S Android Development] simms22:
if you read the nightly thread, people are experiencing reboots with the stock cm kernel too.
[Nexus S Android Development] rentaric:
15% battery left, 2d12h, display on 2h47m, music 1h55m, calls 1h53m.

Using the XTEUV92 (XTEUV92-Any-2.6.35.14-03082011), 2g only, stock 2.3.4 rooted (and some native apps removed).

Not sure if that is a good enough improvement over the TUV11, morfic what do your tests say, will XTEUV92 be a yay or ney in the long run?

Installing the latest TUV11 now for another test.
[Nexus S Android Development] morfic:
xteuv92 is no leap, that's certain. Once the influx of of cm7 caused random reboots dies down, I will assess the stability.

With TUV11 being restored to a true 1.1GHz I could bump its voltage if needed. With xteuv92 taking its place.

The standby time I can't really affect as we reached the bottom with tuv11 back when simms and I pushed it low. So the gains can only be realized in screen on time, through a lower max clock and through returning panel frequency to stock 56Hz.

We will see how it shapes out.
[Nexus S Android Development] king23adrianc:
really? so later on 1.1 ghz wont be UV??
[Nexus S Android Development] yungl82:
Is there anyone with a Rev 11 Nexus S able to run TUV11? I think my phone just cant handle it :(
[Nexus S Android Development] simms22:
UPDATED AGAIN by morfic early this morning, Trinity1.544ghz kernel for the Nexus S http://goo.gl/xj7cZ you should see higher quadrant scores w/this one. the toolchain was updated to a newer version..
[Nexus S Android Development] coloxim:
can I know the voltage in the UV11?
[Nexus S Android Development] dario3040:
You could always check Morfic's github.
[Nexus S Android Development] dario3040:
Mine runs it just fine, it's smooth as butter, no reboots either, I really like the kernel, but I need 1.3 Ghz for lulz.

Mine is rev 11 btw =)
[Nexus S Android Development] coloxim:
where i didn t find them,,,
[Nexus S Android Development] 2000impreza:
The voltages are in the link below.

http://morfic.euroskank.com/git/?p=...122f731c;hb=refs/heads/android-samsung-2.6.35
[Nexus S Android Development] dario3040:
Thanks for posting a direct link, I'm feeling so lazy right now..
[Nexus S Android Development] bringonblink:
is the only difference between TUV11 and t12 the UV?
[Nexus S Android Development] dario3040:
Ummm 100 MHz, bus speeds, gpu clocks, voltages, the name, and... yea, that's it.
[Nexus S Android Development] bringonblink:
i'm assuming the t12 is the one with higher speeds and clocks?
[Nexus S Android Development] dario3040:
Of course :)

12 symbolizes 1.2Ghz
[Nexus S Android Development] yungl82:
I envy you lol. When it's not rebooting I LOVE the kernel.. I'm back on t12 at 1Ghz now though :(
[Nexus S Android Development] gotjazz:
Hrm of course you know best but that would make me a little sad to be honest. To me tuv11 has always been the perfect mix...

Going back to stock frequency was bearable but I'm not sure I'd want an underclocked kernel. The mix of UV and a little OC always felt like the best thing since sliced bread.
[Nexus S Android Development] sinik420:
Also simms no luck on 1.5 same as before, go launcher keeps refreshing until the phone reboots into a loop =[ no big deal as I love 1.4

sent from my nexus s on a kang from simms
[Nexus S Android Development] dario3040:
:eek::eek::eek::eek:
[Nexus S Android Development] dario3040:
Both 14, and 15 freeze on mine.

It seems my phone prefers low frequencies and voltages...
[Nexus S Android Development] simms22:
its that sliced death again.. :eek:
[Nexus S Android Development] simms22:
go launcher keeps refreshing? huh?
[Nexus S Android Development] rejanmanis:
I used SuperOSR ROM, i ported XTEUV 920 , its run very very very smooth. no lag at all. But it freeze and reboot when i downclock to 800mhz.

Battery life also pretty good.

And also i tried to port T 1544mhz. cannot OC at all, when i open cpu performance at parts (cyanogen) setting, and klik 1544 and it s freeze in a real time and reboot. So i cant even try to run it at all.
[Nexus S Android Development] dario3040:
What's wrong with sliced bread?

The sliced bread just needs some love ;)
[Nexus S Android Development] dario3040:
Hold on for a second, what do you mean with ported?
[Nexus S Android Development] sinik420:
As in the background goes black then refreshes, I don't know if its the whole shell or just the app so I wasn't going to assume anything.

sent from my nexus s on a kang from simms
[Nexus S Android Development] dario3040:
Which launcher are we talking about?
[Nexus S Android Development] simms22:
this is my "time in state" from setcpu for TUV11(trinity11). this is pretty much a textbook example of how it should look like(this was overnight, received 14 emails during this time). if it looks much different than this, then you have an app acting badly most likely. notice how often it stays at 100mhz(low end) as opposed to 1100mhz(upper end).
[Nexus S Android Development] dario3040:
That's kind of odd..

Does it really need 1 Ghz for E-mail's?
[Nexus S Android Development] Maximilian Mary:
Still no shark. Maybe I'll try again when it's a little cooler than 125° F. :p
[Nexus S Android Development] rub1k:
I think the way it must work is... when/if CPU usage goes up (i.e. receiving an email or some background activity that uses the CPU), it "wakes" it and switches to the fastest set speed (to get the work done quicker?)... and then, once cpu usage goes down to "mostly idling" or whatever, it'll throttle back down to the low setting.

Or at least that's what would make sense to me... /shrug.

EDIT: From the screenshot though... I'm confused about the time periods.. all that adds up to 555779 (ms/10)... does that mean 5557.79 seconds, i.e. 92 minutes total sample size (~13 of which were at the top speed)?
[Nexus S Android Development] coloxim:
if you use conservative governor ...you can use all freq..

I'm using it without lags...

i've put up threshold 70/75%...

I think it use less battery...
[Nexus S Android Development] simms22:
no, but there are more background processes that go on also :-P
[Nexus S Android Development] simms22:
and lesser performance. i use ondemand.
[Nexus S Android Development] simms22:
thats about right
[Nexus S Android Development] simms22:
im diabetic. bread, especially white, is very bad for me.
[Nexus S Android Development] king23adrianc:
did u put

sampling 15000

up threshold 98%

ignore nice load 0

power save 0 ?
[Nexus S Android Development] simms22:
always.. :)
[Nexus S Android Development] king23adrianc:
okkkkkkkkk :p
[Nexus S Android Development] dario3040:
That seems to come as standard in Morfic's latest kernels.
[Nexus S Android Development] dario3040:
I don't know, why put the threshold so high?

Does Ondemand do some magic or..???
[Nexus S Android Development] sinik420:
go launcher.

sent from my nexus s on a kang from simms
[Nexus S Android Development] sk3201:
Just one question: can i use the 2.3.5 kernels from the first page with 2.3.4 based roms?
[Nexus S Android Development] dario3040:
Yes you can, 2.3.5 is almost the same as 2.3.4.
[Nexus S Android Development] sk3201:
Thanks. Downloading...
[Nexus S Android Development] yungl82:
Lulz
[Nexus S Android Development] Dr_Ownage:
That is when the issue first started.... :(

As simms said CM7 people are having issues too....

an update from last night, went to bed 65% battery. Woke up and the screen is blank the soft touch buttons are lit up and go dull when you put your finger on them but they are unresponsive. The phone is completely unresponsive my 8am alarm did not go off (thank go i set a backup) i pulled the battery out and when the phone turned back on im at 11% battery... WTF is going on?!?!

Gonna give stock a go today everything a go today. Im hoping that will fix it.... :(
[Nexus S Android Development] melvinchng:
How do you make you battery become 99%? Mine stuck at 95.
[Nexus S Android Development] simms22:
charge it as much as itll charge, unplug it, plug it back in, then charge it with the screen on the rest of the way. itll reach 100% that way.
[Nexus S Android Development] melvinchng:
Mine reach 95%. Sometimes with WiFi on become 98%. And after WiFi off and I charged, it become 95 again... does keep screen on give permanent 100%?
[Nexus S Android Development] king23adrianc:
but doesn't this hurt the battery? heard it somewhere bump charges r bad... :confused:
[Nexus S Android Development] simms22:
it reaches 99% normally, but then takes a while to hit 100%. what do you mean permanent? 100% in a battery isnt ever permanent.
[Nexus S Android Development] simms22:
maybe. maybe not. im not an expert. but i havent seen any negative changes to my battery. and ive been bump charging since the first week of january.
[Nexus S Android Development] dsellers2:
Interesting. How in the world did you figure that one out Simms?
[Nexus S Android Development] simms22:
the charging to under 100% is a built in safety feature for the battery. if you want 100%, you have to jump through the hoops.
[Nexus S Android Development] simms22:
noticed a while back that it kept charging when the screen was on, when i was plugged in and using it.
[Nexus S Android Development] window7:
According to SetCPU, ondemand need higher threshold to make it smoother.

while conservative need a lower threshold to make it smooother :)

But ppl often just think that the higher the threshold, the less chances for the frequency to jump from lower to higher, but that's wrong. Ondemand, it just need the opposite, where lower the threshold, the less chances for the frequency to jump from lower to higher :p
[Nexus S Android Development] window7:
Well, after much more research, our phone will charge EXTREMELY fast from 0% to 79%.

Then starting from 80% to 95%, it will reduce it's charging voltage from 100% to 70% with the current(mA) rising 30% more.

Then at 95% to 100%, it will reduce it's charging voltage from 70% to 40% with the current(mA) rising 60% more.

That's why when you charge your phone, you will notice some heat and speed changes on phone and charger.

Charging from 0% to 79% = Extremely HOT + Extremely Fast

Charging from 80% to 95% = Warm + Slightly slower

Charging from 95% to 100% = Cool/Room temperature + Slow

Here's a graph showing some details regarding what I said :D
[Nexus S Android Development] cabstrak:
simms, what's that top left icon on the notification bar? what app is that from?
[Nexus S Android Development] HareyCarey:
TUV11 looks about like the screenshot you posted Simms...only today it seems that it looks like something has been going a little screwy and I checked what was eating my battery up and it is Media(Included packages:DRM Protected Content Storage, Media Storage, Download Manager, Downloads). Was eating 38% of total battery while the display was at around 35%. What the heck is up with that? Is there a rouge program I need to look for that could be using this? And I can't force close it from battery usage in settings, so I don't know what's up. I turned it on airplane mode and it seemed to stop how long it was keeping the phone awake. It was keeping it away for like 2hrs and some change over 12 hours or so and just started to rise near the end of today.
[Nexus S Android Development] simms22:
its a very old battery status app that i used to use on my g1. by the time the nexus x came out, this app wasnt available in the market anymore. so this app was originally on my g1, then i transferred it to my nexus one, then to my nexus s, and then to my old school droid that i bought at a flea market. lol, its been around :)
[Nexus S Android Development] simms22:
seems like a rogue app or background process.
[Nexus S Android Development] HareyCarey:
Where should I look and what should I look for? I found that Media is a cached background process so I stopped it. I will wait until the battery charges to see if that fixed it. But, I wonder if perhaps there is another rouge app that is activating Media to download data or use data or something like that. It also gets very very hot when Media is running wild. I will keep an eye on it and thanks for the response.
[Nexus S Android Development] simms22:
give it a reboot too.
[Nexus S Android Development] melvinchng:
I meant after you reboot your phone, will it stay upto 100% or still 95%?

Is it a one time break through to reach 100% or you have to turn on screen everytime to reach 100%?
[Nexus S Android Development] simms22:
after reboot, sometimes 100 and sometimes 99. and you have to turn your screen on every time to get to 100%.
[Nexus S Android Development] melvinchng:
If you don't turn it on, it will still stay at 95%?

Can you do me a favor? Can you please change the sampling rate from 35000 to 15000 and threshold from 80 to 98 for the 260711 tuv kernel without changing the voltage? I wanted to try whether it will freeze with those settings.
[Nexus S Android Development] simms22:
use setcpu to change it. press advanced..
[Nexus S Android Development] window7:
Wow! The T12 with lower voltage give me 4300+ quadrant :p

Thanks morfic and simms22 :)
[Nexus S Android Development] melvinchng:
I set on boot, it just won't use that number on boot.... and I have to disable set CPU to let it show 1.1ghz. So how can I do it?
[Nexus S Android Development] simms22:
try going to the main phone settings, applications, manage applications, setcpu.. clear its data, then open setcpu and re set it up.
[Nexus S Android Development] melvinchng:
With root access and my phone is 1ghz?

Edit: tried it, no difference.
[Nexus S Android Development] dario3040:
Yes they are, but you won't notice the bad effects before you have a new phone anyway. (Unless you have a two year contract....).

And if the battery breaks, just buy a new one, it won't break any time soon.
[Nexus S Android Development] dario3040:
Not bad, but you forgot to turn on Flight Mode.:rolleyes:

It should boost your scores even further.
[Nexus S Android Development] window7:
Haha. Alright, will bench it now with Flight Mode off. I manage to reach 5978 before with T1576 kernel :D
[Nexus S Android Development] bringonblink:
Im trying to find the voltages for TUV11 too, however i can't make out anything from that link :/

If someone could tell me how to read that or post voltages would be grateful
[Nexus S Android Development] steve.garon:
I was trying to understand those to but them on my GF captivate this morning and from what I can understand, these are the voltages:

1100 @ 1225 (-25)

800 @ 1125 (-75)

400 @ 1000 (-50)

200 and 100 @ 900 (-50)
[Nexus S Android Development] melvinchng:
Wtf?? The record was 5700! Galaxy s 2 1.5ghz won't reach that high too...

That's why nexus s is known as the king of the phone!
[Nexus S Android Development] dario3040:
I don't know what you are talking about, the Galaxy S II has reached a score of over 6200.
[Nexus S Android Development] window7:
Only recently GS II manage to get over 6200, before that, Nexus S still the king. Haha.
[Nexus S Android Development] dario3040:
The Nexus S is still the single core king.
[Nexus S Android Development] melvinchng:
Nexus s previous record was 5700. The sgs2 in YouTube @ 1.5 shown 5400+ only..
[Nexus S Android Development] simms22:
ive seen the 5978 screenshot. my record is just a lowly 5838 :(
[Nexus S Android Development] dsellers2:
[Sarcasm]That is so weak.[/sarcasm]

:)
[Nexus S Android Development] simms22:
thats what im saying :mad:

;)
[Nexus S Android Development] dario3040:
Are you sure you feed it properly? :rolleyes:
[Nexus S Android Development] Maximilian Mary:
For those having trouble with the green screen, this seems to happen at lower (single digit) screen dim levels with the default Voodoo Color gamma settings. The reason it happens after charging all night is that's probably the only time you see the screen on its dim level. To fix it, raise the screen dim level (under CM settings - Display - Auto Backlight), or reset the Voodoo gamma hack to the 2.3.3 defaults.
[Nexus S Android Development] cheech87:
According to the link ( http://morfic.euroskank.com/git/?p=...122f731c;hb=refs/heads/android-samsung-2.6.35 ), it looks like the t12 kernel is undervolted as well?

Also, the 1225 mv is actually -75 mv if you linearly interpolate the stock 1000 and 1200 voltages. tbh, this seems like a rather steep uv for the higher clock speeds. Maybe my phone just can't take it.
[Nexus S Android Development] dario3040:
Mine can't take T12 for sure, but T13 works fine.
[Nexus S Android Development] cheech87:
I'm testing tuv11 right now, but just by looking at the t12 voltages, i know my phone can't handle it since i lock it up with netarchy's kernel with higher voltages than posted for t12.

The t13 voltages look stock (except an ov at 1300), so that's probably why t12 doesn't work for you, but t13 is fine.
[Nexus S Android Development] bringonblink:
i think the uv on the tuv 11 is too steep for my phone, are there any plans to implement the uv mod so we can change it ourselves?
[Nexus S Android Development] cheech87:
I agree that the uv is (slightly) too steep for the higher clock speeds. As far as a mod for custom uv'ing, I don't really see this as necessary.

EDIT: Morfic, what exactly does DVSINT correspond to?
[Nexus S Android Development] dario3040:
The only way as of now is to compile it from source after changing the voltage.

And I don't think Morfic has any plans of implementing voltage control.
[Nexus S Android Development] iamxeph:
anyone can write simple instruction to do that?
[Nexus S Android Development] bringonblink:
The mod already exists, its used in netarchy and matrix kernel.

Sent from my Google Nexus S
[Nexus S Android Development] morfic:
Never.

Sent from my G2x
[Nexus S Android Development] morfic:
Email me, you just git clone my source, install a toolchain to compile for arm on x86. And I send you my simplified build script, should be pretty fire and forget.

Just need to pull one file from samsung git to get the boorloader's "Google" as bootlogo. I didn't commit my bootlogo.h

Sent from my G2x
[Nexus S Android Development] morfic:
True, user voltage control is a nightmare.

Edit: just check how often people talk about unstable matr1x or netarchy and at the VERY end go "i think you might be right. maybe I try the kernel again and try less UV" o_O

Sent from my G2x
[Nexus S Android Development] morfic:
T12 hadn't been used in a while, the voltages it had were clearly for a special build.

Tbh DVSARM2 is quite low, not just DVSARM1, but it will need a bump in DVSINT1 to be comparable to T13.

The kernels were not meant to be comparable.

T12 was the last kernel before the battery guzzler.

T13 I moved closer to the OC kernels.

Easy as that.

You want stable? Get TUV11 or T144.

T12 and T13 are both recently reintroduced and with that have room for improvement.

Sent from my G2x
[Nexus S Android Development] cheech87:
Yeah, the steep uv for higher clock speeds I was referring to tuv11. Should've been more specific. I'm still testing it now, but it seems like its BARELY too low for my phone to handle flawlessly.
[Nexus S Android Development] morfic:
In which your case your mention of T12 and 1200 do not help understand what you refer to.

If xt92 works out, my plans are to bump tuv11 to 1.25V.

Which being the default voltage@1GHz makes it a marginal UV at 1.1Ghz.

I have no plans to do this right now.

There are not enough problems with this kernel to justify raising it on the majority of users.

Once there is a battery saving alternative, that situation is changed enough to make the adjustment for the few users who currently can't run it with 100% reliability.

Sent from my G2x
[Nexus S Android Development] cheech87:
Yeah, sorry. I was quoting someone that referenced the tuv11 voltages. But I should have been less ambiguous anyways.

Thanks for your great work!!
[Nexus S Android Development] morfic:
I'll see about pushing my simplified build script to git.

Then you git clone source, fetch the script, fetch the toolchain, edit voltages or patch in netarchy's modified voltage control (forgot who did the original work, he ought to mention it in his thread) and build and forget.

Using koush's "anykernel", there is no ramdisk to worry about.

But I won't have constantly misused voltage control in a NS Trinity kernel.

I'm slowly waning G2x users off the voltage control too. TUV11 already lost it and T15 will soon have it gone too, it was a mistake to make it available.

My work on the G2x low power kernel shows there is nowhere they can go, yet they ask for large UV amount on the lowest step.

I might bump tuv11 early so you have something to run while you get up to speed.

Sent from my G2x
[Nexus S Android Development] shubu000:
Not sure if anyone picked this out, but i'm using Zulugen atm and i'm having deep sleep issues currently...

anyone else got that?
[Nexus S Android Development] morfic:
Are you using the TUV11 that was built for zulugen with its own logo?

Sent from my G2x
[Nexus S Android Development] simms22:
and this is what pushes a good dev into the great dev territory. its not the actual subject thats written in this quote.. besides for the actual development, its the listening, the responding, and the care.

thank you Daniel
[Nexus S Android Development] cheech87:
+1. Given how fast this thread moves, I'm impressed (and thankful) that he actually looks back and gives clear and meaningful answers to posts that would normally just get lost.
[Nexus S Android Development] Maximilian Mary:
I'd like to use TUV11 as my daily, but I'm having a few issues on my ns4g.

I can't get a signal until after a warm boot.

Wimax does not work.

Adb & usb mount are not available.

Has anyone else had these issues on the ns4g, or found solutions?
[Nexus S Android Development] Kurupt1:
I use tuv11 as my daily. I usually get service and usb storage on the first reboot, have to drive a little bit for 4G but ill try it out tomorrow.

Sent from my Nexus S 4G