Related
Hello all!
Just upgraded my wife from the MyTouch 3G Slide to the G2 as she has to have a keyboard and we were on our 5th replacement Slide. So, as she is not the geek that I am, she will not be constantly flashing new ROMs and such. However, I am going to at least install the latest CM and I am looking for kernel suggestions. I already have root, s-off, new hboot, and all that, I'm just waiting for CM7 to finish downloading.
I started using Android with the G1 and constantly updating Radios, as well as ROMs and I currently use a Samsung Vibrant running a TeamWhiskey ROM. It's stable as anything, I like the theme, and CM7 still has some broken stuff on the Vibrant. I'm glad to see that Eugene recently picked up a G2 as he made some bad ass kernels and ROMs for the Vibrant.
So, let's here those kernel recommendations and why you recommend them.
Thanks!
Well am currently using mexdroidmod and their kernel is pretty awesome because its fast and stable. My best advice is to test the diffrent kernel and read through the tread, see what people say about it. All the kernels I have tried are all awesome so you should try them
Sent from my HTC Vision using XDA Premium App
pershoot's kernel. great batt life and OCing
Umaro's kernel has been rock solid for me and has tons of features as well. You can OC all the way to 1.9 Ghz if you so please and it has smartass.
well considering your wife isn't much of a techie.. i say you should go with pershoots kernel because he's always releasing updates and i've never had a problem with any of them. the battery life is excellent if you use the right radio (.17 and .30 have been good to me), but you need to experiment with this though. the phone runs beautifully, just make sure you use superwipe+ to format/wipe so you don't end up with gps issues like many people have had, good luck!
I've run umaro, eugene, pershoot, flippy, pyro, etc etc... aaand I've decided that the provided kernel is pretty much good to go. yeah, there are some little trinkety things with a few of the above kernels that the standard CM7 kernel doesn't support... but honestly, they're worthless to a user who just wants to turn the phone on and have it work.
set her up with the stock kernel @ 245-1017 (I haven't found a reason yet to ditch the ondemand governor, it seems to work best with CM7) and a vanilla gingerbread launcher and she'll be blown away.. that's my $.02
Like said above, CM kernel is great. I've tried most or even all available kernels for CM and finaly decided to stick with original one. It's stable and supports OC (up to 1.5GHz) "out of box", so really, I see no single reason to use the other ones.
Sent from my HTC Vision using XDA App
AllWin said:
Like said above, CM kernel is great. I've tried most or even all available kernels for CM and finaly decided to stick with original one. It's stable and supports OC (up to 1.5GHz) "out of box", so really, I see no single reason to use the other ones.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I'm also thinking about changing the kernal, but only for smartass. Does smartass offer that much of an increase on battery life or anything else? Also, when you OC, do you use SetCPU or just CyanogenMod Settings?
slapshot30 said:
I'm also thinking about changing the kernal, but only for smartass. Does smartass offer that much of an increase on battery life or anything else? Also, when you OC, do you use SetCPU or just CyanogenMod Settings?
Click to expand...
Click to collapse
not at all pooping on any of the guys who swear by smartass/other governors, but the change in battery life is almost unnoticable for me.. the change in performance however can be pretty apparent.
here's my problem with "battery saving" governors:
in order to save battery, these governors are supposed to be more intelligent about which frequencies they select once a task is called... well, that's all well and dandy, but the problem is that the majority of battery-hogging apps (ie streaming music/video, gaming, browsing for a long time, being on the phone, etc) are still going to be battery hogs with or without a fancy governor. the governor isn't capable of making an app that needs a lot of processing power run well at a lower frequency, it can only try to be more selective about which frequencies it uses in order to attempt to save battery life.
additionally, most people use their phones like this: phone is idle (ie screen off), and a call arrives. call ends, phone is back to idle. texting a few people, back to idle. playing a game for 15 minutes, back to idle.
is it really logical to assume that these short bursts of activity are going to benefit at all from a fancy shmancy governor? I doubt it.
I still swear by ondemand or interactive (both work well for me) thru built-in settings if possible (ie cyanogen performance settings). second choice would be setcpu with no profiles (unless you're overclocking heavily, then you should at least have a temp warning profile). at this point, screen-off profiles don't do a damn bit of good, because pretty much every kernel we have for the vision is going to scale down during inactivity.
After the release of Clemsyn's 1.6 GHz Kernel for CM7 based ROMs last night, I immediately switched to it just to see.
But before that I was running Faux123 1.3 GHz.
I'm keeping the Clemsyn kernel for now, simply because I can. My phone can run it with little difficulty thus far and I have a profile to lower the max freq when the CPU gets to a certain temperature. I think I went with about 65 Celsisus.
Before I switched back to CM7 (or rather Neutrino) I was using Wet Dream. I OCed to 1.45 then in attempt to compensate for only half decent webtop performance.
But now I really only do it because I can. Whenever possible, my phone is on the lapdock since I like to HDMI mirror. Battery is not a concern since the lapdock charges the phone and I pretty much always keep the lapdock charger on hand in my bag.
I just thought it would be an interesting subject for the community to discuss as I'm sure it's something that a number of us haven't even thought of and I bet a good number of us fall into the because I can or bragging rights category.
Specific instances of problems OCing helped with in x app or y app might make someone else want to OC whereas someone who doesn't OC might persuade a user like myself to drop it for amazing battery ETC.
Sent from my MB860 using Tapatalk
Why I DO OC.
Right now I have my Atrix OC'ed at 1.45. I'm currently running Alien ROM Build #4.
The CPU has never gotten past ~55ยบ C.
I also have 2 profiles set
1 for Screen off - 800 MHz max.
1 for Battery< 10% -216 MHz max.
This paired with Alien ROM and LP has left me with a buttery smooth experience.
Is the 1.6 OC kernel worth giving a shot? Or does it make the CPU run excessively hot?
EDIT: I didn't really address battery life. I don't notice a huge decrease in battery life, I'm a pretty heavy user- SMS, Web, Video streaming, Facebook, Twitter. Over all OC'ing is definitely worth it to me.
I like to keep mine overclocked because it seems snapier. I use faux 1.45 and its great. Ive noticed clem's likes to make my phone very hot when running video or games and has actually shut my phone down due to heat. If I run clems I like to drop the overclock with setcpu to around 1.3 so it doesnt shut down but seems to get way hotter than faux's. Anything over 1.5 is just going to cause damage to peoples phones and IMO it should not be used so lightly.
I'm OC'd to 1.45ghz I do it for performance and those random times I need to benchmark I want to try 1.5-6 but I can't seem to get them to boot with the ICS mod2 cm7 so till cm9 or neutrino ill just float about with what I have
Sent from my Atrix-4G, stock 2.3.4 (rooted)
No need for 1.6 IMO.
1.3 is plenty for the Atrix. Even Faux 1.0 is fine. Its a phone, not a PC.
Sent from my HTC Inspire 4G using XDA App
I dunno...my webtop configuration may want to take exception to that statement
troycarpenter said:
I dunno...my webtop configuration may want to take exception to that statement
Click to expand...
Click to collapse
+ 1
Sent from my Atrix 4G using Tapatalk
i honestly haven't been able to really tell a difference between 1.0 and 1.3GHz in most of my applications. it definitely doesn't help with system slowdown due to live wallpapers, which is a disappointment.
troycarpenter said:
I dunno...my webtop configuration may want to take exception to that statement
Click to expand...
Click to collapse
Haha, I was in that boat before I switched to HDMI mirroring coupled with VNC or Splashtop (when applicable) from experience, I can tell why Webtop users want OC. You can turn your phone into such a useful computer, and then it falls flat on its face because the inner-workings aren't streamlined. The extra power DOES help in that situation.
But in my actual experience, I haven't seen many realworld benefits past 1.2.
Especially since 1.6 kept eventually shutting down on me after about an hour (assuming there is the same issue as in Clemsyn 1.5, setting your max to a lower frequency than 1.6 won't stick so my temperature profile wouldn't actually work)
My "because I can" mindset is going to leave me stuck on 1.45 though most likely. I keep it maxed at 1.2(or is it 1.1? I'm not using the kernel right now) and then have a profile to ramp it up to 1.45 when it's on the charger (aka my lapdock)
I don't think it is quite the same for Blur based ROMs, but on CM7 1.0 seems perfectly adequate for the Atrix. Even at it's stock speed, it is snappy.
Sent from my MB860 using Tapatalk
I dont overclock. I used to be at 1.3ghz, but I didnt see a big enough difference to keep it. At least on CM7, the Atrix is plenty fast on stock speed.
I overclock, but I wait for thoroughly tested kernels before doing so. Right now I'm with faux's v023r @ 1.3 Ghz. I'll try Clemsyn's after its second or third "redesign" or bugfix.
I stick to optimal battery life kernels rather than performance (faux 123 0.2.3 being the one I'm currently on and most likely will be for the foreseeable future)
Also I can't imagine performance possibly getting any quicker or running programs any faster than they already are on the atrix.
Honestly, I never understood why people oc their phone, especially the Atrix. I mean the phone is already fast being that it is 1Ghz dual core. Plus from what I have seen, the Atrix overheats like crazy with the stock frequency so why would you want to increase that even more, so it explodes? I use my phone to mostly play 3D games and I have never encountered any lag or low fps whenever I play games.
Atrix_Owner said:
Honestly, I never understood why people oc their phone, especially the Atrix. I mean the phone is already fast being that it is 1Ghz dual core. Plus from what I have seen, the Atrix overheats like crazy with the stock frequency so why would you want to increase that even more, so it explodes? I use my phone to mostly play 3D games and I have never encountered any lag or low fps whenever I play games.
Click to expand...
Click to collapse
Quote for truth
The Atrix is plenty fast already. I can understand if you OC a HTC Magic, or a Hero; but there's no real need to do so on the Atrix.
Idk I see a difference on any launcher when I flip through pages and through apps. 1.3 or 1.45. But I def notice the difference in snappyness.
Sent from my MB860 using xda premium
95% of the time I overclock I do it for getting awesome benchmark scores that I can admire. 5% of the time I do it when playing 3D games like Fruit Ninja, It seems a lot smoother to me. But I hardly ever do it because it sucks the battery down so fast, so usually I'm at 1ghz. Also it's just kind of cool to see the the potential the phone has when overclocking.
i used faux's kernel to overclock to 1.3 for a few months but i didnt really see any difference except when i run quadrant or how my phone got hotter than stock when under load. another thing that annoyed me with faux's kernel was constantly losing widgets on reboot. i use two batteries so i reboot pretty often.
I used faux 23r 1.4GHz with setCPU profiles.
Profiles clamped speed to 1ghz at cpu temp of 50degc and 800mhz at 60degc.
Most noticeable difference was in k9 mail, indexing and searching were slightly improved.
I ran it so I would get a short boost if the cpu was cold.
Matthew
Sent from my MB860 using XDA App
Hey
On my old and feeble Hero I had to OC, if I wanted it to run fine, however I never felt the need to OC my Atrix. it has so much juice in it without OC, making it useless to squeeze the battery for the extra 0.2-0.5 GHz. Moreover, since we have no real ICS, our CPU runs freely and waste energy for nothing, so OC it will just make it run ever faster for nothing (In Hebrew there is a saying- running full throttle on neutral ).
I used to run Faux123 1.0Ghz kernel just to UV the device, but since I flashed weekly 6 I use the stock kernel, and it runs great, no overheating, and extremely stable (What cannot be said on UV kernels...)
The only time i oc is when using webtop, that extra speed makes a difference. The rest of the its running at 1ghz and seems plenty
Sent from my MB860 using xda premium
I would love to know how many people have hardware bricked their xplay through extreme Overclocking. You will hear many warnings about bricking your phone through OCing on the forums but I don't know of one person who has actually done it. I always feel a little uncomfortable when I OC my devicedue to the fear of hardware failure.
Ive been running mine overclocked to 1.5Ghz for about 24hrs now with no issue
Between 1.2 and 1.5 are the safe operating parameters for the Xperia Play. It differs from handset to handset though. Yours might be unstable at a lower overclock than mine for example.
Best thing to do if you plan on OCing is to try it in increments to find the limit for your Play. If it starts acting unstable at say, 1.5Ghz, then set it to the setting below that (1.4)
1,6 is save for me at 2,0 GhZ it stocked and i have to restart my phone^^
OC
It's like PC CPU overclocking. When you give it too high frequency, it may reboot. Here is potential hazard. If the phone don't turn off, it can burn your phone CPU. But there also (like on PC) many things, that may prevent crash.
You can always use the app Stability Test from Android Market to see which OC speed is best for your phone.
https://play.google.com/store/apps/details?id=com.into.stability&hl=en
1.9ghz with all governors and I/O settings work for me.
Once I select 2.0ghz the phone shuts off. I never changed voltage values. Perhaps a bump in voltage would get me to 2.0ghz?
I'm not so keen on taking such a risk anyway.
I do think not all Xperia Plays are created equally and consider myself lucky to reach 1.9ghz. The only time I overclock it that high is when I'm using N64oid or GTA3 to prevent occasional lag.
I think 1.6ghz is the sweetspot for most phones.
1.6 ghz smartass v2 all day everyday!
Sent from my R800a using XDA App
It's interesting that not a single person has replied saying it has actually caused hardware failure, just instability and a reboot
thatsupnow said:
1.6 ghz smartass v2 all day everyday!
Sent from my R800a using XDA App
Click to expand...
Click to collapse
Same here
Sent from my R800i using XDA
same here to runs sweet as a nut
mulllen666 said:
It's interesting that not a single person has replied saying it has actually caused hardware failure, just instability and a reboot
Click to expand...
Click to collapse
Must be some kind of safety shutoff built in
Sent from my Xperia Play using xda premium
CTU_Loscombe said:
Must be some kind of safety shutoff built in
Click to expand...
Click to collapse
One time that I overclocked mine at 1.9 GHz and let it run a stress test it froze after a while and didn't reboot until I removed the battery, but it didn't get damaged even though it got pretty hot. Weird...
Sent from my R800i using XDA
I've burnt out a CPU in my laptop before, so I don't and won't over clock.
Sent from my Xperia Play using Tapatalk 2
KeiranFTW said:
I've burnt out a CPU in my laptop before, so I don't and won't over clock.
Click to expand...
Click to collapse
I find it funny that you make kernels that allow overclocking but don't overclock your phone
Sent from my R800i using XDA
leots said:
I find it funny that you make kernels that allow overclocking but don't overclock your phone
Sent from my R800i using XDA
Click to expand...
Click to collapse
Not really?
That's like saying its funny how people go to war but don't shoot themselves
No, I put OC in the kernels as I understand people use over locking. However, I don't offer any higher that 1.6GHz as higher than that dramatically reduces the lifespan of the device.
Sent from my Xperia Play using Tapatalk 2
leots said:
Same here
Sent from my R800i using XDA
Click to expand...
Click to collapse
I have cooked a few graphics cards in my time so never push my play more than 1.6 ghz I dont want this badboy to break in any way
I have to use 1.6 using doomkernal with smartass. If I go any higher then that, Dolphin Mini won't load properly :/
So who has run their phone at 1.4ghz or above for say a year or more?
My PC has been running an OC of about 30% for about 2 years. I know it will shorten the lifespan of my hardware, but who will keep a PC for 10 years anyway. It will be a dinosaur by then.
If I get 2 years from my phone that is enough
I don't see the point of overclocking all the time... for battery saving if nothing else...(?) Maybe the preinstalled R800i UK stock ROM is better and less bloated than what some people get, but 1GHz with the Snapdragon is fine for general use... web browsing, Shadowgun, Asphalt 6, FIFA, Riptide ... all ran well when I wasn't even rooted. Those games are sold for our phones anyway...
But 1.7GHz is definitely over the limit for me as well. Freeze / reboot after a few minutes.
Since Im using DoomKernel my phone is allways overclocked and i have no problems
For daily usage im using MAX 1,3 / MIN 1,0 and GOUV: Smartassv2 or Powersave.
Only for Quadrant tests sometimes i really set it to 1,8 GHZ
So I've got some time at the moment to work on the vibrant again, so I figured I'd ask you guys a question.
What are you guys wanting out of the vibrant?
I'm not really one to go for the latest and greatest buzz word feature like "Linaro build" or "optimized build prop," etc.
lengthy posts are encouraged, tell me what you still want out of this device. What do you use it for? What do you want to use it for? Etc.
Like I said, not looking for "gimme 500MB ram" or " an updated 2.3 kernel", I wanna know what user experience your looking for.
Sent from my Galaxy Nexus using Tapatalk 2
No takers?
Sent from my Galaxy Nexus using Tapatalk 2
Now we have almost faultless ROMs and kernels, the only issue is GPS.
+1 on GPS
lorendroll said:
Now we have almost faultless ROMs and kernels, the only issue is GPS.
Click to expand...
Click to collapse
Point if the question was missed, it's not about faults. Also there are very talented individuals working on the GPS issues. I cannot test GPS as mine no longer works. I want to know not just for me but also the talented Devs working on the vibrant, what ideas do you guys have for improving the Android experience, just in this case I happen to be gearing it toward the vibrant as I won't be working in anything else myself. That doesn't mean it's faulty, there is always room for improvement.
Anyway...not monitoring this thread anymore....Idgaf anymore and people not gonna answer :3
Sent from my Galaxy Nexus using Tapatalk 2
ECOTOX,
Just in case you do monitor this thread Ill give you a request. Ive built a couple of Froyo ROMs now, and plan to stick with Froyo for some time (at least until the EU error fixed)
That said I usually package the Bali 18.8.UV kernel with them. My favorite Froyo kernel is the DMZ kernel.
http://rootzwiki.com/topic/633-kernel2213ghzdragonmodz-nightly3smartassscary8262011140pm/
What set your work apart is the fact it could stepclimp in 100mhz increments. My phone pukes at anything over 1100mhz. Its has the smartass governor (the one I want) that works perfectly. It is smooth, quick, and almost perfect for my needs. Ive only packaged it with one of my ROMs due to the lack to stepclimbing. Here is a request:
Ive tried up to 3 different overclock / volting programs. Tried to set it manually via init script, but the kernel has 2 stock settings: 500mhz / 1000mhz. If I I overclock to 1100mhz I only get three settings: 500/1000/1100. Is there any way you could get a 200mhz in there?
That said your git is available. I don't know how but I guess I could try and build my own based off your source / patches. You kinda sounded like you wanted to help/work some on the T959. With the EU error we have more folks coming back to Froyo every day. Froyo is not dead if I have anything to say about it -
Thanks for your time (I if read this)
+1 on GPS
Sent from my SGH-T959 using xda premium
GPS is primarily due to inadequate or faulty hardware design. We have pushed the limits of trying to fix it with software guys.
I personally would love more battery life. I truly cannot get more than 45 minutes of screen time in ICS.
Sent from my SGH-T959 using XDA
How about intergrating more RAM?
Sent from my SGH-T959 using xda premium
Moped_Ryder said:
ECOTOX,
Just in case you do monitor this thread Ill give you a request. Ive built a couple of Froyo ROMs now, and plan to stick with Froyo for some time (at least until the EU error fixed)
That said I usually package the Bali 18.8.UV kernel with them. My favorite Froyo kernel is the DMZ kernel.
http://rootzwiki.com/topic/633-kernel2213ghzdragonmodz-nightly3smartassscary8262011140pm/
What set your work apart is the fact it could stepclimp in 100mhz increments. My phone pukes at anything over 1100mhz. Its has the smartass governor (the one I want) that works perfectly. It is smooth, quick, and almost perfect for my needs. Ive only packaged it with one of my ROMs due to the lack to stepclimbing. Here is a request:
Ive tried up to 3 different overclock / volting programs. Tried to set it manually via init script, but the kernel has 2 stock settings: 500mhz / 1000mhz. If I I overclock to 1100mhz I only get three settings: 500/1000/1100. Is there any way you could get a 200mhz in there?
That said your git is available. I don't know how but I guess I could try and build my own based off your source / patches. You kinda sounded like you wanted to help/work some on the T959. With the EU error we have more folks coming back to Froyo every day. Froyo is not dead if I have anything to say about it -
Thanks for your time (I if read this)
Click to expand...
Click to collapse
Lol happened to be browsing the forum for info and saw you posted here.
I'll make you a kernel, but I'm not 100%sure I'm sticking with the 100mhz steps for my own release but I'll make you one specifically. I might, but I want to get voltage control working with 100mhz steps, I also gotta work on keeping the gpu clocks more stable.
Sent from my Galaxy Nexus using Tapatalk 2
I would be in your debt sir. Thanks for your time.
I just wanted to say thanks for the great work on DMZ, ECOTOX. It has surpassed Overstock as my kernel of choice, but I had one quick question/request. Is it an issue with the kernel or with a particular ROM for some functions to get a little quirky when you start to overclock into the 1.2Ghz range? Whenever I set the CPU ceiling to 1.2Ghz the long press functions on the haptic buttons of the Vibrant would become flakey. I read that's fairly common with overclocking, but was curious who the culprit might be.
Not knowing anything about how scalers/governers can be implemented, what would the chances be to get something like Smartass v2 or a few more options on a new Froyo kernel? I liked messing around with them when I was running Sub-Zero on ICZen to find that happy medium of battery life vs performance.
I say a Galaxy S III themed gingerbread ROM. Anyone?
I recently flashed the newest Trinity Kernel on my Nexus 7. I still have the stock ROM. I tried to tweak the CPU settings with ROM Toolbox and the most I can overclock is 1400mhz. Why can't I overclock to 1600? Is it because of the stock ROM? I'm looking into Glazed Jelly Bean as a custom ROM but I'm not sure I want or need to use a custom ROM at this point.
Any suggestions?
Because he dropped the Max. You probably flashed A111 correct? That's a TSVZ meaning it is slightly over clocked and undervolted kernel meant for battery not for performance.
Sent from my Nexus 7 using Xparent White Tapatalk 2
U2Bono269 said:
I recently flashed the newest Trinity Kernel on my Nexus 7. I still have the stock ROM. I tried to tweak the CPU settings with ROM Toolbox and the most I can overclock is 1400mhz. Why can't I overclock to 1600? Is it because of the stock ROM? I'm looking into Glazed Jelly Bean as a custom ROM but I'm not sure I want or need to use a custom ROM at this point.
Any suggestions?
Click to expand...
Click to collapse
try a96, its one of my faves. it has a max of 1700mhz http://goo.gl/mLUCZ
Mildly on topic question ... do you notice any imporvments with overclocking? My first experience with overclocking as on my Hero, and then Galaxy S1, but this N7 just feels so fast i cant see overclocking making it any smoother? lol
thanks
myke66 said:
Mildly on topic question ... do you notice any imporvments with overclocking? My first experience with overclocking as on my Hero, and then Galaxy S1, but this N7 just feels so fast i cant see overclocking making it any smoother? lol
thanks
Click to expand...
Click to collapse
yes. its noticeable, but not like on the older devices.
simms22 said:
yes. its noticeable, but not like on the older devices.
Click to expand...
Click to collapse
Nice, ill have to look into rooting sometime soon.
Ok, I got the a96 and I've flashed it...
Is there a detailed changelog for each version? The a111 said it was a 1600mhz kernel so I don't understand why it was dropped down to 1400. That's where my confusion was.
I did notice some increase in speed at 1400. I was having some stuttering issues with Dead Trigger and Minecraft PE, and they were less with the 1400. I've got it running at 1600 now but I don't know what it will do to the battery or how well it will perform. I'll find out later. I've run through the battery pretty quickly today, but I was tinkering with it A LOT so it's not accurate.
What kind of tweaks could I do using Rom Toolbox that would help me maximize my battery while overclocking to 1.6?
Dont over clock.. i dont even see a need to. I use the ondemand gov which stutters a little but using interactive clears that up. Also using the CFQ IO as it is the stock IO used. Its stock so its gotta be good . Also you should turn F-Sync off that helps quite a bit. Also you could toggle auto hotplug and make it only run two cores while gaming and then turn it back on when finished so that way it will hotplug cores as it sees necessary. You could also up the voltages a little bit, some CPU's dont like the lower voltage and that will cause stuttering and glitching just up them by 25mV and see if it clears if not try another 25mV.
I will try those things, but I really want to play with overclocking and learn what happens. This is my first Android device so I'm experimenting and playing around.
But I have one more question...I've overclocked to 1.5...I found 1.6 to be the same as 1.5. But it seems that after an hour or so, it resets to 1.3. in ROMToolbox. Why is this?
Don't use rom toolbox. Use the Trinity app. It sticks just fine for me. Besides you support the dev to make better kernels.
Sent From My Toro+ via White Tapatalk
simms22 said:
try a96, its one of my faves. it has a max of 1700mhz http://goo.gl/mLUCZ
Click to expand...
Click to collapse
i **** my pants a little when it says "system succesfully corrupted, please freak out now"
MRsf27 said:
i **** my pants a little when it says "system succesfully corrupted, please freak out now"
Click to expand...
Click to collapse
Lol its a joke... its the updater-script you can make it say anything... :laugh:
MRsf27 said:
i **** my pants a little when it says "system succesfully corrupted, please freak out now"
Click to expand...
Click to collapse
ha!
youre not the first
Overclocking past 1.4 Ghz doesn't result in any major usability improvements. I've gone up to 1.7 Ghz and the only thing it does is make my tablet really warm and unstable. All you really need for improving system performance is I/O tweaks to speed up app and page loading, and a little bit of GPU overclocking to help with the transitional effects.
and, to be honest, depending which trinity kernel im using, im using either 1100 or 1150mhz mostly. on a111 im using 1100mhz and on a96 i used 1150mhz. with those speeds everything is still fast but a bit better on battery
Overclocking
If you want a little more information about the the overclocking if you havent already you might want to check out http://forum.xda-developers.com/showthread.php?t=1788759 its the official thread of the trinity kernel for grouper.