• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Uberfast Snap 7.6 w/ turbo released!

has anyone tried to use SETCPU after flashing to this rom?
I just grabbed it, for the first time, and I can't really adjust the sliders on the main screen; it's not getting superuser access from my evo now...Strange, using unrevoked 3.2, and the ROM works great..
 
has anyone tried to use SETCPU after flashing to this rom?
I just grabbed it, for the first time, and I can't really adjust the sliders on the main screen; it's not getting superuser access from my evo now...Strange, using unrevoked 3.2, and the ROM works great..


i was having a bunch of FC's with setcpu. i downloaded overclocked widget from the market and all seems to be good so far @ 1.19ghz
 
funny, I uninstalled the version from the market, and grabbed it from xda, and it works fine..
I get fc's with this kernel and cyanogen when my evo changes orientation from portrait to landscape almost all the time, but otherwise, not usually...weird, huh?
 
I was getting FCs after i activated turbo... but i just reinstalled SetCPU and it works great now, i have no problems whatsoever with this CM6-Snap, only that i miss a couple of things about Sense
 
I was getting FCs after i activated turbo... but i just reinstalled SetCPU and it works great now, i have no problems whatsoever with this CM6-Snap, only that i miss a couple of things about Sense

Same thing happened here. Only difference I do not miss Sense at all.
 
I can see this is a religion to you. After all, if a bunch of people all believe in something, it must be true. Who needs evidence? The kernel has 300k downloads!

You still can't provide any proof or quantifiable measure of what 2400 really means. Your claim is simple:

The fact by itself is sound. Who COULD dispute that? What I'm saying is that Quadrant tells us IO is improved. But no one, including you, can quantify improved perfo rmance. So, assuming your claim above is valid, doesn't that imply quadrant is wrong? Or more likely, somebody found a neat trick to fool quadrant during its measurement? All I'm looking for here is improved performance. If it were true, I would have stuck with the quadrant slayer build last month.

As you say, sometimes you succeed, sometimes you fail. The kernel uncap was a success. Quadrant slaying, not so much. I'm sorry you can't see that. So, I'm done with this thread and out of your hair, as you requested.

I'd like to say that we will miss your pontificating, but we won't. You put down benchmarks as unreliable, but then reject the testimony of those using this kernel as well. Then you lambast the developer for not providing evidence. If benchmarking is not evidence and user testimony is not evidence, WHAT is evidence?

IMHO, you are not even in the game here. You sit on the sidelines hurling insults at the players on the field. I happily anticipate the release of YOUR kernel.

PS. If you observe the Quadrant bench as it is running, you will clearly see that the db r/w portion goes MUCH faster than with kernels not optimized by Turbo. So if turbo uses some "trick" to increase I/O speeds, how is that not a good thing? I guess you also believe the speed claims made by ssd's are also bogus?

I don't think you are nearly as clever as you think you are.
 
anyone else getting this error when phone rotates from portrait to landscape? driving me nuts..
"The Process android.process.acore has stopped unexpectedly, Please try again
 
well, I love this rom/kernel combo, so I cant imagine changing it..
I guess I will just deal with the FC when i go from portrait to landscape..
 
well, I love this rom/kernel combo, so I cant imagine changing it..
I guess I will just deal with the FC when i go from portrait to landscape..

U should try wiping and reflashing.... that should do the job, if u don't mind having to restore apps etc.
 
using overclocked widget @ 1.19 all my personal apps installed.

2el8mbm.jpg
 
I tried this the other day and was getting FC android process as well. Tried doing full wipe then flash cm6 then snap. Finally got it working then ran asphalt and screen started pixelating. I pressed the home button and then there were lines on the screen. I gave up after that.
 
quick question about this kernel; once you have it on your phone, if you change roms, and reflash this kernel onto your phone, do you have to activate Turbo mode again?
I read that you do not, but, after going from Cyanogen 6.0 to a nightly today, I wiped, and reflashed, and did not go through the process of turbo mode; even though the phone seems fast, my quadrants went from 2300 to 1450...I know turbo mode has to be activated on the first reboot after flashing, so I dont want to do it after the fact, but I had read that it only needs to be activated the very first time you put this kernel on your phone..

Anyone have thoughts on this?

thanks
 
I'd like to say that we will miss your pontificating, but we won't. You put down benchmarks as unreliable, but then reject the testimony of those using this kernel as well. Then you lambast the developer for not providing evidence. If benchmarking is not evidence and user testimony is not evidence, WHAT is evidence?

IMHO, you are not even in the game here. You sit on the sidelines hurling insults at the players on the field. I happily anticipate the release of YOUR kernel.

PS. If you observe the Quadrant bench as it is running, you will clearly see that the db r/w portion goes MUCH faster than with kernels not optimized by Turbo. So if turbo uses some "trick" to increase I/O speeds, how is that not a good thing? I guess you also believe the speed claims made by ssd's are also bogus?

I don't think you are nearly as clever as you think you are.

I'm pretty sure that's uncalled for now, if continue to read further on they amicably settled their differences already.

I would like to say that this has been a very informational thread and thanks to all the detailed posts.
 
If anyone has GL Benchmark can you guys confirm if you get the same results I got below. There are 2 PRO ES 1.1 testing and I chose the very first one on the list. The other test was smoother and couldn't tell much difference so I decided not to use that one. I can record that one if anyone else wants to see it.

Edit: I tried enabling turbo but after it was done I got a flash screen loop. Tried several times but no luck so i can't test with turbo on. Can someone upload a video with turbo on. Below is the link to get the GL benchmark apk. There's no Evo as selection so I just chose the Incredible.
http://www.glbenchmark.com/

Cyanogen CM6 R2 stock
YouTube - GL benchmak HTC Evo running Cyanogen CM6 R2
CM6 R2 with Snap 7.6 turbo disabled
YouTube - GL benchmark HTC Evo with Cyonogen CM6 R2 with Snap 7.6 Kernel turbo disabled
 
I'm having an isse with the SnapTurbo Kernel, I flashed CM-6 and everything was working fine, i then flashed ST and now my Evo's four touch sensitive buttons no longer light up.
Is this a problem with the Kernel?
And how would I, if I had to, uninstall the kernel?
 
***very important!!!!!make nandroid!!!***evo 4g clockworkmod just flashed over on my (cyanogen 7.0.0-RC2-Supersonic) used (snap 7.6 bfs) quadrant score of (1757) . make sure to reboot after snap did a reboot wait like 5 min then do one.GOOD LUCK!!!

***question*** whats the best rom for snap 7.6?
 
Back
Top Bottom