yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] polobunny:
Oh dang no wonder. Does it boot at 1480? My phone can't seem to handle anything past 1.3GHz, unless I apply lots of voltage to it. Not touching this more though, otherwise I might end up with molten plastic.

Happy and jealous. :P

Haha I did notice the naming convention was a bit funky, but that's why there's file dates, right? Would still be nice if they were nicely ordered and everything. That's the OCD part of me talking.

So are there any LESS extreme Thermites? Yes, quite the irony, but just wondering if you did anything I could actually test. :)
[Nexus S Android Development] simms22:
it(thermite15b) boots at 1ghz. and the bus speed at 1ghz is 250.666 mhz. and it makes a wonderful kernel with use at 1ghz. battery life is surprisingly good.
[Nexus S Android Development] red_skittles:
running the thermite15b at 1504/1504 on demand. test 6/6. On 4/6 it was 5162. a little short of 6000 though:p
[Nexus S Android Development] morfic:
There are less extreme Thermite kernels.

I call them Trinity
[Nexus S Android Development] ZeDestructor:
Someone called?

@morfic: is there a way we could get the flashable zip online dump as an ftp folder? It would make my life easier when checking what I have and don't have as well as preserve modified dates. rsync would be nice as well... it would make me learn how to use it at any rate :P
[Nexus S Android Development] morfic:
So i didn't wipe **** and all my apps are there.

Going to wipe in a little bit

and don't flash trinity:

I/SurfaceFlinger( 429): SurfaceFlinger is starting

I/SurfaceFlinger( 429): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...

E/FramebufferNativeWindow( 429): couldn't open framebuffer HAL (No such device)

E/SurfaceFlinger( 429): Display subsystem failed to initialize. check logs. exiting...

but at least this was interesting:

kernel is 2.6.35.7 o_O
[Nexus S Android Development] melvinchng:
Newest beta was just released.

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] morfic:
i understood the rsync question but failed to understand the part about the online dump?

not my box/account so i can't easily say what works and what doesn't
[Nexus S Android Development] morfic:
stop hammering it then:

Service Temporarily Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

EDIT: Thanks for stopping, downloading. :P
[Nexus S Android Development] melvinchng:
As they shown the about phone, it is running 2.6 kernel and not 3.0.

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] tehgeekguy:
The final kernel could easily change, since this is a straight SDK port. If you launch the SDK emulator, you would see the same kernel version number, which shows it's not device specific.

That's not saying the kernel WON'T be 2.6.x, but that doesn't mean it WILL either. My point is, this is a port, so a lot of the "details" you see in there can't be truly trusted.
[Nexus S Android Development] melvinchng:
some people claimed that trinity kernel is working in ics.. some work, some not.
[Nexus S Android Development] kecinzer:
So morfic, you don't want to implement battery cosmetic fix for 100% state?
[Nexus S Android Development] roshga:
He did in termite addition.

Speaking of termite addition, with 15b I'm getting outstanding battery! 89% left after 4.5 hours of low use!

Running 400-1000 lazy, I guess that raising the min frequency is helping the deep idle to kick in quickly : D
[Nexus S Android Development] kecinzer:
Where I can get termite edition?
[Nexus S Android Development] roshga:
Look in previous posts....
[Nexus S Android Development] djjonastybe:
I am using the UV version. Can we have setcpu support or can we know the voltages?
[Nexus S Android Development] polobunny:
I see what you did there. :p

Mostly theorizing about a 1Ghz CPU 250mhz bus one or something similar though.

For the record and those interest, with TEUV-S22_04102011 I'm getting from 95 to 85 battery in around 15 hours of mostly idling, some very light SMS and my alarm clock in the morning.
[Nexus S Android Development] Lazat:
Why would the higher min frequency make the phone reach deep idle faster? :)
[Nexus S Android Development] polobunny:
Takes less time for the phone to complete the operation, thus reaches idle quicker. Spending more time idling = better saving. Or so is the theory.

Either way, try it with a minimum frequency of 400MHz, it's definitely snappier than having it at 100MHz. I used to have mine set at 100MHz but when waking up it took a few moments to be usable. With 400MHz it's usable right as I wake-up my phone.
[Nexus S Android Development] ZeDestructor:
Interesting find you have there. A friend recently did something similar on his Desire...

In other news, my chip runs cooler on Thermite than on T144... I have no idea why... And before you ask, its definitely hitting 1.5GHz, Quadrant and CF-Bench scores say so.
[Nexus S Android Development] polobunny:
Not my find however, I think Ezekeel or franco might have pushed this theory forward.

Looking at the battery stats it does seem like the phone reaches idle nearly as soon as the screen is turned off VS taking a few moments to reach idle at 100MHz. Using fictive values, a second spent at 400MHz seems to give better battery than 5 seconds at 100MHz.

400MHz seems to be an arbitrary value though (as in everyone is doing it, but nobody really made any experiments to find the optimal one) but 200MHz might turn out to be enough. And since 200MHz uses less voltage, it could save battery even more.

Then again, we wouldn't be talking about day and night here between 200MHz and 400MHz if 200MHz turned out to be "enough" not to stall.
[Nexus S Android Development] benrees21:
Yea but if the minimum is set to 200mhz then when it enters idle, it will be idling at 200mhz using more battery then 100mhz? I'm probably thinking wrong but just checking before I set it like that.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] polobunny:
No that's the thing. There's more states than just "idle", some which save more power and put the phone in a near inactive state. That's the point of deep idle, reaching a deeper state without sacrificing functionality.
[Nexus S Android Development] benrees21:
Ok thanks. I will set the minimum to 200mhz then.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] yaronyud:
by the way you can also see that the voltages are exacly the same... so why not enjoy that a tiny bit more speed...
[Nexus S Android Development] benrees21:
I can only set it to 400mhz minimum.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] belair56:
Morfic does not have a 200 step (level), others do.
[Nexus S Android Development] polobunny:
You sure?

:p
[Nexus S Android Development] red_skittles:
Morfic, are the thermite kernels seperate from Trinity ( as in will we see a thermiteEUV, thermiteUV, etc) or will the thermite features be incorporated into Trinity
[Nexus S Android Development] Maximilian Mary:
The UV kernels have 200. The OC kernels do not.
[Nexus S Android Development] roshga:
LOL! fail.
[Nexus S Android Development] coloxim:
Hi Nordic..i 've tried your last t11

...

Is fantastic..very fast and nice battery...

But sometimes I've the reboot...

I'm using kang..

Another thing..I've disabled deep idle..but if i use CPU spy..i can see 87% deep idle..why?

Maybe the voltage are to much low?

Inviato dal mio Nexus S
[Nexus S Android Development] polobunny:
Nah it's just an older TEUV morfic made for simms22. No deep idle, just lazy. My daily driver, very stable. I'm waiting until deep idle is absolutely stable before I use it all day long or in mission critical moments.
[Nexus S Android Development] dario3040:
Don't fall in the Galaxy S II trap, rather wait for the third nexus phone.

Galaxy S II is worth it, but why buy it when the quad cores are so close.
[Nexus S Android Development] simms22:
thanks pickles, i agree with that statement. id rather wait too :D
[Nexus S Android Development] tangcla:
Hi guys, back on Trinity UV11, Netarchy 1.3.5 and 1.3.6 give me random reboots on my phone! :)

Is the one on the first post (Trinity UV11 - 2.3.4 - cm7 NS+4G - w/ VS8 - BLN - 2.6.35.13 - bfs404) the best one available to use?
[Nexus S Android Development] simms22:
well, that one isnt the newest, but it would work well. you can try it if you would like. personally, i like and am using this one right now http://db.tt/K9cBy96 it runs great and has voodoo updated to version 9 :D
[Nexus S Android Development] window7:
spicy version is the best :)

However, if you need the Voodoo v9 version, that's not the best one :D
[Nexus S Android Development] window7:
the SKUT11 just difference of boot image right? :confused:
[Nexus S Android Development] dario3040:
I think so, most of them are the same, maybe a little tweak in the bus speed, or voltages.
[Nexus S Android Development] simms22:
difference is in the boot.img(the one i linked has the trinity mushroom cloud), it has voodoo 9, plus slight difference in bus speed/voltage, and a little more. its a similar kernel but different.
[Nexus S Android Development] lichti1901:
Is this one better than the special Edition one?

Im asking because the special one was the best Kernel ive ever tried!

Best regards
[Nexus S Android Development] tangcla:
Hm, I don't mean to be a pain, but do you have a kernel without to bootup sounds? It's too distracting you it reboots at work. :(
[Nexus S Android Development] dario3040:
Well, there are 2 things you can do, depending on the situation of course.

If you have already flashed it, you can manually remove it, I think I might even make a script to do it xD

It's located at /system/media/audio/poweron

You can remove it with Droid Explorer or Root explorer.

If you don't want the sound after flashing the kernel, open it in winrar, and go to

System/media, and delete the folder called "poweron", or whatever it's called.
[Nexus S Android Development] simms22:
you can delete it. its in /system/media/audio/poweron/, just delete the .ogg file ;)
[Nexus S Android Development] tangcla:
Ahh, win :D thanks!
[Nexus S Android Development] tangcla:
I'm looking in SetCPU and despite the sliders allowing the choice of 1100MHz, the display only shows that I am getting 1000MHz, why is this?
[Nexus S Android Development] dario3040:
Which kernel?

Try deleting the SetCPU data.
[Nexus S Android Development] tangcla:
I'm using the UV11 as linked to in this post.
[Nexus S Android Development] tangcla:
btw - tried clearing data for SetCPU in Settings --> Applications --> Manage applications, still no luck :(
[Nexus S Android Development] dario3040:
Only thing I can think of is: Reinstall Setcpu if you haven't done so already.

Or go to recovery and: Wipe dalvik cache, and cache, then reflash and reboot.
[Nexus S Android Development] simms22:
its all normal, dont wory. its something with setcpu. it shows an 1100 option but shows the max frequency as 1000. the setcpu widget reports it right, as 1100. you can use other apps to look at the cpu(like system info). theyll all report 1100. i have the same with my setcpu. or, you can just bench it. it doesnt benchmark like a 1ghz kernel :p
[Nexus S Android Development] window7:
Yea, simms22 was right. Trinity kernel is very special that set cpu cant handle the "time in state" and "phone info" correctly :p
[Nexus S Android Development] roshga:
@polobunny I was joking.

you where quoting about the 200mhz step and posted a picture without any sign of 200mhz... :)
[Nexus S Android Development] polobunny:
Oh haha, just wanted to show it could go as low as 100MHz if desired, that 400MHz wasn't the minimum.
[Nexus S Android Development] simms22:
off subject(except photo'd w/the ns running thermite15b)..

giant nyc rat! :eek:
[Nexus S Android Development] polobunny:
Your lunch? :D
[Nexus S Android Development] simms22:
was debating that. theres enough meat on it, thats for sure! actually i let him go around the corner from where i work. the poor thing was crying the whole time, and i couldnt bare harming it.
[Nexus S Android Development] SA-07:
Lol

Scrumptious ;D
[Nexus S Android Development] polobunny:
Normally the head gets caught and they choke, not the legs.

Simms22 the crackflasher softie. ;)
[Nexus S Android Development] dario3040:
Nawwwwwww <3333333
[Nexus S Android Development] benrees21:
Sends a shiver down my spine...ewww!!

I flashed Thermite15 S22D

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] belair56:
Really?

I don't know.
[Nexus S Android Development] GeezyAF:
It's already been stated that only the under volted kernels have the 200mhz step.
[Nexus S Android Development] morfic:
I refer to this as Bigbore....I had them before, they will soon return.

Don't know why I use plural there.....
[Nexus S Android Development] morfic:
Thermite is a Trinity flavor.

What thermite features?
[Nexus S Android Development] polobunny:
Ah interesting. I might not have been around yet when you were compiling those. Only really became a crackflasher around august or so and I was mostly toying with netarchy's kernel (it was a bit more active back then).
[Nexus S Android Development] kevlars9:
Hey I have a question. I haven't been following this thread since about early September because I was waiting for a replacement nexus. However I tried flashing thermite 15 b &d on my ns4g and both times I couldnt get passed simm's awesome splash screen. Is this common for some??
[Nexus S Android Development] melvinchng:
I saw norfic two page back
[Nexus S Android Development] morfic:
Thermite asks a lot from a phone.

It might not boot.

If it does it's smooth

Think of thermite as "beyond Trinity" even if it's a Trinity flavor.
[Nexus S Android Development] ZeDestructor:
I ran SetCPU stresstest for some 3 hours or so today. It gets as hot as T144 under very heavy load, but otherwise stable. Under normal use, it runs cooler than stock kernel! :O

Also, first boot may or may not be successful as caches are rebuilt, so I safely ignore my first-boot freeze :). Of course, ymmv depending on how awesome your chip is. Mine for instance luuurves voltage :D
[Nexus S Android Development] jacky169:
Support for this kernel thanks for updates.

---------- Post added at 07:42 AM ---------- Previous post was at 07:36 AM ----------

T1544-S22-05102011 (1.54GHz with 220MHz bus/gpu)

the link is dead , please reupload thanks again.
[Nexus S Android Development] Bamdroid:
Just played 9mm for an hour running Thermite (1000/100) and it was very smooth, no lag and just awesome... I can die now.

私のネクサスSから送りました
[Nexus S Android Development] morfic:
Not yet, wait until tomorrow.
[Nexus S Android Development] coloxim:
Any update for Trinity?

Inviato dal mio Nexus S
[Nexus S Android Development] vis80k:
meaning new kernel update tomorrow ;)
[Nexus S Android Development] skinniezinho:
Anyone know the voltages from TEUV and TUV?
[Nexus S Android Development] coloxim:
About battery?

Inviato dal mio Nexus S
[Nexus S Android Development] polobunny:
http://morfic.euroskank.com/simka/
[Nexus S Android Development] melvinchng:
I'm waiting for tuv update(s) :)

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] coloxim:
T11 too..sometimes reboot..

Inviato dal mio Nexus S
[Nexus S Android Development] benrees21:
I'm gonna give TEUV a go until something else comes up.

EDIT: I actually flashed: BBT-S22-27102011c-b.zip and it is good. Really like it so far.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] Naa Laa:
Waiting for TEUV stable update!!! :cool:
[Nexus S Android Development] simms22:
haha..

you found the Big-Bore Trinity being tested right now :p
[Nexus S Android Development] polobunny:
:O! Need to flash it later.
[Nexus S Android Development] morfic:
http://goo.gl/QS4XD voltages.h
[Nexus S Android Development] morfic:
http://goo.gl/7jvCd vs http://goo.gl/KlZlS

Which do you prefer?

Both are 1GHz max Big Bore kernels.

Very similar, would just like to hear preferences.

What a big bore kernel is? It's like a Thermite, but with the top speed cut off and instead 1GHz max with a 250MHz bus.

Why? If running Thermite set to 1GHz max is the same? It's not.

Big bore runs the same as Thermite set to 1GHz, but at considerably lesser voltage.

Being 1GHz max, you also have the 200MHz step some seem to be missing.

So big bore is really nothing like Thermite set to 1GHz ;)
[Nexus S Android Development] coloxim:
Sorry but the different between first and second...i don't understand ..my English is very bad. I don't undestend nothing about this new..someone can resume it? Please..

Inviato dal mio Nexus S
[Nexus S Android Development] morfic:
Those who want to participate should run both.

And tell me which one they like better.

I will not tell you what the difference is until after i get feedback from people.

Both are equally safe, that's all i can say.

I want to avoid placebo, thus i will tell those who participate, AFTER they gave me feedback :)
[Nexus S Android Development] tempera:
Is the big bore kernel undervolted? Good on battery life?
[Nexus S Android Development] morfic:
little bit undervolt is left in him, yes. but not at top end.
[Nexus S Android Development] tempera:
Better battery life than t11 1100/100 lazy though right?
[Nexus S Android Development] Bamdroid:
All I wanna know is if one of these *****es make nachos!? I've been waiting FOREVER!!! ;)

私のネクサスSから送りました
[Nexus S Android Development] benrees21:
I tried both and prefer c-b + gave me better quadrant score.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] simms22:
i prefer c over c-b. c-b is occasionally slow to wake and seems to drain the battery at a faster pace(for me). benchmarks are about the same.
[Nexus S Android Development] benrees21:
Ok now I'm gonna flash C again!! Lol.

EDIT: PM me and tell me the difference, I won't tell!

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] morfic:
You should start to ignore me if i answered this with Yes or No.

I built the BBTs last night, NOONE can know any such thing by now, especially since i spent most time charging it since then, while i slept.

give us some time ;)
[Nexus S Android Development] morfic:
Those who want to experiment with race to idle and battery savings, i suggest using 200MHz on the BBT and *UV kernels, not 400MHZ, as 100mhz and 200mhz have the same voltages, race to idle might work.

At 400MHz, voltages are higher and race to idle may or may not make up for the increased consumption.
[Nexus S Android Development] franciscofranco:
I still think 400 is the best minimum frequency for the race to idle.
[Nexus S Android Development] Igotsanevo4g:
Can't boot either one. Fml.

Guess ill wait for a new teuv
[Nexus S Android Development] morfic:
I know you do.
[Nexus S Android Development] morfic:
http://morfic.euroskank.com/simka/2710/

for those seeking other speeds
[Nexus S Android Development] benrees21:
Is the T13 built the same as BB or Thermite?

I want a T13 with a 250 bus

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] king23adrianc:
so teuv2710 is same 220mhz bus/gpu?
[Nexus S Android Development] morfic:
All T* are built how they were always built.

Same as TEUV still has 880mhz w/ 220MHz bus.
[Nexus S Android Development] Bamdroid:
Received 3 reboots using BBT c version. Once after initial boot up, once accessing camera..then again accessing xda to try and post these results. Not sure what's going on. Going to try BBT c-b. This one isn't working well with me. Outside of that it's pretty effin smooth.

*Edit* I didn't wipe cache/dalvik just flashed kang and kernel.

私のネクサスSから送りました
[Nexus S Android Development] benrees21:
Ok, You should do a T13 with a 250MHz bus. Thanks for BB it's really good.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] morfic:
Not possible.

But I'll be looking if it's feasible to have the gpu unlinked from the bus.

I'll see if using a gpu frequency table instead of a divider off of the bus frequency (which makes bus == gpu, unless you want to underclock the GPU) is not only doable, but also "a good idea".

My Goal is to create a kernel where the bus is clocked more agreeable to more SoCs, with the gpu running at a different clock.

Take the 1GHz BBT, it can reach 63fps in nenamark1 without a problem, all thanks to the 250MHz gpu.

But some phones don't like booting a 1GHz kernel with 250MHz bus.

No promises, but that's what i had been thinking about for a while now.

replacing the math after the divider lookup replaced by a lookup of an absolute value

Before i get there i will test if it saves energy if 200 and 400 MHz also use the slower GPU or if it makes for an ugly phone.

But i'm about to head to work (hate nightshift), so this will stay at concept stage until after work/this weekend.
[Nexus S Android Development] polobunny:
Yeah I think I was talking about this with benrees21. 200MHz might be enough for most tasks, making it a better battery saver than 400MHz.

+1 on the unlinked GPU. Now that would be awesome. Gaining control over the GPU separately from the bus could help suck out every last performance bit from any phone, just not the ones able to do X frequency on the bus.

Edit: What do you do for a living, if that's not too personal?
[Nexus S Android Development] benrees21:
Cool!, hope it works out. I will look forward to hearing development on this. Sorry to hear your on a night shift. Have fun lol.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] coloxim:
ok....thanks...

I'll try ...

I'm looking for the best battery...I'll tell you which one is beter for me...

;)

I'll try with and without deep idle...

cause for me deep idle makes more battery drain.
[Nexus S Android Development] Ezekeel:
Interesting idea. But my guts tells me this will not work. I got a feeling the dividers are there for a reason - I guess for synchronizing the different clocks. If you have one clock running at speed x and another faster clock at n * x (n=1, 2, 3, ...), every tick of the slower clock will coincide with a tick from the faster clock. On the other hand if these two clock speeds are not related by a simple integer divider the clock ticks will coincide less often. This could be seriously detrimental for the efficiency or not even work at all. But that is just a hunch.
[Nexus S Android Development] Maximilian Mary:
Cpu = 1152

Gpu = cpu/3

Bus = cpu/5

:D
[Nexus S Android Development] coloxim:
C-b is impossible to use..

Too much lag..

Inviato dal mio Nexus S
[Nexus S Android Development] Ezekeel:
I guess you mean something like 1005.

That would put the CPU in sync with the GPU and the bus, however the GPU and the bus would be seriously out-of-sync - the clock ticks would coincide only every 5 GPU = 3 bus ticks. As I said maybe this is not important at all, however it offers an explanation for the current implementation based on integer dividers.
[Nexus S Android Development] benrees21:
Just had a SOD with BBT C. Gonna try a different one for now. Might go with the latest T13.

EDIT: I'm actually gonna try: THERMITE-S22-optron8.zip

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] coloxim:
With the C I've reboot :(

Inviato dal mio Nexus S
[Nexus S Android Development] polobunny:
Ain't cool enough for 250MHz bus, BBT-S22-27102011c gives me boot loops. :(

What's the specs on TEUV-S22-27102011 though? 220MHz like other TEUVs?
[Nexus S Android Development] Bamdroid:
Running BBT c-b. So far no reboots like I got in version c. However...not as "smooth" as version c. Conundrum. Lol

私のネクサスSから送りました
[Nexus S Android Development] king23adrianc:
try going bak 1 single page and u get ur ans