Related
So now that I have Froyo, how do I overclock it?
I'm rooted with stock build (FRF50).
There have been a few tutorials out there but I'm not sure what is applicable now and whether they will still work.
If they do still work, can someone pls recommend a good one that will work for sure with Froyo?
Thanks lots in advance!
Hi there,
I've been running FroYo overclocked for a few days now and am absolutely loving it.
I'm running the leaked build that Paul uploaded, and running the pre-rooted kernel from Cyanogen. Other than that, I manage the CPU's speed with SetCPU, running at a max of 1113MHz.
The kernel can be found at http://forum.xda-developers.com/showthread.php?t=686627
codesplice said:
Hi there,
I've been running FroYo overclocked for a few days now and am absolutely loving it.
I'm running the leaked build that Paul uploaded, and running the pre-rooted kernel from Cyanogen. Other than that, I manage the CPU's speed with SetCPU, running at a max of 1113MHz.
The kernel can be found at http://forum.xda-developers.com/showthread.php?t=686627
Click to expand...
Click to collapse
what he said...
Umm...
OT
...Android kernels don't get "rooted". Root on these phones simply means having the "su" app with suid set, and superuser.apk around to manage thos permissions. If you can put those two files in place with a stock kernel, and properly set the permissions, you have root.
endOT
That said, there appear to be two "packaged" solutions to OC your FroYo:
Cyanogen's update.zip (not only does it put in an overclockable kernel, it also roots your phone).
Pershoot's newly-posted kernel (this is what I'm running...)
Of course, if you are brave, you can always "roll your own". People are clearly doing this, as there are FroYo Nexus One's out there showing 1.2ghz speeds.
big_adventure said:
Umm...
OT
...Android kernels don't get "rooted". Root on these phones simply means having the "su" app with suid set, and superuser.apk around to manage thos permissions. If you can put those two files in place with a stock kernel, and properly set the permissions, you have root.
Click to expand...
Click to collapse
You also need ro.secure=0 in the default.prop file (of the ramdisk portion of boot.img). So you could say the kernel gets 'rooted' this way (correct me if I'm wrong).
(On the Motorola Milestone this is not possible even though you can add "su" and "Superuser.apk", although on the Droid you can)
has anyone really gotten a real world speed increase with the OC'ed cpu? Yes it can technically run faster, but do our phones ever really max out the cpu when we are using them? Personally I feel that the ram adds more to the speed of the phone than the cpu. But that just an opinion. I'll have to see about doing some testing to see what the active cpu levels are under use.
followinginsanity said:
has anyone really gotten a real world speed increase with the OC'ed cpu? Yes it can technically run faster, but do our phones ever really max out the cpu when we are using them? Personally I feel that the ram adds more to the speed of the phone than the cpu. But that just an opinion. I'll have to see about doing some testing to see what the active cpu levels are under use.
Click to expand...
Click to collapse
You can see improvements with benchmarks, but as far as noticing a difference... no, not really. There's always the placebo effect of "wow, this is so much faster with a ~10% overclock", but I don't think it's really a difference that you can pick up on. There are a lot of other things that could account for a 10-15% performance difference at any given time.
Granted, I could tell more of a difference on 2.1 than I can on 2.2 Froyo's JIT capability improves the efficiency to the point that you really can't tell a difference at all. Under 2.1, I at least felt like the menus were just a little snappier. Everything is snappy under Froyo though.
Clear as mud, lol?
side by side with a stock clocked n1 was the only way i could see a differance.
but its not a drastic differance, like a stock droid vs 800 mhz droid
just finished the "HOW TO:Root, Install Clockwork, Remove Bloatware, Integrate Google, Un-root, and more" tutorial and was wondering what i should set the min max to in setcpu
also why am i always using like 70% of my ram.
why does launcherpro always have to be running when obviously touchwiz never had to do that
fupamobile said:
just finished the "HOW TO:Root, Install Clockwork, Remove Bloatware, Integrate Google, Un-root, and more" tutorial and was wondering what i should set the min max to in setcpu
also why am i always using like 70% of my ram.
why does launcherpro always have to be running when obviously touchwiz never had to do that
Click to expand...
Click to collapse
Your phone doesn't manage memory like Windows. It *should* be using most of your RAM. LauncherPro needs to be running because it IS always running. If it's not running, you kind of won't have a dock.
To be fair, Windows uses as much ram as it can as well, for the same reasons.
Its been that way since Vista.
fupamobile said:
just finished the "HOW TO:Root, Install Clockwork, Remove Bloatware, Integrate Google, Un-root, and more" tutorial and was wondering what i should set the min max to in setcpu
also why am i always using like 70% of my ram.
why does launcherpro always have to be running when obviously touchwiz never had to do that
Click to expand...
Click to collapse
If LauncherPro was killed by the system every time you go into an app, it would have to redraw when you go back to it. Redraws are slow and laggy. It's a good thing that it is running all the time. The RAM thing is a good question. I'm not sure. I know that using a ROM that was deodexed and zipaligned really decreased the amount of RAM being used at boot and I had a lot more free overall.
For SetCPU, use Min 200 Max 1000(or whatever your kernel's max is) and Conservative scaling. No profiles.
GoogleAndroid said:
If LauncherPro was killed by the system every time you go into an app, it would have to redraw when you go back to it. Redraws are slow and laggy. It's a good thing that it is running all the time. The RAM thing is a good question. I'm not sure. I know that using a ROM that was deodexed and zipaligned really decreased the amount of RAM being used at boot and I had a lot more free overall.
For SetCPU, use Min 200 Max 1000(or whatever your kernel's max is) and Conservative scaling. No profiles.
Click to expand...
Click to collapse
how do i know what my kernals max is. im a total newb and just went through that whole tutorial. they never tell you what to set the cpu at.
fupamobile said:
how do i know what my kernals max is. im a total newb and just went through that whole tutorial. they never tell you what to set the cpu at.
Click to expand...
Click to collapse
It's 1000.
Hello there XDA I just switched to the Aria from the Captivate. I am new to Android modding, so please bear with me.
I like the phone, It doesnt bother me losing screen space. However it is a bit slow with the 600 MHZ processor.
So if there are some people kind enough to guide me to/through the following it would be appreciated.
1. I would like to overclock it a bit, maybe to 800.
2. General performance tweaks
3. Get rid of Att bloatware
4. Root ( z4root is not in the market anymore and ATT disables side loading.)
Sent from my HTC Liberty using XDA App
Everything u need is in the android Dev. Section for the aria its really simple. To find and to follow..I use cm6 rc2. It overclocks very nicely
Sent from my Liberty using XDA App
Hey Joshua, being new to the Aria as well (less than a month), I haven't looked into overclocking it... but I am running CM 6.1 RC 2, what do I need to do to start overclocking?
Install SetCPU to overclock. I wouldn't go over 825mhz as it starts getting unstable.
As for rooting, search for posts by user asiancuta. He did a really good write up that included a key point I didn't see anywhere else. It's titled NOOBZ: easy guide to rooting your aria.... Read all instructions, and make sure you understand it first.
To install cyanogenmod 6.1 rc2 do a search for That aria - she's so racy!
Sent from my Liberty using XDA App
Mike's Aria said:
Install SetCPU to overclock. I wouldn't go over 825mhz as it starts getting unstable.
Click to expand...
Click to collapse
In the other overclocking thread (or overcloking as the OP spelled it ) several people posted that they were running at 864... what type of instability is likely? Also, doesn't overclocking HAVE to have some sort of adverse effect? Like reduced reliability or an increased likelihood of hardware failure? If there are no adverse effects, why would HTC not set the CPU higher from the factory?
I want to try it, but I feel like I pushed the limits of my comfort zone just by rooting and installing CM...
911jason said:
In the other overclocking thread (or overcloking as the OP spelled it ) several people posted that they were running at 864... what type of instability is likely? Also, doesn't overclocking HAVE to have some sort of adverse effect? Like reduced reliability or an increased likelihood of hardware failure? If there are no adverse effects, why would HTC not set the CPU higher from the factory?
I want to try it, but I feel like I pushed the limits of my comfort zone just by rooting and installing CM...
Click to expand...
Click to collapse
I always lean on the side of caution when it comes to overclocking a phone. I don't want to fry the processor since I can't replace it as easily as one on a computer.
Processors are never set from the factory to run at their fastest.
Sent from my Liberty using XDA App
While it might seem odd since all these phones have the same hardware they don't all respond the same to overclocking. Some people can do 864. I can't even get my phone to do anything over 825 and even 825 gives me issues. I like to keep mine between 768-787. Over doing it can cause damage and shorten the life of the processor but keeping it around 800 is probably safe as long as you moniter temps. Heat is the real enemy here. Manufacturers are trying to balance cost, reliability, battery life. Our little phone use a smaller battery and so a lower clock speed keeps the phone running longer. And the aria is a mid range phone, they don't want it to be faster than the more expensive phones. Also Higher clock speeds will drain your battery faster. At 768 the phone is noticeably snappier and the battery drain over stock isn't even noticeable.
Huh. That's good to know, Callmearia. However I don't even know where to start on any of this. I've never 'flashed' a phone or anything like that before.
Sent from my HTC Liberty using XDA App
This is a really good guide explaining how to root your phone and install a custom recovery, Clockwork, with which you can flash ROMs, make backups, and a bunch of other stuff:
http://forum.xda-developers.com/showthread.php?t=788737
You will still not be able to sideload apps just by rooting though. You will need to flash a ROM in order to do that. Check out the Android Development section, it is all there.
L551 said:
Huh. That's good to know, Callmearia. However I don't even know where to start on any of this. I've never 'flashed' a phone or anything like that before.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
I think most people can hit 864 now using CM6.1 RC2. I think some tweaks were made to allow it. Before I was only hitting 825mhz or 844mhz when I ran in to stability problems... but now I have none. Or, it could be due to the fact it's colder here now.
Alright, so after some adb troubles with Ubuntu 10.10, I am now rooted, woo!
So now, where to go from here?
This worked flawlessly and easy. Less than 5 minutes
http://forum.xda-developers.com/showpost.php?p=7449486&postcount=1
EDIT : I see that you already got rooted.
You have two choices for Attn1's custom ROMS
Liberated or Cyanogenmod
http://forum.xda-developers.com/showthread.php?t=819715
http://forum.xda-developers.com/showthread.php?t=821642
Take in mind that CM has more customizable features, INCLUDING OVERCLOCKING. Liberated doesn't.
Place the .zip on your SD card. Enter clockworkmod recovery by holding down the volume down button after restarting phone. Wipe Data, Cache, Dalvik Cache. Go to install zip from Sdcard. Pick the file. It should install. wait, and reboot and continue.
Customize it to your liking. Download apps/widgets
Turn off unnecessary background items. (Auto Sync)
Decrease Brightness
Only use GSM networks
(these are battery saving tips....lots more)
http://forum.xda-developers.com/showthread.php?t=505419
That is the SetCPU for XDA members.
To install, go through ADB in the command line, or download FASTAPP Install from the Market and place the .apk on your sd card and install it from there.
kaschenberg said:
I think most people can hit 864 now using CM6.1 RC2. I think some tweaks were made to allow it. Before I was only hitting 825mhz or 844mhz when I ran in to stability problems... but now I have none. Or, it could be due to the fact it's colder here now.
Click to expand...
Click to collapse
That's probably true. I haven't tried going over 825 since way back with dumfuqs kernel.
Alrighty... did all that, now running cyanogenmod on my Aria! \o/
No more ATT bloatware.
I made sure to do a nandroid backup just in case.
Also overclocked to 768MHz. Phone seems a bit quicker.
Thanks guys
Any other tips?
Oh also adb stopped working again on Ubuntu >.< Anyone know how to fix that?
Sent from my Liberty using XDA App
L551 said:
Alrighty... did all that, now running cyanogenmod on my Aria! \o/
No more ATT bloatware.
I made sure to do a nandroid backup just in case.
Also overclocked to 768MHz. Phone seems a bit quicker.
Thanks guys
Any other tips?
Oh also adb stopped working again on Ubuntu >.< Anyone know how to fix that?
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Make sure you install the google apps package.
Also, Not too sure.
I use windows. Works perfectly on there. try that
Yup I made sure to install that. Need my market.
I'll see if it works on windows later.
Sent from my Liberty using XDA App
L551 said:
Alrighty... did all that, now running cyanogenmod on my Aria! \o/
No more ATT bloatware.
I made sure to do a nandroid backup just in case.
Also overclocked to 768MHz. Phone seems a bit quicker.
Thanks guys
Any other tips?
Oh also adb stopped working again on Ubuntu >.< Anyone know how to fix that?
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Try leaving the OC alone after the reflash.. It's defaulted to 864mhz and it works flawlessly for me.
It was default 600MHz for me.
EDIT: Holding down 1 to access voicemail no longer works, as there is no voicemail number in the options. What is it?
Sent from my Liberty using XDA App
L551 said:
It was default 600MHz for me.
EDIT: Holding down 1 to access voicemail no longer works, as there is no voicemail number in the options. What is it?
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Its different for every one. My VM is a local number. You can always just use your phone number.
I recently set my VM to go thru my Google Voice number now.
Sent from my Liberty using XDA App
Using my own number worked.
However, now my phone is freezing randomly, and causing the launcher to hang. (ADW and LauncherPro both do this)
It seems android.process.acore always takes alot of CPU time when it does this.
One of my buddies at work has a rooted Droid X, and I couldn't believe how laggy it is, even compared to the stock JFD Vibrant.
I am not here to pick up the fights with "my phone is better than yours" type of replies, I am just looking for any pointers how to help my buddy because my Vibrant with Nerov3+voodoo (2.2 ROM with /system, /data, /dbdata and /cache converted to EXT4) runs circles around his DX.
I am not sure if it is an app or something that cause this (he does not have much installed), but even looking at the youtube vids of DX his phone feels like it's limping on a half a leg.
So far I know he is running the latest OTA and his phone is rooted, I checked his /system, /data etc are EXT3 - I assume the stock DX has a proper FS unlike my Vibrant when it was stock.
It's probably the blur elements. A custom ROM fixes that quite quickly.
blockhead42 said:
It's probably the blur elements. A custom ROM fixes that quite quickly.
Click to expand...
Click to collapse
Thank you! I will suggest him to join xda and flash a custom ROM.
Sent from my Nero powered Vibrant
Blur shouldn't make it lag that much. Some of his settings might be slowing him down. If he is trying to be real conservative on his battery and set it to "conservative" - it is going to throttle back his CPU usage to try and maintain better battery life.
Need to check a few things like that.
what kind of scores do you get in quadrant on your phone (if you aren't boosting them with the stagefright etc)?
thepolishguy said:
Blur shouldn't make it lag that much. Some of his settings might be slowing him down. If he is trying to be real conservative on his battery and set it to "conservative" - it is going to throttle back his CPU usage to try and maintain better battery life.
Need to check a few things like that.
what kind of scores do you get in quadrant on your phone (if you aren't boosting them with the stagefright etc)?
Click to expand...
Click to collapse
I will see him after the New Year's and will check.
I am not sure what Quadrant scores he is getting, but the phone obviously not performing to its full potential. I get around 1500 Quadrant with EXT4 converted filesystem, it is under a 1000 stock. The boost in score is def the filesystem read/write + a small bump due to JIT on 2.2.
Once rooted try to get setcpu and leave it at 800Mhz permanently. That fixed my issues with lag. Of course a new Rom wouldn't hurt since Stock Verizon/Blur Rom sucks balls.
Sent from my DROIDX using XDA App
A few things I do to speed up the x are; turn off push for e-mail, freeze the stock applications I do not use via titanium backup, and use fast reboot when it slows down anyway. I still have some lag issues but these help. I'm ready for the incredible Hd so I can drop the x, this Motorola device just has never met the mark for me plus I miss sense.
Sent from my DROIDX using XDA App
sandman2025 said:
I'm ready for the incredible Hd so I can drop the x.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
That's my plan too... I wish Motorola gave a similar option like on the original nexus one bootloader...
Sent from my DROIDX using XDA App
Is there an OC app for liberty or anything that I can install that's like the overclock things u can download and install through fission rom manager? So that there preset and all u do is install it
You can use my DOOverclock tool. It isn't an app, but it works.
http://www.kimete.com/dooverclock.html
My personal favorite is Droid Overclock from the market.
It costs $1.50 but is worth every penny. Gives you more than just overclocking options. Just my 2 cents.
miketoasty said:
My personal favorite is Droid Overclock from the market.
It costs $1.50 but is worth every penny. Gives you more than just overclocking options. Just my 2 cents.
Click to expand...
Click to collapse
Agreed. Well worth the money. The best app I ever paid for.
I also use Droid overclock very nice app. Well worth the money. Donating to very worthy people
Sent from my Liberty D2
The only thing about setcpu is that you still have to load a custom kernel module to overclock. Without the kernel module, you can only scale up to 1ghz. Droid Overclock edits the module for you with presets up to 1.45ghz which is very convenient and user friendly.
I'm pretty sure Liberty 1.0 has overclock script in it. If you go into terminal emulator and type:
Code:
su
overclock.sh
it should pop up and you can change slot levels higher than 1GHz.
But now that Liberty 1.5 has the native overclock it shouldn't be a problem.
I use Droid 2 Overclock AND Quickclock.
I use Quickclock to calibrate then import into D2O. Basically Quickclock automatically calibrates YOUR phone and gives you safe over and under clock ranges. Then save the profiles....export....then import into D2O.
My D2 is clocked at 1.305GHz