Database Users

Can only overclock to 1.3 GHZ anymore it freezes

any suggestions...... ive been seeing people get 1.5 GHZ sooo i kinda feel bad lol. And b4 anyone says anything i know 1.3 GHZ isnt bad lol

Not every phone can overclock the same. I personally wouldn't keep the phone over 1.2 ghz. Other than fooling around there isn't much reason to clock it higher.
Sent from my T-Mobile G2 using XDA App

Check out the android development section. There is a VERY lengthy thread about this stuff.

Every phone is diff I can't overclock more than 1.3 also
Sent from my T-Mobile G2 using XDA App

Yep just like everyone says.....it's all built differently. I personally would keep mines at 1Ghz or 1.1Ghz. It's fast enough at 800MHz. Maybe occasionally just to make myself feel good, I'd run 1.2Ghz. Just imagine what 800MHz or 1GHz will be like when a optimized custom ROM can be installed....Stupid FAST!!

1.46 Ghz here since the OC was discovered..
No problem yet, battery life almost never changed, and I'm loving it.

As others have said, it varies. Not every processor will overclock the same, which is why these are sold at a slower speed than possible.
My friend and I bought the same PC processors at the same time. Mine overclocks to 3.6ghz, and I could only get 3.2ghz with his. Nothing is perfectly identical

Common CPU Problems w/ OC

Is it just me but w/ the release of the 1.6GHz and other kernels, people with the OC sensitive CPU in the Vibrant kinda stand out as the losers in the Vibrant community because we cant experience the same increase in performance like everyone else can. Like the Cool kids and the nerds. when i got this phone i was excited to see OC for this phone coming from a MyTouch watching Nexus one users jiz everywhere because of CM love from a million different CM6 roms and OC kernels past 1.0Ghz but when i get a 1GHz phone, i cant even experience it...SMDH .... to me, it takes the fun out of having my vibrant rooted. I kno i aint by myself on this?

Right there with you, bro

you know...honestly people...you should buy a phone for what it is stock
if you can't live with the stock phone you bought without modding it, or you're going to have severe depression issues if yours can't be pushed to the max as far as other Vibrants...you seriously need a life for the latter, pick a new phone for the former.

i bought this phone because of its potential

hydrogenman said:
you know...honestly people...you should buy a phone for what it is stock
if you can't live with the stock phone you bought without modding it, or you're going to have severe depression issues if yours can't be pushed to the max as far as other Vibrants...you seriously need a life for the latter, pick a new phone for the former.
Click to expand...
Click to collapse
LOL
anyway.... I see you got bionix installed.
Try fusion, Viral has tried the 1.6gthingamajigger using the Fusion ROM.
see if that works!

ive installed ASOP-like 1.4 w/ jac kernel...I like this.. jus gonna chill w/ this until someone comes to our rescue w/ a stable OC kernel even i can use.

boimarc89 said:
i bought this phone because of its potential
Click to expand...
Click to collapse
Realize that it is clocked to a stock 1 Ghz because during testing the chip yields had a certain number of chips fail at speeds over that, but do not fail at 1 Ghz. That's why they are clocked at 1 Ghz. Some will work and some won't. Same for desktop CPUs and GPUs. If they never failed at 1.2 Ghz, the processor would be clocked to 1.2 Ghz. Same for 1.4 or 1.6 Ghz.

boimarc89 said:
i bought this phone because of its potential
Click to expand...
Click to collapse
What potential is that? To over clock? That is luck of the draw... If you don't like your luck and must get a chip that overclock well, sell yours and get another. But no guarantee that that one will overclock either.
That'd like buying a lotto ticket to pay your mortgage...
Sent from my SGS Vibrant.

Making my Evo any faster?

So I've been messing around with different roms and kernels for the past few weeks and finally settled on CM6 6.1.1, and the snap 7.6 bfs kernel, for stability and speed. I turned on the turbo mode with snap, OC'd to 1152mhz (freezes at 1192), killed all apps, and ran quadrant.
[Picture of a 2330 benchmark screencap was supposed to go here, but I don't have eight post haha]
I know thats pretty good, my scores average from 2100-2350, but I'm looking to make it even quicker. What can I do?
Thanks!

Move to gingerbread.
Sent from my PC36100 using Tapatalk

sultan.of.swing said:
Move to gingerbread.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Which ROM and which kernel?
weehooherod said:
Don't use Snap 7.6 on CM6.1.1, just use the stock kernel. The new kernel built in with CM6.1.1 is much better, Snap 7.6 is pretty old.
Click to expand...
Click to collapse
I had 6.1.2 flashed, but snap wouldn't work on it and I was only benching around 1400 with the stock kernel.. Even with an OC

xsaqzw said:
Which ROM and which kernel?
I had 6.1.2 flashed, but snap wouldn't work on it and I was only benching around 1400 with the stock kernel.. Even with an OC
Click to expand...
Click to collapse
Benchmark scores don't matter. I don't even check them anymore. Wether I get a 1400 or 2200 its still gonna dial a number at the same speed. Im not playing call of duty on my phone or anything. I want efficiency.

A benchmark does not actually show how fast your phone is....
Cyanogen himself stated this.

quadrant scores =/= to your phone being 'fast'.
But if you care about synthetic benchmarks then you could trick your file system into giving you quadrant scores in the 3000+ range.
by the way thanks for posting this in the relevant subsection of the evo forum dedicated to development this will absolutely further the development of android.

Yeah man, don't worry about benches. If you want to brag about how high it is just PhotoShop it. It's all about smoothness and real world performance/battery life for me. Just find what setup works best on your phone
Edit: and this goes in the q and a section

Lol okay then guys, so which gingerbread ROM and which kernel for the best efficiency and speed?

david279 said:
Benchmark scores don't matter. I don't even check them anymore. Wether I get a 1400 or 2200 its still gonna dial a number at the same speed. Im not playing call of duty on my phone or anything. I want efficiency.
Click to expand...
Click to collapse
I couldn't agree more, how instant can a phone get? Theres a point where speed wont be relevant anymore and its pretty damn close to it already. In my eyes efficiency is the future, doing more with less is something im looking forward to.
Sent from my Warm TwoPointTwo RLS5 Beta'd out Evo

lexusmike said:
Yeah man, don't worry about benches. If you want to brag about how high it is just PhotoShop it. It's all about smoothness and real world performance/battery life for me. Just find what setup works best on your phone
Edit: and this goes in the q and a section
Click to expand...
Click to collapse
**** man I'm sorry I'm new to this forum.
Mods: Please move to the correct section.

Thread moved to General.

Also keep in mind that the EVO's Snapdragon CPU was never a problem, it's still competitive even with the newer CPUs (with the exception of the upcoming A9's both single and especially dual core). Most of the "hacks" that raise the Quandrant score over 2000 are just that, hacks. They manipulate the other tests (non-CPU specific ones) to raise the score and make you think that you've just achieved some kind of new level of performance when in fact you'll see pretty much no difference.
Over clocking will help a little but like I said the problem isn't the CPU; a lot of the lag you may see on the EVO is because of the GPU. Nobody has figured out out how to overclock the GPU so over clocking the CPU will make no difference with the GPU. There have been some improvements in the drivers and if you're running CM or MIUI, you already have them. Gingerbread slightly improves some of the core graphics in Android so you'll see a boost over pre-Gingerbread Android but I think what we should all be waiting on is for the new Adreno 200 GPU drivers that Google will release when the OTA 2.3 update for the N1 drops. It wont magically make our EVO's into Nexus S' or anything but I wouldn't be surprised to see a noticeable boost in performance.

Oddly enough, I'd rather have the transition animations that come with some of the custom ROMs, even if they take longer. They provide a much more "fluid" experience. I don't like the jarring, speed-driven, animation-free transitions that come with stock ROMs, because they lack polish. As soon as I saw videos of those animations, I was in love. LOL. Seriously though, lag and lack of animations (which consequently actually help hide lag and load times) are the two things I see holding back the polish of Android. Just as an example (not trying start a flame war here, people), look at the animation when going from portrait to landscape in iOS. Then look at Android's lack thereof. THAT is what Android needs-to actually FEEL faster, not necessarily BE faster. So try something like that if you want the phone to feel more fluid instead of just achieving raw benchmark speed. Again, just my opinion (kind of sad that I feel the need to put that disclaimer in every post lately).

Award Tour said:
Also keep in mind that the EVO's Snapdragon CPU was never a problem, it's still competitive even with the newer CPUs (with the exception of the upcoming A9's both single and especially dual core). Most of the "hacks" that raise the Quandrant score over 2000 are just that, hacks. They manipulate the other tests (non-CPU specific ones) to raise the score and make you think that you've just achieved some kind of new level of performance when in fact you'll see pretty much no difference.
Over clocking will help a little but like I said the problem isn't the CPU; a lot of the lag you may see on the EVO is because of the GPU. Nobody has figured out out how to overclock the GPU so over clocking the CPU will make no difference with the GPU. There have been some improvements in the drivers and if you're running CM or MIUI, you already have them. Gingerbread slightly improves some of the core graphics in Android so you'll see a boost over pre-Gingerbread Android but I think what we should all be waiting on is for the new Adreno 200 GPU drivers that Google will release when the OTA 2.3 update for the N1 drops. It wont magically make our EVO's into Nexus S' or anything but I wouldn't be surprised to see a noticeable boost in performance.
Click to expand...
Click to collapse
that is interesting.. thanks for the info.
I hope it does open some more performance and maybe a way to overclock the GPU

Im not playing call of duty on my phone or anything. I want efficiency.[/QUOTE said:
Lmao
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse

Why do YOU Overclock (or refuse to) on the Atrix?

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

User feedback

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?