Root Cyanogen TAZZ v 3.0 Vanilla

[ppbb]

Just flashed this over Tazz v 2.0

also installed the CFS kernel and all seems to be very snappy, quick. The new keyboard is pretty stellar too.

I flashed the Dark Froyo them V 1.0 no keyboard ( as I really dig the keyboard that came with Tazz V3.0)

so far real happy with this set up. I have the dark theme, a killer keyboard and what seems to be an even faster rom than before.

Tazz the dev is very responsive and comes up with some killer fast roms.

 

[erisuser1]

also installed the CFS kernel and all seems to be very snappy, quick.

RETRACTED - see note.

Make sure you that set all of your SetCPU profiles that use the "interactive" governor to have minimum frequencies no lower than 245 Mhz. It might be possible to set your "Screen Off" profile lower, but only if you use the "ondemand" governor for that profile.

eu1

[ Edit ] I'm having troubles with SetCPU and CFS2 kernels - seethis post below in the thread (#11)

 

[ppbb]

Make sure you that set all of your SetCPU profiles that use the "interactive" governor to have minimum frequencies no lower than 245 Mhz. It might be possible to set your "Screen Off" profile lower, but only if you use the "ondemand" governor for that profile.

eu1

actually i'm not using set cpu. Am I missing the point of this kernel by not overclocking/underclocking?

I'm running no set cpu, jit on, compcache on, vn heap set at 24. seems to be quicker than Tazz v 2.0

 

[ppbb]

just installed set cpu set the profiles to interactive. then set the main slider to 710/245 and phone rebooted.

i've had numerous problems with set cpu. any settings over 604 freeze instantly. If OC to 604 isnt that lower than the stock setting for this rom? Wouldn't I be better off not running set cpu?

 

[Conap]

just installed set cpu set the profiles to interactive. then set the main slider to 710/245 and phone rebooted.

i've had numerous problems with set cpu. any settings over 604 freeze instantly. If OC to 604 isnt that lower than the stock setting for this rom? Wouldn't I be better off not running set cpu?

it is already set at 710/245 so you are right in not needing setcpu if those are the speeds your gonna clock at anyway....you won't be missing out on anything...governer is interactive by defualt.

 

[ppbb]

it is already set at 710/245 so you are right in not needing setcpu if those are the speeds your gonna clock at anyway....you won't be missing out on anything...governer is interactive by defualt.

Conap, thank you for your contributions to the Eris rooting community. The kernel and your roms are top notch. Thanks!

 

[erisuser1]

just installed set cpu set the profiles to interactive. then set the main slider to 710/245 and phone rebooted.

i've had numerous problems with set cpu. any settings over 604 freeze instantly. If OC to 604 isnt that lower than the stock setting for this rom? Wouldn't I be better off not running set cpu?

RETRACTED - see note.

Well, it sounds like maybe you shouldn't be using it

Although if you were previously running faster than 604, something is a little odd: the maximum speed your phone can run is determined by the hardware alone - the ROM software might change the probability of a timing fault, but that is sort of a 2nd order effect.

The kernel builder has the option of setting the defaults for the min/max clock speed - offhand I don't know what they are for Tazz 3.0. If the minimum is already set to 245, then I suppose that there is little to be gained in the way of battery reserve by using setCPU for a CFS kernel at this time - unless a 19 Mhz min profile can be used with an ondemand governor for the "Screen Off" profile.

eu1


Edit: oops, I see I'm late to the party - again!

[ Edit2 ] I'm having troubles with SetCPU and CFS2 kernels - seethis post below in the thread (#11)

 

[lukesdiesel]

I'm doing a Nand Backup right now then I am going to do a full wipe and install Cyanogen Tazz 3.0 Black Rain

 

[doogald]

just installed set cpu set the profiles to interactive. then set the main slider to 710/245 and phone rebooted.

i've had numerous problems with set cpu. any settings over 604 freeze instantly. If OC to 604 isnt that lower than the stock setting for this rom? Wouldn't I be better off not running set cpu?

Ok, off topic a bit, now I am wondering if this is the reason why you are having problems flashing Nonsensikal. Many of them are overclocked by default to a maximum of 710. I wonder if it is because your phone cannot handle that speed as it boots for the first time and the phone tries to run at that speed.

See this thread, starting with this post.

 

[ppbb]

Ok, off topic a bit, now I am wondering if this is the reason why you are having problems flashing Nonsensikal. Many of them are overclocked by default to a maximum of 710. I wonder if it is because your phone cannot handle that speed as it boots for the first time and the phone tries to run at that speed.

See this thread, starting with this post.

Could be. But the weird thing is tazz 2.0 & 3.0 both work on my phone. I think my phone must be possessed.

 

[erisuser1]

FYI -

for the moment I think I should not offer any opinion at all about using SetCPU with the Decad3nce/Conap CFSV2 kernel - I'm having nothing but trouble no matter what settings I use when I use SetCPU (v2.0.2)

The odd thing is that trouble doesn't develop immediately - in the last trial I attempted, I used only interactive governor profiles on a CFS2 overflash of Tazz 2.0, with minimum clocking no lower than 245 Mhz... and the first sign of trouble showed up 9 hours later. (I used the phone for texting and web browsing off and on during that time).

The trouble shows up when you wake the phone from a screen off condition; immediately after that, the phone seems normal but then slows down progressively over time scales of a small number of minutes - perhaps 3 to 5 - eventually to the point of unresponsiveness.

I'll run another pass at the same ROM + kernel replacement; but without the use of SetCPU or Autokiller. In the meantime, I can't say that SetCPU is causing the trouble (I'm not using the widget, BTW), although I think that Decad3nce believes that the SetCPU app is the source of the trouble - I'm not seeing anybody else complaining about their phone freezing up, so that (SetCPU) seems like the first place to look.

eu1

 

[ppbb]

i'm starting to notice similar unresponsiveness and it is after i wake the phone up.

My phone is frozen now and may have to batt pull. This has happened twice so far today.

And i am not using setcpu. was installed, then uninstalled earlier today.

gmail app is painfully slow right now.

 

[ppbb]

seems like gmail is the most affected. other apps function seem to be okay. Gonna try to flash a newer version of the gapps.

 

[erisuser1]

ppbb,

Have a look at the CFS thread over on XDA - the problems you are experiencing have to do with a problem with the way those kernels were compiled. Fortunately, it has nothing to do with the CFS scheduler - the low memory killer was accidentally left out.

For anybody else who is reading this, this has nothing to do with the Tazz 3.0 release.