yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] morfic:
one or both centisecs may actually be defaults now, but no reason to remove it

the ratios are to limit the size of write backs, unlike you i may be writing out more often due to this but when it writes out the chucks are small and thus linux kernel stalls will be less noticeable

this is the same reason to use deadline (VR btw is no good, i tried it)

minimize the probability of linux stalls due to congestion

if we make the kernel write out very efficiently it will write even faster onto a device that's still as slow as it was, it starts a vicious cycle.

I had stalls on a desktop (let's face it, those phones are desktop's in our pockets with far too slow "disks")
[Nexus S Android Development] franciscofranco:
I know what those options are and what they do, I was actually very intrigued by the values you choose...and you actually make sense, that's something I never thought before... I'm definitely gonna try that.

About VR and deadline, after tweaking VR for flash devices it works pretty awesomely...whats your problem with it I'm curious!
[Nexus S Android Development] morfic:
Funny how the flash device tweak is same as for deadline, should try running it against deadline tweaked that way.

Main issue is it works as well as deadline.

I don't like to add in stuff that allows me to run as well as i did before i added it in.

Less is more.

EDIT: i guess your head reversal penalty tweak shows you noticed it's not "it", you seem like a no nonsense kinda guy, curious what you think about deadline tweaked, vs VR
[Nexus S Android Development] franciscofranco:
Yes you make a point there. I don't have enough background testing to tell you what I think about deadline tweaked vs VR yet, but that's something I will test as well and I'll get back to you.

The only thing that I noticed about VR, and which I've found strange, is the disparity of values in the I/O quadrant test (I dont measure performance by benchmarks, but it's an useful tool to get some conclusions about changed code). In one test I can get 6700 and in the next I can get 8500, then back to 7000, then 6500, then 8900, and with deadline I always got steady values, not changing much. Other than that I can't compare tweaked VR and tweaked deadline just yet, gotta do more real life testing.
[Nexus S Android Development] Ezekeel:
Old testament cereal. Nice. "You shall strengthen yourself with a hearty breakfast before smiting the blasphemers with holy vengeance." Is there also a Mohammed cereal or would this be offensive so close to Ground Zero? ;)
[Nexus S Android Development] benrees21:
Oh yes more Thermite goodness. Got it running now, can't believe how fast and smooth it is at 1ghz. My fave kernel so far.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] melvinchng:
Is battery life slightly reduce even you are running at 1ghz than tuv 1ghz? Is the bus still 240 at 1ghz?

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] skinniezinho:
No boot for me :S endless reboot in the animation
[Nexus S Android Development] benrees21:
I don't know about the bus. Battery life is good, about 18 hours moderate/heavy use.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] skinniezinho:
Morfic, could you share the uv table that you use in your TUV 05/10?

WIth proton it only says 100mv lol
[Nexus S Android Development] roshga:
Hi morfic,

what do you think about the twicks in this thread?

http://xdaforums.com/showthread.php?t=1313288

is it any good?
[Nexus S Android Development] Salvatore11:
Hey , im just using the latest cm7 nightly . Should i download the TUV on top or the G2X ?
[Nexus S Android Development] pan1980:
almost 2 days with T11 1910 and no problem appeared.

no reboots, no signal loss no death screens.

i am updating to miui 1.10.21 which integrates 2.3.7 core to test compatibility with T11.
[Nexus S Android Development] JmPTaz09:
G2X is for the LG G2X phone...
[Nexus S Android Development] simms22:
the g2x kernels are not for the nexus s, they are for the g2x. try teuv, thats a nice kernel :)
[Nexus S Android Development] Salvatore11:
Thanks for the quick answers guys , gonna try this now
[Nexus S Android Development] lgalkis:
stuck on boot for me...:(
[Nexus S Android Development] simms22:
it should at least boot, it boots up at 1ghz. try redownloading?
[Nexus S Android Development] noobiekins:
getting 1 and an half usage with teuv, 1 full day with t11. LOVING it so far. No reboots NOTHING
[Nexus S Android Development] dario3040:
Damn, I had 50% when I arrived at the school, and I started benchmarking with the speed set to 1480/1480, it literary killed my battery in 47 minutes T_T
[Nexus S Android Development] simms22:
why so long? you must not have been benching it enough :p

but, it means that it runs on your phone :D
[Nexus S Android Development] dario3040:
Yes it runs, and actually it's more stable than T144
[Nexus S Android Development] morfic:
It's not your grandma's 1GHz, that's why :)
[Nexus S Android Development] benrees21:
LMAO!!!

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] Igotsanevo4g:
I can run T154 but I can't even boot thermite anything :(
[Nexus S Android Development] lgalkis:
I have try it but nothing different happens...what is the bus speed cause my phone cant handle over 220 mhz..?maybe that is the problem...or not?
[Nexus S Android Development] Lazat:
Simms, what special electrons do you feed your phone with =D ? i reach the same cpu-score as u 10600, but my memory is 1665, and most alarming, my 3D score is just half of yours, 1014 =( it never goes higher, doesnt matter how many runs i run and flightmode and shutting of screen for 10sec.

i know its just a benchmark. but it most be something wrong when my 3D scores are 50% of yours.. is there anything i can do to improve those things? feels like its something slowing my phone down.
[Nexus S Android Development] morfic:
Your 3D is quite normal, memory way too low.

Fairly certain we don't all have the same ram (chips) in our phones though.
[Nexus S Android Development] simms22:
nothing wrong with your phone. thats how it should be. somethings "wrong" with my phone. its been scoring higher than normal in most 3D tests. morfics scores half my 3d score too. weve been trying to figure out why my phone scores higher in 3d for some time now. oddly, my phone scored half of what it usually does with this past week of cm kangs. so im on a kang from 10/5 now, it scores my normal high 3d score. something recently changed in cm that is bringing my 3D score down :(

youre memory score does seem slightly low though.
[Nexus S Android Development] jjhrrsn:
Just curious who's running what governor and rom issue free with teuv
[Nexus S Android Development] simms22:
no issue here. mostly lazy but sometimes ondemand. cm kang, 10/5.
[Nexus S Android Development] melvinchng:
The t11 is great! Everything works! Including games and everything.

Btw, is there any huge different between voltage on tuv and t11

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] simms22:
out of curiousity, with people having different experiences with trinity(good and bad), could i get everyone to run this command in your terminal emulator then give me a screenshot of what it says after..

it turns out that morfic and i have different bootloaders, and different experiences with flashing stuff. my bootloader is I9020XXJK1 and morfics is I9020XXKA3. heres my screenshot. im curious to what the common bootloader is, seeing that i havent changed my bootloader since getting the phone, and neither has morfic.
[Nexus S Android Development] ragnarokx:
This is mine:

androidboot.bootloader=I9020XXKA3

Sent from my Google Nexus S
[Nexus S Android Development] dsellers2:
Mine is

View attachment 757321
[Nexus S Android Development] thedudejdog:
I can't run teuv or pretty much anything besides tuv.
[Nexus S Android Development] Rem3Dy:
No wonder I can't run teuv. My phone needs 905mv for 100/200. If I could have that I would be so happy!!!!
[Nexus S Android Development] simms22:
i found this bit of information..

top line got cut off, it said nexus s (worldwide version "XX")
[Nexus S Android Development] irishrally:
KA3 here. Never had any problems with trinity.
[Nexus S Android Development] FuZZ__:
JK1 here.ah,I should update it...
[Nexus S Android Development] lgalkis:
KA3 for me...is this the reason that thermite cant boot?
[Nexus S Android Development] jjhrrsn:
am i overlooking something because mine is D720SPRKE1 which is the radio that i am on. Its the newest update and can be DL for NS4G not sure about NS from rom manager from peteralfonso. Could this be causing issues ?
[Nexus S Android Development] Bestplayer55:
Hi guys! How can i changes voltages in this kernels???
[Nexus S Android Development] kfjunky:
You can't.
[Nexus S Android Development] :
yep, even with 1.666 one :D.. something must be different in ramdisk of oxygen, because manually installing apps (not from market) it works.

edit: and it was confirmed by several other users in the oxygen thread.
[Nexus S Android Development] gotjazz:
just a little observation based mostly on playing fruit ninka - so do take it with a grain of salt.

the uv11 kernel in the OP seems to be a lot smoother than the latest version
[Nexus S Android Development] dsellers2:
Hey Simms and Morfic,

Take a look at the screen shot. I've been driving myself crazy trying to figure out why since I've installed rc1 cm my CPU has been idling up near 50 to 100 percent with the screen off. For hours even.

Using systempanel app I was looking for a rogue app but all apps looked normal and by the looks of the systempanel app the CPU should be idle at around 4 to 5 percent. Just out of curiosity I reinstalled the cm7 and did not reinstall my normal kernel which is skuv11 or t12. I use both of them. Both show the same results. If you look at the bottom chart and the first 6 hours you will see what I'm talking about. But since I've went with the kernel that come with CM for the past hour I have been seeing normal CPU speeds while the screen is off.

So....what are your guys thoughts? Between the first 6 hours and the last 2 no apps had changed and the only change was the kernel.

View attachment 640066
[Nexus S Android Development] johnkim0011:
Which UV11, UV12 kernels with Voodoo Driver v9 are compatible with CM7.1 RC1?
[Nexus S Android Development] brainmaster:
I am on CM 7.1 RC1 with SKUV11 kernel and everything is fine. Tried monitoring for 4 hours, the CPU is under 10% when the display is off.
[Nexus S Android Development] simms22:
i cant explain it, maybe an app checking in. ive monitored my phone, and my cpu usage while the screen is off ranges from 3-8%. 8% was when i was recieving emails.
[Nexus S Android Development] dsellers2:
Hmmm....maybe its my gmail accounts. But I figured happened would show the CPU utilization and when on the stock cm kernel its staying at 3 percent constant. Oh well. :)
[Nexus S Android Development] dario3040:
All android 2.3.4 kernels are supported.

All voodoo 9 kernels from Morfic should work
[Nexus S Android Development] martinsjt:
Hello,

I also had this issue, on my case was the android.process.media process that was eating 90 % of the processor power.

I solved this issue on app manager cleaning app data.

I also suggest you to install Watchdog Task Manager Lite from market:

https://market.android.com/details?id=com.zomut.watchdoglite

It allows you to checker which app is using the processor excessively.

"Watchdog monitors your apps and alerts when one loses control, allowing you to kill just that single app."

Best
[Nexus S Android Development] jark99:
Soo just curious. All the netarchy kernals have voodoo color and sound in them? To get better sound quality during calls? Right?
[Nexus S Android Development] JmPTaz09:
No, for better quality music when using as an mp3 player. Trinity kernels all have voodoo as well.
[Nexus S Android Development] dario3040:
Why do you ask that in this thread? :confused:
[Nexus S Android Development] simms22:
thats like going into mcdonalds and asking if burger kings big mac has pickles included. you can find your answer in this thread http://xdaforums.com/showthread.php?t=936219&page=373
[Nexus S Android Development] SA-07:
Lol simms
[Nexus S Android Development] gotjazz:
thanks so much for the oxygen kernel. for one i love every uv11 kernel you made anyway but this one made me try oxygen.

I'm now away from cm7 nightlies and have no remorse. i DO miss some of the extra feature but the most important ones are there in oxygen too and it's so much smoother in daily usage - couldn't be happier with my nexus atm.

Guess I'll skip the galaxy S2 upgrade I was thinking about :D
[Nexus S Android Development] jark99:
godddamn xda app messed tthings up! my bad! but thanks for the replies haha :)
[Nexus S Android Development] dario3040:
Hmmm, how are pickles related to voodoo sound, and color?
[Nexus S Android Development] SA-07:
Lol
[Nexus S Android Development] window7:
Mine is KA3 yet I can use any Trinity Kernel including kernel without any fault.

By the way, my Nexus S written "Made in Korea". Surprisingly, it's not made in China :eek:
[Nexus S Android Development] lgalkis:
Also mine made in korea writes...but i dont know if this makes any difference..i can use any kernel but not over 220mhz bus/gpu speed...
[Nexus S Android Development] shubu000:
Mines ka3, I can run t144 but as soon as I start games like asphalt, it freezes so yeah :(
[Nexus S Android Development] window7:
Where did you get the Nexus S from? Vodafone? Outright from where?
[Nexus S Android Development] melvinchng:
Ka3 for me... I'm using kd1 radio.. so... have to change?

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] roshga:
I'm on the KA3, but I had the KF1 before, it updated after the 2.3.3 update which I got on stock OTA. so simms I guess yours haven't changed because you're not a stock person :P
[Nexus S Android Development] shubu000:
i bought mine in Hong Kong, which in itself was a grey import from the us
[Nexus S Android Development] window7:
So yours is AMOLED version?
[Nexus S Android Development] belair56:
Screen shot

Here you go.
[Nexus S Android Development] benrees21:
Here we go.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] Lazat:
Here's mine:

"$su

# cat /proc/cmdline

console=ttyFIQ0 no_console_suspend androidboot.serialno=323194F2E61400EC androidboot.bootloader=I9020XXKA3 androidboot.baseband=I9020XXKD1 androidboot.info=0x4,0x0,1 androidboot.carrier=EUR gain_code=3 s3cfb.bootloaderfb=0x34a00000 mach-herring.lcd_type=0x00000000 oem_state=unlocked

#"
[Nexus S Android Development] Bamdroid:
Mine is JK1.

私のネクサスSから送りました
[Nexus S Android Development] graphreak:
My NS (on TMO) has:

HW Ver: REV 11

Bootloader: I9020XXKA3

Baseband: I9020XXKF1

Serial No.: Begins with a 36300ACEF_ _ _ _ _

Had updated my Radio to the latest a month or so back.

If that's helpful.
[Nexus S Android Development] simms22:
so it looks like there isnt a real difference what bootloader you are using.. thats one more variable thrown out. thanks for posting those.
[Nexus S Android Development] Maximilian Mary:
I just pulled the phone out of my pocket to find it bootlooping. I'm not sure if it's related, but I had bld disabled for a change.

Teuv1910 / 1020 euroskang / ns4g

I'm not complaining, mind you. Just reporting in case it helps.
[Nexus S Android Development] sinik420:
XxKA3
[Nexus S Android Development] benrees21:
Want more Thermite!!! I don't understand how some people can't boot it? Mine works lovely. If there is anything I can do to help track down the problem, let me know. Maybe it's a ROM issue?

EDIT: Morfic, have you thought about doing a ROM? Sorry if you have but I can't recall seeing one.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] shubu000:
Yep :)

Loving it :D
[Nexus S Android Development] simms22:
more thermite :p THERMITE-S22-optos.zip http://goo.gl/89ffn
[Nexus S Android Development] dsellers2:
Not all phones are made the same. Not all chips are made the exact same. Electrons flow different. That's why with this chip default is 1ghz and not 1.4. This way they know all phones will operate the way their supposed too. Consider yourself lucky. :)
[Nexus S Android Development] benrees21:
Thank you!!! Gonna try this now!

EDIT: Brilliant! Unbelievable performance as usual!

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] benrees21:
I can't run 1.4 for long before I get a reboot, 1.3 is my max. I find it weird how the same chips can be so different with frequency.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] jjhrrsn:
Can't even boot either thermite
[Nexus S Android Development] benrees21:
What ROM?

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] jjhrrsn:
Been on bm miui . Just updated. Couldn't run on other version either. T11 has been the only one I haven't had issues with. Been on cm7 kang gpa18 and miui
[Nexus S Android Development] dsellers2:
I'm very happy with the teuv tuv1, and 1.1, although its capable of running up to 1.3 fine. I've never been able to run morfics at 1.4 though it doesn't seem to work more than an hour of benching. The phone Burns and goes wierd. :)
[Nexus S Android Development] FuZZ__:
thanks!gonna get more reaction:D
[Nexus S Android Development] morfic:
Nah, a rom...a good one, takes time.

Building the occasional kang when cm7 is broken to high hell aside, I don't think I'll be doing one.
[Nexus S Android Development] Bamdroid:
Using fitsnugly kang and T11 (10/19). On 1100 I got a couple reboots checking twitter and sending a text. On 1ghz its cherry/no issues...

私のネクサスSから送りました
[Nexus S Android Development] Bamdroid:
My Nexus S is skanktafied...

That is all.

Well actually, any reason the 1ghz speed on the latest Thermite seems faster/snappier than T11's 1ghz? Wait...somebody asked that already huh?

私のネクサスSから送りました
[Nexus S Android Development] benrees21:
Ok..then....lol. You gotta build one when I get the Nexus 4 though :-P

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] intheb0x:
Experimental Nexus S+4G Kernels:

TEUV and T144 using the Deep-Idle patch Ezekeel found and extended to work on Nexus S (Originally for Vibrant)

92deepidle and 95dimmers now moved into 98tweak and removed on flashing of these kernels

Please set your defaults in 98tweak from now on.

curious to what that means?

lol

thanks

---------- Post added at 04:40 AM ---------- Previous post was at 04:25 AM ----------

also im interested in Thermite kernels, but that one did nothing but throw me into bootloops!

but 18 hours of battery life with heavy use sounds pretty amazing to me.

so any insight into that?

:)
[Nexus S Android Development] benrees21:
What ROM are you using?

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] khartaras:
Thermite doesn't work too well on my phone. I suspect it might be the ROM (taichi's kangs) and the fact that I haven't wiped my data in well over a month. What's the bus on Thermite?

Anyway, T11 is fast and somewhat battery-friendly.
[Nexus S Android Development] the_trade_place:
I cannot for the life of me get any trinity kernel to work on my.device. all they do is send it to bootloop city
[Nexus S Android Development] ZeDestructor:
Can we have some more info on your phone? Specifically, which ROM and Android Version you're using?
[Nexus S Android Development] Bamdroid:
I like taichi's kangs as well but it sounds like you may need to get skanktafied. Go with gearhead's kangs n try Trinity. I haven't lost my data yet since I went back to the skank. Just saying ...

私のネクサスSから送りました
[Nexus S Android Development] noobiekins:
my phone finally had a bsod after it sleeping on T11-1910
[Nexus S Android Development] intheb0x:
rooted stock gwk build.
[Nexus S Android Development] Rem3Dy:
How are you running windows on your phone :-)
[Nexus S Android Development] simms22:
its seems like most(not all) the people that have issues with trinity are running a stock rom.

---------- Post added at 01:07 PM ---------- Previous post was at 01:04 PM ----------

taichi is a skank too :eek:
[Nexus S Android Development] the_trade_place:
I'm running brainmasters miui on a nexus s. I've tried everything. Simple flash, wiping everything and flashing, flashing along with factory reset. Phone just does not like Trinity.

Actually now that I think about it. I do get random reboots with all kernels that use aggressive undervolting
[Nexus S Android Development] benrees21:
Or MIUI. People need to get some CM7/NSCollab in their life haha.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] morfic:
Usual 1ghz: bus = 1000/5

Thermite 1ghz: bus = 1000/4

1ghz is what makes thermite thermite.
[Nexus S Android Development] belair56:
FuZZ_ playing both sides :rolleyes: He's becoming MasterKang

All his stuff is Kangtastic
[Nexus S Android Development] dsellers2:
Yes, but since I've noticed to have data problems with Taichi Kangs and morfics t11. Gearhead working good with t11 though.
[Nexus S Android Development] simms22:
list of skanks and kangs/kernels/boot animations :D http://goo.gl/hJcWZ
[Nexus S Android Development] intheb0x:
well this is the first time ive had any issue with anything trinity, as long as its not BFS it will work great.

i usually run the TEUV with deep idle mod, but i want to update to the newest, but im unsure what "92deepidle and 95dimmers now moved into 98tweak and removed on flashing of these kernels

Please set your defaults in 98tweak from now on." all that means?

but others also seem to be having bootloops with thermite as well using other roms.
[Nexus S Android Development] simms22:
actually youre right about the bfs and stock roms. it does give issues. with thermite, its probably the 250mhz gpu :eek:
[Nexus S Android Development] red_skittles:
what long term risks does overclocking pose? i assume it shortens the life of the cpu but by how much and would it even matter. if oc'ing takes off 2 or 3 years when the cpu is meant to last for 10 thats not much of a big deal. hypothetically if i ran T1544 as my daily driver over the life of my phone (2 or 3 years) what type of issues could i potentially see if any

And Ive been running the latest thermite on Fuzz Kang for just over a day now with max cpu at 1480 and haven't had any reboots or hiccups so far
[Nexus S Android Development] franciscofranco:
Morfic, just in case you don't know ck kolivas released BFS 0.413.
[Nexus S Android Development] Serious_Beans:
:( teuv w/ deep idle just wont run stable on my phone, I get worse battery life than with regular teuv, I'm just going to stick with the regular teuv, I've used kangs, aosp and stock, nothing works :/ oh well at least I've got teuv lol.
[Nexus S Android Development] simms22:
im sticking with the regular teuv as my daily driver too. so far this ones my favorite http://morfic.euroskank.com/simka/TEUV-S22-04102011.zip
[Nexus S Android Development] ellesshoo:
I've been running CM7, usually a recent nightly build (no kangs), and still any trinity with 220mhz bus or greater doesn't run for very long, even on a completely fresh wipe/rom install. It is not related to cpu clock because I can run T12 and T13 fine but T11 and TEUV are totally unstable.

I guess my point is that while I agree users of CM7 are probably less likely to have issues with trinity vs using some obscure custom rom, CM7 won't magically make these kernels work for them.

Also, aside from bus speed, I tend to experience more issues with the lazy governor than with ondemand.