Originally Posted by jrny99

and it wipes your evo for you so no wiping 3x !

Oh yea I forgot about that it does pretty much everything for you, some devs had trouble at first using it tho and errors, but new things take practice and there's a tiny learning curve not really tho its a touch UI which is a lot better than using volume keys

Sent from my PC36100 using xda premium

Originally Posted by jrollercoasters

Does under world work as good as the nitrous sbc Rom does, because I've used under world and its good and all but this kernal gives me crazy good battery life, but it might just be the Rom, its only my second day here haha, also will it might help, if I just uc it through set CPU or is it different through viper mod? Because I don't even use past 103 mhz so I lowered it to 103 but it dosent seem like much of a difference with battery life

Sent from my PC36100 using xda premium

From http://forum.xda-developers.com/show....php?t=1369817

Q. "I'm going to set scaling min freq as 100 mhz because my kernel supports it. Hope there's nothing wrong in doing that."

A. Wait! You may want to stay away from using 100mhz during screen-off or screen-on states for three reasons 1) It seems 100 mhz uses more power than 200 mhz. According to tests, 100 mhz accounted to 1 W /GHz and 200 mhz to 0.7 W / GHz, when both the cores were online. 2) 200 mhz can finish same task faster compared 100 mhz and thus hit deep idle soon. 3) 200 mhz is the 'sweet spot' of frequency in SGS II. ie, the frequency used in the calculations based on the optimal energy to run (Ex: In Milestone it's 550 MHz). So , 'energetically efficient' frequency for our CPU is 200 mhz.

Originally Posted by pipefitter

From http://forum.xda-developers.com/show....php?t=1369817

Q. "I'm going to set scaling min freq as 100 mhz because my kernel supports it. Hope there's nothing wrong in doing that."

A. Wait! You may want to stay away from using 100mhz during screen-off or screen-on states for three reasons 1) It seems 100 mhz uses more power than 200 mhz. According to tests, 100 mhz accounted to 1 W /GHz and 200 mhz to 0.7 W / GHz, when both the cores were online. 2) 200 mhz can finish same task faster compared 100 mhz and thus hit deep idle soon. 3) 200 mhz is the 'sweet spot' of frequency in SGS II. ie, the frequency used in the calculations based on the optimal energy to run (Ex: In Milestone it's 550 MHz). So , 'energetically efficient' frequency for our CPU is 200 mhz.

I know that haha all my minimums including my profiles are set to 245 I was talking about my max its set to 1.03 ghz

Sent from my PC36100 using xda premium

Originally Posted by jrollercoasters

I know that haha all my minimums including my profiles are set to 245 I was talking about my max its set to 1.03 ghz

Sent from my PC36100 using xda premium

Do you mean 1.3?

Originally Posted by raafaell

Do you mean 1.3?

1036 mhz

Sent from my PC36100 using xda premium

Rom, radios, reboots

---

[/COLOR]

Originally Posted by hotstocks

Well after a month of frustration with trying to figure out the reboots and reboot loops in Nitrous, I gave up and nandroid back to my stock Sprint rom with root and freedom kernel. So far NO reboots or loops, but too early to tell for sure. I KNOW it is not the kernel, I have tried many and they all do the reboots with Nitrous Rom. It is definately something in Nitrous Rom, and Definately tends to happen more when using multiple radios. (ie. when I am using gps and bluetooth, or when I am on 3g and put on wireless, or when I am using all 3.) With stock rom/root my kids can both wifi their itouch and download apps from my phone's 3g/wifi. With Nitrous roms (at least the last 2 versions) it will crash loop within minutes every time. The original Nitrous seemed to work fine for me, but honestly I am having a better experience with Sprint stock and rooted with any kernel (lionfish, poonsense, freedom)

Yesterday I had gps/bluetooth on, got a cell call and 2 minutes into the cell call reboot loops!! GRRR! If my stock rom does this in the future I will let you guys know it was my hardware, but all things are pointing to the Nitrous Rom not playing nice with multiple radios.

I read in the OP that there are some 3G data tweaks baked into this rom, which seem to be killing my d/l bit rate. Upload is good, but I was hoping someone could refer me to the **data* or whatever (EPST??) codes that govern this activity so I might adjust it back to stock.

'cause I love *everything* else about this ROM, but connection speed (esp d/l) is kind of a big deal... To me, anyway.

Sent from my PC36100 using Tapatalk 2

Two things I really miss about running CM ROMs that aren't included here are:
1) Volume-button screen-on option, as these phones are mostly 2 years old and the power button tends to wear out even with standard use.
2) Back-button hold app-kill feature.

Are there after market apps that can provide this functionality? Or is there a chance we could expect these features in the next version, or a patch?

Either way, lovin' the ROM big time, & serious props 2 the Dev.

Sent from my PC36100 using Tapatalk 2

@raafaell

Were you able to bake in the new kernel for your ROM in this release? Any addition system tweaks are CPU tweaks to accommodate the new Kernel?

Guys, try linpack

---

Out of curiousity, can some of you guys run linpack
a bunch of times in a row and see if it ever says
inaccurate result or inconsistant result under Precision?

I do not have mine overclocked, but can get it to say those
two things every few runs. I removed all battery saver and task
killer apps, which seemed to have helped somewhat. But I don't
know if linpack should ever say inconsistant or inaccurate Precision.
Is this normal due to multitasking, or is my kernel a problem (freedom), ram or cpu going?
I just downloaded stability test and ran all 4 tests for 1/2 hour each with NO errors.
I think linpack app is wrong, since stability test has a linpack that produces no errors,
as well as stressing cpu, ram, and gpu. It is definately the radios, need to know
of a stability test for bluetooth, 3g, wifi, and gps to figure this out! Any suggestions?

Thanks