Develop Bugs

[Q] Percentage of well overclockable Desires?

Hi guys!
I haven't yet rooted my Desire(I would have but I was fool enough to install the 2.2 OTA).The main reason for me to root would be the ability to overclock my device.All this time that I have been around here on the Desire and Nexus One forums I have been seeing that our devices are overclocked only up to 1113MHz and only in very rare cases 1267MHz.However,to my great surprise,I noticed on OpenDesire ROM's thread that the Desire can be overclocked @1344MHz(which of course made me think a big HELL YEAH!).Is that number ok for all of us or for some select few?I remember from my Hero days that only some few,lucky guys like myself could overclock up to 768MHz,although there were cases of people,rare,yet not unheard of,that could overclock @844MHz.Is this the case here or are things different with the Snapdragon?
Many many thanks guys!

C'mon guys,no one?

tolis626 said:
I have been seeing that our devices are overclocked only up to 1113MHz and only in very rare cases 1267MHz.
Click to expand...
Click to collapse
I don't think overclocking to 1267MHz happens in rare cases. I had no problems oc-ing to 1267 and it seems that a lot of forum member were able to do this too.
Why don't you downgrade your HBoot to 0.80, root your phone and try it out?
Just make sure your phone does not become too hot if you try 1344MHz.

I have to ask the question, but does it really matter?
IMHO, the Desire is plenty fast enough that overclocking it simply isn't necessary.
I can understand underclocking to eek out more battery life, but other than gaining a few points on some benchmarks, I really don't see the point in overclocking.
Regards,
Dave

foxmeister said:
I have to ask the question, but does it really matter?
IMHO, the Desire is plenty fast enough that overclocking it simply isn't necessary.
I can understand underclocking to eek out more battery life, but other than gaining a few points on some benchmarks, I really don't see the point in overclocking.
Regards,
Dave
Click to expand...
Click to collapse
so this, its really not needed at all. a decent fast rom and 1ghz is more than enought for things to be super speedy. any decent kernal will provide more than enough speed.
overclocking(and lots of other things these days!) reminds me of that bit in jurassic park where they are all sat around the table and geoff goldblum says:
"Yeah, but your scientists were so preoccupied with whether or not they could, they didn't stop to think if they should".
herein lies the lesson, just because you can do it doesnt mean you should do it.

Well,I have my reasons wanting to overclock...First off,I will check if I can see any difference in speed or smoothness.If there isn't,I will just revert the clock back to normal after some benchmarks.
I just am the kind of guy that wants to get the most out of his phone!

I think ALL Desires can overclock to 1267Mhz. It's not that rare and I've not seen anyone having a problem with it.
It does make things a bit snappier as well.

sbdags said:
I think ALL Desires can overclock to 1267Mhz. It's not that rare and I've not seen anyone having a problem with it.
It does make things a bit snappier as well.
Click to expand...
Click to collapse
That's what I'm talkin' about man!
And now that I think of it,it's not that much.I mean,the Hero could overclock @768,which is 45% overclocking.The Desire's 1267 is about 27% and 1344 is about 34,5%.Nothing too much!So why not?

Every CPU is different. The Qualcomm Snapdragon is a very different beast compared to the Qualcomm MSM 7200A.
We are just starting to learn what we can do with the Snapdragon without damaging it.

Kinma said:
Every CPU is different. The Qualcomm Snapdragon is a very different beast compared to the Qualcomm MSM 7200A.
We are just starting to learn what we can do with the Snapdragon without damaging it.
Click to expand...
Click to collapse
Well my man,in this case the MSM7200A is no beast but rather a pooch that barks to no avail!Good pet however!
Joking aside,the Snapdragon is a beast for a mobile phone,but even beasts get beaten.Now,if I can somehow reach or even get close to the performance of the Galaxy S or the Droid X I'll be happy.Software wise I believe that HTC is far superior ,but it's hardware is a little out of date.Let's see what their new devices will do for us!
Btw,does anyone know if the so anticipated HTC Ace will be anything better than what we already have or if it will be the Evo for GSM users?
Thanks!

The desire is plenty fast as it is and I don't see the point of overclocking it. I've had it to 1267 in the past and it made no difference at all for usability. I'm also the type that overclocks all his computers...
Sent from my HTC Desire using Tapatalk

Personal preferences dude...What everyone does with their phone is their own business.I wish I could resist overclocking too!
However,I was watching a thread over at the N1 forums in which a dude named Storm9999(genius dude,not just a random one) stated that an overclock @1,3GHz could fry our phones.Is that so?I mean,I know overclocking reduces the CPU's lifetime,but is it THAT MUCH dangerous?

I think overclocking can kill your phone.. I use to overclock my own o2 orbit and it died after a year..

Friend of mine just burned his old HTC by overclocking it and as a consequence is going to buy a desire.
I had my phone overclocked at 1345Mhz for a moment, just to test it, and it made no real difference to when it was overclocked at around 1.2Ghz, which in turn has very very little difference to stock 1Ghz.
I think the only case where you see some small impact is in games.
I've tested HD recording at 1.345 Ghz and stock speed and there was no difference.
If anything, it's going to kill your battery and shorten its life for sure, going so high. If ever I will OC again I won't go over 1.1 and only if I find some tangible improvements.
As said, this phone is always fast, there is no real need to OC, other than for 'fun'.

The fun is what I want...Well,most probably I will have my phone overclocked at the maximum speed it can get for about a week or two and then go back to 1 or 1,1GHz...
Btw,your signature kicks ass andycted!

GPU overclocking

Hi im running xdandroid on my rhod210 and i am very happy with it, one of the few annoying downsides to it is the ****ty fps of 17.5 which is quite choppy for most 3d games.
But iv heard that gpu overclock for rhodium is definatly possible with the right line added to startup.txt.
look at this thread:http://forum.xda-developers.com/showthread.php?t=697673
it says about overclocking the vogue with a line in startup.txt, with it the vogue achieved 36.5fps!!! which is brilliant, and the vogue is inferior to the tp2 harware wise.
So we know its possible and will give us great improvement, so all we need is someone with the know how to tell us how? it was sais that we would "need to talk to your kernel devs to add this functionality" so hopefully this will be a great update.
any comments, anyone willing to help? anyone working on the xdandroid project willing to implement this? it would be much appreciated.
tank you, please reply :]

Thus far I think we've only overclocked the main CPU, haven't touched the GPU. Looks promising tho.

ohhhhhhhh my god its really ?? i cant belief !! its co0o0o0o0o0o0ol

Jandyman said:
Hi im running xdandroid on my rhod210 and i am very happy with it, one of the few annoying downsides to it is the ****ty fps of 17.5 which is quite choppy for most 3d games.
But iv heard that gpu overclock for rhodium is definatly possible with the right line added to startup.txt.
look at this thread:http://forum.xda-developers.com/showthread.php?t=697673
it says about overclocking the vogue with a line in startup.txt, with it the vogue achieved 36.5fps!!! which is brilliant, and the vogue is inferior to the tp2 harware wise.
So we know its possible and will give us great improvement, so all we need is someone with the know how to tell us how? it was sais that we would "need to talk to your kernel devs to add this functionality" so hopefully this will be a great update.
any comments, anyone willing to help? anyone working on the xdandroid project willing to implement this? it would be much appreciated.
tank you, please reply :]
Click to expand...
Click to collapse
this would be awesome, would definitely raise its quadrant score

I'm not sure what is Vogue and what screen resolution it has, but I supppose as it's old phone with Qvga. Qvga means 1/4 of the pushing pixels that we have on screen. So if Rhodium had qvga screen we would have 4 times beter frame rate. 69 FPS. I wouldn't call 17,5 fps of WVGA 3D ****ty in phone that was presented almost 2 years ago with different operating system. And we should remember that it's Android, which isn't (for now) fully working.

I'm not sure what is Vogue and what screen resolution it has, but I supppose as it's old phone with Qvga. Qvga means 1/4 of the pushing pixels that we have on screen. So if Rhodium had qvga screen we would have 4 times beter frame rate. 69 FPS. I wouldn't call 17,5 fps of WVGA 3D ****ty in phone that was presented almost 2 years ago with different operating system. And we should remember that it's Android, which isn't (for now) fully working.
Click to expand...
Click to collapse
your right the htc vogue has a qvga screen, but it also has less processing power so this should somewhat balence things out. But i still think gpu overclocking would greatly improve the rhodiums performance and if i remember right neoseekers version of android recorded 24.1 fps, and that is without gpu overclock. so improvement is more than possible.

ohhhhhh god 24.1 fbs its brilliant beside 17.5 to the htc rhodium its co0o0o0o0ol

I tried the startup option they were talking about in the thread referenced... if the value is too low then maybe that is the issue, or it just doesn't work. Either way got 17.6fps on neocore before and AFTER changing the startup.txt and rebooting. Unless a dev wants to chime in I don't think that is the only step to overclocking.

Well those startup options are in the kernel. So we'd have to get the kernel enabled before we can ever dream of having the startup option work
Basically any option that's set in cmdline is being passed to the kernel - so if our kernel isn't enabled for that feature/option, it'll just get ignored.

arrgghh beat me to it
i dont kno how hard or easy it is to change the kernal to allow this but hopefully the devs will hear and implement this feature. Or if someone could contact them suggesting it would be great.

its actually simple to over-clock, but does anyone know what values to overclock to before burning up the phone?
If you guys want this done, id look for an existing winmo solution to do this on windows. Once we know what values to use on the clock regs, we can easily port it over on android.

a quick google search of 'overclocking gpu on htc touch pro 2' has lead me to nothing :/ im presuming this is because there is no need to overclock the gpu when running windows mobile because there are very few decent windows mobile games (as far as i kno) and havnt found any using 3d, specially not free.
But if we find the detailed specs of the touch pro 2, and then search for the safe frequesncy to overclock that power of gpu too wouldnt it be the same? thats probly our best bet unless someone can find evidence of overclocking gpu on a tp2 running windows mobile.

Jandyman said:
a quick google search of 'overclocking gpu on htc touch pro 2' has lead me to nothing :/ im presuming this is because there is no need to overclock the gpu when running windows mobile because there are very few decent windows mobile games (as far as i kno) and havnt found any using 3d, specially not free.
But if we find the detailed specs of the touch pro 2, and then search for the safe frequesncy to overclock that power of gpu too wouldnt it be the same? thats probly our best bet unless someone can find evidence of overclocking gpu on a tp2 running windows mobile.
Click to expand...
Click to collapse
Nahh.. don't work that way. Its not like 1 clock you can change to any frequency. All the clocks are derived from the plls and you would need to do some math to determine what pll to use and what to devide it by.
There are also other clocks involved with the display. mddi, mdp are other clocks that can also change. Vogue for example has the ability to over clock mddi.
But yea.. a winmo app would be very helpful.

[ACL] said:
Nahh.. don't work that way. Its not like 1 clock you can change to any frequency. All the clocks are derived from the plls and you would need to do some math to determine what pll to use and what to devide it by.
Click to expand...
Click to collapse
For those who are still unawares at this point, PLLs are crystals on the mainboard that resonate at different frequencies. Thus you would need to tear open the phone and figure out which PLLs are linked to the GPU and which are just ancillary, and then be able to put it back together. Whomever wants to take this upon themselves, I wish them luck.

Hamsteriel said:
For those who are still unawares at this point, PLLs are crystals on the mainboard that resonate at different frequencies. Thus you would need to tear open the phone and figure out which PLLs are linked to the GPU and which are just ancillary, and then be able to put it back together. Whomever wants to take this upon themselves, I wish them luck.
Click to expand...
Click to collapse
Not entirely tru. We know which pll the gpu uses and what its currently dived by. We had this discussion today on the irc board. There is some work being done to help improve the speed.

[ACL] said:
Not entirely tru. We know which pll the gpu uses and what its currently dived by. We had this discussion today on the irc board. There is some work being done to help improve the speed.
Click to expand...
Click to collapse
Yay, I can haz FPS?

[ACL] said:
Not entirely tru. We know which pll the gpu uses and what its currently dived by. We had this discussion today on the irc board. There is some work being done to help improve the speed.
Click to expand...
Click to collapse
Just curious if this work on GPU overclocking ever got anywhere or was determined to be possible in the future?

it's possible - but more than likely it would cause severe problems with battery life and stability. Considering the dismal state of our battery life already I doubt the work is worth it for an extra 4fps in angry birds.
Thread necromancy is bad mkay

randomblame said:
it's possible - but more than likely it would cause severe problems with battery life and stability. Considering the dismal state of our battery life already I doubt the work is worth it for an extra 4fps in angry birds.
Thread necromancy is bad mkay
Click to expand...
Click to collapse
If you're up to date on kernels, especially if you're on Wistilt's test branch, battery life is great. When sleeping, battery life is measured in days now. Anyway, just because the compromises involved don't interest you doesn't mean they wouldn't work for someone else.
Alternatively to overclocking the GPU, I wonder what sort of UI smoothness/framerates would be possible if the display driver were recoded to pixel double to our screen from 400x240 (same resolution as a Samsung Intercept).
I played around with the lcd density but that didn't seem to be able to create the same effect, as program's like Neocore still knew that my display was actually 800x480 and displayed as such.

[q] Livewallpapers

Hello!
I-m trying to apply several live wallpapers. Some crash, its acceptable.
Others, plain buggy. Example: Galatic Core.
I select it in the Livewallpapers selector, it does not error, and shows a black screen. i press settings, get the message "buy the app", and then it shows!
If i then select it, i get a black screen... and then the original wallpaper again.
Anyone got more luck than i ?

They were never meant to run on our phones so they will be iffy at best for performance
Also if your using cm6 that's a known issue across the board with them
Sent from my HERO200 using XDA App

thoughtlesskyle said:
They were never meant to run on our phones so they will be iffy at best for performance
Also if your using cm6 that's a known issue across the board with them
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Could you guys please stop doing that ?
"" XPTO was not meant to run on our phone ""
What is it there... that our phones have... or have not... that make a given app not run ? Sure... we can agree on "it wasn't designed for 320x240. Ok, i agree too.
But either than that ?? Yeah, our CPU is the slower MSM on the field, at least compared to Diamonds/Raphaels and upwards... but hey!! We have 1/4 of the pixels to take care of. That sould give us some room...
Now, don't get me wrong. It was not designed to run Android. But that doesn't mean it was not meant to. Take for example a simple little phone, sold here on Portugal as Optimus Boston. It has a MSM cpu... it came with 1.6 running at 600mhz... but the latest update to Eclair 2.1... underclocked it to 480. My kaiser usually runs at 550. (official rom, its possible to have custom roms running at the original 600.) and it still is a great phone... look at the simple specs :
http://www.gsmarena.com/gigabyte_gsmart_g1305_boston-3201.php
Now, someone explain... why can't our Kaiser/Vogue/Polaris run Android like that leatle freak underclocked to 480 runs. Please.

The fact that we have absolutely no RAM doesn't play into it ever since sheer clock speed always determines speed, to be honest I haven't even seen them run well on my hero and I have it OC'd to 691
But hey if you want to argue about it there are links to the source around go in and fix the problem, most of the devs for this project have more important things to focus on at the moment
Sent from my HERO200 using XDA App

thoughtlesskyle said:
The fact that we have absolutely no RAM doesn't play into it ever since sheer clock speed always determines speed, to be honest I haven't even seen them run well on my hero and I have it OC'd to 691
But hey if you want to argue about it there are links to the source around go in and fix the problem, most of the devs for this project have more important things to focus on at the moment
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Do not feel ofended. It was not my intention.
My point is that if we had accepted the slowness of our devices, we would never had attempted to port Android.
As for the RAM, agree.. it is a bottleneck...
Now, has for speed... i've seen them run well... on other devices of course.

I did many tests on my Kais130 Fresh Froyo, about livewallpapers
I agree with Daedric on the ability of our device.
I managed to run the "Grass" Wallpaper properly. Others, like Mario, Galactic Core, ... Sometimes with bugs and/or too many resources used.
It seems to me that LiveWallpapers work less well in the latest Froyo

Well were not the slowest android phone anymore. But that doesnt mean much, we still have a lot of instability. The ram limitation can be overcome with comp cache (virtual memory) but that brings only more instability and adds overhead that we don't need. Also the performance just isnt there yet. Our phones beat only one phone and thats because that phone doesnt have froyo on it. Otherwise it would beat ours out. Also that was with my kaiser overclocked to 572 mhz with a gpu overclock as well. Any other phone msm 7200 phone at those speeds kick our kaisers ass. I think the resource intense ones are just not meant to work well at all for us. My background works at least lol, I use a background that shows the core of a 486 cpu.

aceoyame said:
Well were not the slowest android phone anymore. But that doesnt mean much, we still have a lot of instability. The ram limitation can be overcome with comp cache (virtual memory) but that brings only more instability and adds overhead that we don't need. Also the performance just isnt there yet. Our phones beat only one phone and thats because that phone doesnt have froyo on it. Otherwise it would beat ours out. Also that was with my kaiser overclocked to 572 mhz with a gpu overclock as well. Any other phone msm 7200 phone at those speeds kick our kaisers ass. I think the resource intense ones are just not meant to work well at all for us. My background works at least lol, I use a background that shows the core of a 486 cpu.
Click to expand...
Click to collapse
Should we assume... that at the same speed, diferent MSM devices offer diferent performance ? Or, are we simply doing still things wrong, i don't know, perhaps a poor schedule, buggy drivers which introduce lag, perhaps the graphic one.
We must remember, they kick our kaiser hard, but they have much more pixels, how can that be ?

2.0 Ghz kernel

Hai Guise!
Back a little while ago the G2/Vision thread (before Desire Z was merged) had a thread about overclocking made by a user named Flippy. I followed it for a while because it was getting insanely out of control and awesome. I had used 1.9Ghz as my max oc for a while and It was great. Now I'm on 1.8Ghz again because the 1.9Ghz kernel was removed later on and replaced with the 1.8Ghz update zip. (For some reason doesn't work for me so I had to fastboot it)
So the reason I made this thread is because I would like to have the 2.0Ghz kernel. I know it's possible and has been done already. I've looked into compiling my own but apparently I need linux to compile it and I'm not fond of installing VM's on my old computer that will barely run as it is.
Now I ask of you, if anyone who is kind enough to possibly please compile a 2.0Ghz zimage for me, I would be greatly in your debt and appreciate it much so! I understand that it is my fault if I mess up my device and only I am held responsible.
Thank you in advanced to anyone kind enough to offer their services.

dietotherhythm said:
Hai Guise!
Back a little while ago the G2/Vision thread (before Desire Z was merged) had a thread about overclocking made by a user named Flippy. I followed it for a while because it was getting insanely out of control and awesome. I had used 1.9Ghz as my max oc for a while and It was great. Now I'm on 1.8Ghz again because the 1.9Ghz kernel was removed later on and replaced with the 1.8Ghz update zip. (For some reason doesn't work for me so I had to fastboot it)
So the reason I made this thread is because I would like to have the 2.0Ghz kernel. I know it's possible and has been done already. I've looked into compiling my own but apparently I need linux to compile it and I'm not fond of installing VM's on my old computer that will barely run as it is.
Now I ask of you, if anyone who is kind enough to possibly please compile a 2.0Ghz zimage for me, I would be greatly in your debt and appreciate it much so! I understand that it is my fault if I mess up my device and only I am held responsible.
Thank you in advanced to anyone kind enough to offer their services.
Click to expand...
Click to collapse
Why do you need to overclock that high? I've used the 1.8Ghz and found that to.be overkill. I'm running at about 1ghz at that seems ample.
Sent from my CM7 powered Desire Z

cjward23 said:
Why do you need to overclock that high? I've used the 1.8Ghz and found that to.be overkill. I'm running at about 1ghz at that seems ample.
Sent from my CM7 powered Desire Z
Click to expand...
Click to collapse
+1
Wouldn't that fry your phone without any active cooling system or something? Sounds unnecessarily risky..

dietotherhythm said:
Hai Guise!
Back a little while ago the G2/Vision thread (before Desire Z was merged) had a thread about overclocking made by a user named Flippy. I followed it for a while because it was getting insanely out of control and awesome. I had used 1.9Ghz as my max oc for a while and It was great. Now I'm on 1.8Ghz again because the 1.9Ghz kernel was removed later on and replaced with the 1.8Ghz update zip. (For some reason doesn't work for me so I had to fastboot it)
So the reason I made this thread is because I would like to have the 2.0Ghz kernel. I know it's possible and has been done already. I've looked into compiling my own but apparently I need linux to compile it and I'm not fond of installing VM's on my old computer that will barely run as it is.
Now I ask of you, if anyone who is kind enough to possibly please compile a 2.0Ghz zimage for me, I would be greatly in your debt and appreciate it much so! I understand that it is my fault if I mess up my device and only I am held responsible.
Thank you in advanced to anyone kind enough to offer their services.
Click to expand...
Click to collapse
You don't need a VM. You need to wipe the garbage off and install linux on the "bare metal".

While it would be *neat* to oc this phone to 2GHz - just because. It would be beyond useless and I can just see some noob burning down their parents house or possibly starting a nuclear war with Russia by accident. Lets not forget your carrier reporting you to the CIA for having a nuclear reactor in your phone.
Look, with no active cooling it's just downright stupid to go that high. However being the genius' that we are I'm sure somebody could devise a method to install a mini fan or some liquid cooling on this phone. But then you may need that nuclear reactor to power all that stuff. Haven't we already set a guiness world record at 1.8GHz on a production phone anyway? Maybe we need to tell them so we can make it in the book

My phone froze at 2Ghz... I went in for 2.2Ghz at first but it froze after a couple seconds

MacaronyMax said:
My phone froze at 2Ghz... I went in for 2.2Ghz at first but it froze after a couple seconds
Click to expand...
Click to collapse
LOL, it didn't make you go back in time or some ****?

The 1.9Ghz kernel caused my phone to crash. 2.0 would burn your phone's processor out. Just use the 1.8Ghz kernel and have the profiles on SetCPU set to the lowest speeds when the display's off.

Your phone may not actually run stable at 2GHz. Mine doesn't run stable past 1.6GHz, and that runs psx4droid *perfectly*, especially with the optimization they've done in the app recently.
Also, even with setCPU profiles, battery drain when you ARE running that high is a beeeotch.

Honestly, it's not really for OCing that high, but rather the look at what I can do I had a friend just ask be how high I can OC my phone and at 1.5GHz he's like woah :O His face at 2GHz would have been like

I previously used Flippy's kernel on my G2 and did OC it to 1.8 GHz, and got a Quadrant score of 3037. It was cool to see how fast my phone could actually get, but I'm more than comfortable with OC'ing it to 1.4 GHz. Anything more than that seems to be unnecessary to me, but that's just my opinion. Last thing I want is to have my G2 melt while it's in the pocket of my pants.

Try the .ko module and overclock that way
Sent from my HTC Vision using XDA App

mejorguille said:
Try the .ko module and overclock that way
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Oh yeah totally forgot that existed. Thank you for the useful response.

tried the module but the phone freezes after doing anything above 1.4ghz
I believe it needs voltage tweaking which I don't know how to go about sooo... yeah

MacaronyMax said:
My phone froze at 2Ghz... I went in for 2.2Ghz at first but it froze after a couple seconds
Click to expand...
Click to collapse
LOL!! Froze? Or more like "fried"!! Hehe
Doesn't it happen to you guys that when running @1.5Ghz u get many FC from some games? Running excessive OC might stop your phone from working.
Why do you need 2Ghz?!

EdWRX said:
LOL!! Froze? Or more like "fried"!! Hehe
Doesn't it happen to you guys that when running @1.5Ghz u get many FC from some games? Running excessive OC might stop your phone from working.
Why do you need 2Ghz?!
Click to expand...
Click to collapse
Nope, not for me anyway. I know different HW revisions and such have an effect on how high you can oc but my phone doesn't skip a beat at 1.8GHZ. I'm sure I could go to 2GHZ or a bit higher but unless I'm trying to emulate a PS3, I don't see the purpose - aside from maybe setting a record.

KCRic said:
Nope, not for me anyway. I know different HW revisions and such have an effect on how high you can oc but my phone doesn't skip a beat at 1.8GHZ. I'm sure I could go to 2GHZ or a bit higher but unless I'm trying to emulate a PS3, I don't see the purpose - aside from maybe setting a record.
Click to expand...
Click to collapse
Same. I can do 1.8 all day if I keep near a charger. Anything over 1.3 will drain my battery like a monster though.
I keep at 1.2 regularly and only go higher for games.
Sent from my HTC Vision using XDA App

EdWRX said:
LOL!! Froze? Or more like "fried"!! Hehe
Doesn't it happen to you guys that when running @1.5Ghz u get many FC from some games? Running excessive OC might stop your phone from working.
Why do you need 2Ghz?!
Click to expand...
Click to collapse
I can jog 1.8 and 1.9Ghz for a day without even reaching a dangerous temperature.
Can I get some supportive ideas and less herp derp personal opinions?

Highest Ive pushed mine is 1.5ghz. No need to go any further, Im satisfied with the performance. I get a full days battery life and the temperatures never get critical (my setcpu profile is set to underclock at 38.2 degrees Celcius but my G2 hasn't gotten close to that). Im curious at what stage my G2 would score 3000+ in Quadrant.

You might PM flippy and see if he will customize a kernel for you that goes that high. Let him know you will send a certified letter signed in blood and a video of you stating you release him of all liability for what ever town you destroy when your phone goes nuclear.
Seriously though, I'm willing to be he'll make it for kicks if you ask nicely - btw, call guiness so you can make it into the record books. Also, I'm not sure but if you flash a 'blank' kernel couldn't you just echo the speed and voltage in the 00banner file or whichever one it is?

[Q] Highest stable overclock on Touch Pro 2?

Anyone care to tell me what the highest stable overclock they have achieved on the Rhodium/Touch Pro 2 with Android?

reocej said:
Anyone care to tell me what the highest stable overclock they have achieved on the Rhodium/Touch Pro 2 with Android?
Click to expand...
Click to collapse
Depends on the device. Most seem to max out at 748,800khz, one guy claimed he hit 820mhz or smth outrageous.
Honestly the best way to establish what your device can handle is to push the OC in WinMo until it's not stable any longer. That should be a good indicator of how far you can push Android.
Honestly I found OCing Android to be way more trouble than it's worth - the phone seemed to lag even more, and it definitely made the device less stable. I'm not a big fan of overclocking my computer either, so I am a little biased.

Cool. Thanks arrrghh. I reprogrammed a USSC TP2 to use with PagePlus for my daughter and put Android on it for her. Just wanted to try and push it to its limits I guess and see what it would do. What class/size/brand card do you suggest I use? Right now it is using a Sandisk class 6 8 gig card, but I've heard some have gotten better performance from class 2 cards.

I'd start at around 600mhz and keep pushing it up 20mhz at a time. The clock driver only takes it in steps of 19.2mhz, but is smart enough to divide it correctly via mod. At 640 or so the bottom started to get noticeably warm, and I've set it at 660 right now.
Each device is different, some take overclocks easily than others.
-- Starfox

Thanks for the help guys, I'll keep tinkering with it.

I've a RHOD100 and have acpuclock.oc_freq_khz=692000 on FRX07 and all is well and does not seem to even get any way warm underneath.
Mind you, while I've set this, is there any way to check within Android as to what speed my TP2 thinks it's actually running at (in case it is ignoring the setting in the setup file) ?
However, it is possible that the speed may work differently with differing builds of the various components but maybe someone more knowledgable on here could confirm whether or not this is the case.
C

Hi,
i use the tool "CPU Master Free" to see the actually clock speed (i hope it shows the right values).
At this time its oc at 633,6 Mhz an no problems.
sebastian

Perfect - it says I'm running at 691.2Mhz
C

reocej said:
Anyone care to tell me what the highest stable overclock they have achieved on the Rhodium/Touch Pro 2 with Android?
Click to expand...
Click to collapse
Got my Tilt2 (most recent kernel + rootfs) maxed out at 768.000MHz, and I noticed smoother scrolling and window animations.
But for me, I noticed that the phone actually freezes at times.. even when the phone wasn't overclocked. I believe that's just bugs in the kernel, though, soo not much to do about that from my experience, OC performance relies heavily on the device and kernel version (if that wasn't obvious lol).
EDIT: Ehh, I've read that anywhere from 600-640MHz is the most stable. Currently I'm at 595.2MHz and am noticing an improvement in stability over 768MHz.. Hope this helps.