Related
Is it possible for me to install the VillianROM on my HTC Droid Eris or am I going to brick my phone?
are you rooted?
not heard of the villianrom. is it a eris rom? if it is not and not ported, prob just give you an endless boot....its pretty hard to brick your phone once you have the recovery image.
droidkevlar said:
not heard of the villianrom. is it a eris rom? if it is not and not ported, prob just give you an endless boot....its pretty hard to brick your phone once you have the recovery image.
Click to expand...
Click to collapse
I'm pretty sure its a g2/hero Rom.
droidkevlar said:
not heard of the villianrom. is it a eris rom? if it is not and not ported, prob just give you an endless boot....its pretty hard to brick your phone once you have the recovery image.
Click to expand...
Click to collapse
Evil Eris = Ported Villian Rom ;P
1. I am rooted and running:
- Eris_Official 0.81T2
- Senseless patch
- Nexus One patch
- Nexus Launcher w/LWPs
It's nice, but more laggy than I'd like. Is Evil Eris really the ported VillianRom?
After downloading SetCPU, I've been able to set my processor at a higher normal frequency and am experiencing better performance.
Turnyface said:
After downloading SetCPU, I've been able to set my processor at a higher normal frequency and am experiencing better performance.
Click to expand...
Click to collapse
what settings are you using?
droidfreak said:
what settings are you using?
Click to expand...
Click to collapse
I'm utilizing different profiles.
Normal:
Max = 528 mhz
Min = 245 mhz
Sleep/Standby
Max = 245 mhz
Min = 160 mhz
Battery temp > 50 C
Max = 160 mhz
Min = 160 mhz
Someone told me to do this because we actually can't overclock yet:
...fire up a adb shell and do a cat /proc/cpuinfo while it's over clocked were just curious to see if the program is in fact over clocking the cpu
Click to expand...
Click to collapse
when I did that, it came up with 526 which is not overclocking... funny thing was when I used a different profile to slow it down, it still said 526...
The highest frequency the Eris can attain at this time is 528 mhz. We're not overclocking, just simply setting the running frequency to a constant number. I don't think you're going to see a difference between 528 and 526. 2 mhz is such a minute amount.
right it is minute, but my point was that 528 is what the eris can do... but maybe youre right that set cpu keeps it at a constant... set it lower and run what I said and it probably still will say the 528... thats what I did not understand and never got an answer... it did not seem as though setcpu had throttled it back at all... I saved the app though waiting til we can get over 528..
Turnyface said:
1. I am rooted and running:
- Eris_Official 0.81T2
- Senseless patch
- Nexus One patch
- Nexus Launcher w/LWPs
It's nice, but more laggy than I'd like. Is Evil Eris really the ported VillianRom?
Click to expand...
Click to collapse
I'm runnning that exact same config, and I haven't noticed any lag.
It has been getting better as the night has gone on. The one issues I'm consistently having is the Nexus One Launcher force closes from time to time, making my phone useless and forcing me to pull the battery and start again. Maybe I'm doing something wrong?
Framework43 said:
Evil Eris = Ported Villian Rom ;P
Click to expand...
Click to collapse
really?
they dont act the same.
i have a friend who has the Villian Rom and well u kno i ran the Evil Eris and it was seemingly 2 totally different devices. even tho u say its the same thing?
does this app work on Streak?
I tried out and nope, it don´t work how it should. It says the Streak is running with 998 Mhz and you can´t overclock it. Waiting for update...
crazy cat said:
I tried out and nope, it don´t work how it should. It says the Streak is running with 998 Mhz and you can´t overclock it. Waiting for update...
Click to expand...
Click to collapse
998Mhz is the limit for the kernel. you need a kernel that can be overclocked for that option....
it works fine. at this moment in time you can not overclock but it auto detects settings just fine and you can set screen off speed/battery low speed to extend your battery life.
crazy cat said:
I tried out and nope, it don´t work how it should. It says the Streak is running with 998 Mhz and you can´t overclock it. Waiting for update...
Click to expand...
Click to collapse
Wait, u know there are three levels of clocking, right? one is under clock, one is clocked and one is over clock. There are two frequencies when u turn on the setcpu, one is max and one is min...but i would like to know if u r able to make the max and min both up to 998mhz so that it can run at full speed at all times
zgmf-x322a said:
Wait, u know there are three levels of clocking, right? one is under clock, one is clocked and one is over clock. There are two frequencies when u turn on the setcpu, one is max and one is min...but i would like to know if u r able to make the max and min both up to 998mhz so that it can run at full speed at all times
Click to expand...
Click to collapse
yes you can bro. both max & min are customizable from 24500Mhz upto 99800Mhz. however, ive found that having the streak running totally max when the screen on will simply drain your battery, there are no real speed improvements to be seen. a good compromise to combat lag would to be to set screen on: 76800 - 99800Mhz.
i completely downscale mine when the screen is off and although the battery life on the streak is good, doing this makes it even better. no lag when switching screen on either (frequency change)
Works great for me too! I don't see any need for overclocking a phone (unless you don't use it as a phone..)
I unplugged mine from the charger about 1.5 hours ago, still 100% battery..
thanks guys for the reply, appreciated it alot!
it does and very well
to get interactive setting you must at least have performance fix and it will let you overclock and add interacting setting i just did perf. fix and setcpu settings and now quadrant score of 1700+
Works great for me. Flash smokku and fard's djsteve kernal perfmod using clockwork or streak mod and then you can overclock using setcpu. Look at my signature line below.
Dell Streak, 2.2 froyo (318), custom kernel, OC to 1.2ghz, quadrant 2002, hspda signal mod,
hi, i have jit on my stock generic world 2.1 firmware. After jit enabiling my build.prop on 32 vm heapsize, i changed after reading some in an motorola milestone forum , it to 36 vm heapsize with rootexplorer. I can not explain why, but i have the feeling that most of my apps go smother when i launch they. I think my phone is smother. Im newbie, but i have the feeling after change it, try the xda app, for example,find it is faster loading.
sry for bad english, and please make a backup before change it
Do you get more points in Linpack and Quadrant now?
Tried, and all it does is brick your phone
When you restart it ofc! Haha
I didn't brick my X10. Mine is smoother now.
In Quadrant I get almost on every run more than 750 points now and in Linpack almost on every run more than 17.35 points. New record for me in Linpack are 17.52 points.
I'm still trying to get more than 777 points in Quadrant...
Flo95 said:
I didn't brick my X10. Mine is smoother now.
In Quadrant I get almost on every run more than 750 points now and in Linpack almost on every run more than 17.35 points. New record for me in Linpack are 17.52 points.
I'm still trying to get more than 777 points in Quadrant...
Click to expand...
Click to collapse
The more cache heapsize, the faster big apps (like huge games) are running. But small and medium size apps run slower.
The less cache heapsize is, the faster small apps run, but this can be cause of FC of huge apps.
for example, with 12 MB heapsize, small apps will fly on your phone instanly, but medium-size and huge apps will crash everytime.
If u are not playing games and use huge apps, u can set cache heapsize to 24 MB, else the 32 MB is good solution for all in my opinion
Flo95 said:
I didn't brick my X10. Mine is smoother now.
In Quadrant I get almost on every run more than 750 points now and in Linpack almost on every run more than 17.35 points. New record for me in Linpack are 17.52 points.
I'm still trying to get more than 777 points in Quadrant...
Click to expand...
Click to collapse
Hm how did that work?
I'm on 2.1 JIT enabled, global FW... I'm restoring it to the J+Z W 2.1 anyways haha!
I might try it again though, if I can be bothered, I'll post results I'll do it more carefully next time
changed to 36m on mine now. SE-Shipped-Lite ROM
hmmmm...seems smoother
Well, guys... same here) Changed to 36, and have everything smoother. Even if everybody recommends changing between 12-32 only, 36 fits perfect our x10s.
hi, thanks for feedback
i have played with my phone these day, and have no problems
linpack now 17.186 before believe at 16, but not over 17
when somebody have problems, you can go back to 32 or 24 vm heapsize
Alakasam said:
Hm how did that work?
I'm on 2.1 JIT enabled, global FW... I'm restoring it to the J+Z W 2.1 anyways haha!
I might try it again though, if I can be bothered, I'll post results I'll do it more carefully next time
Click to expand...
Click to collapse
I changed 32 to 36 with Root Explorer, saved it and rebooted my device. That's it.
Sent from my X10
Placebo effect.
I made that change and did not notice anything different or more smother, Linpack and Quadrant give lower values
Flo95 said:
I changed 32 to 36 with Root Explorer, saved it and rebooted my device. That's it.
Sent from my X10
Click to expand...
Click to collapse
I think I missed out the 36(m <--) bit XD silly me T_T
Will changing it make running 3D gameloft game smoother? Is the build file under /system folder
tiggerbcn said:
Placebo effect.
I made that change and did not notice anything different or more smother, Linpack and Quadrant give lower values
Click to expand...
Click to collapse
Right. Little apps are slower than before.
I changed it back to 32.
Has someone found a value, that makes the X10 faster? With better benchmarks etc
has anyone tested 18 or 24?
hi you can test it and report it
think it's just a feeling, maybe a bit of fine-cut not for the dramatic performance gains
Flo95 said:
Right. Little apps are slower than before.
I changed it back to 32.
Has someone found a value, that makes the X10 faster? With better benchmarks etc
Click to expand...
Click to collapse
It does say that a smaller vm will make smaller apps faster and larger apps slower. I tend to use news readers and browsers rather than games and the like, so I would if I could be bothered, take it down to 24
Edit: just changed it to 24 and it does feel faster. I was able to use it sooner after boot and my custom animations were lovely and smooth. Thanks for the tip op
Sent from my X10i using XDA App
If you are not a gamer and are an average user with the average apps, then 24 is good. I changed down to 24.
IMO the default value 24 is the best fit for our X10i. Never have a problem and can't feel any different when changing it to 32. Even when I'm in 32, I have to relaunch several apps twice before it works correctly.
So I think I'll stick with 24. ^^
The original heap size of the X10 are 24?
And JIT changes it to 32?
I think 32 is better, because the benchmarks are much better.
Title says a helluva lot ;-)
READ THIS WHOLE POST AND THE WHOLE POST AFTER IT!
Features:
All steps undervolted about 25%. Should be stable still
The table is currently 300, 600, 950mhz until I can make it scale more than 3 steps.
The voltage for 950Mhz is less than at stock for 800Mhz, so you should see better battery life even though we're overclocked.
Display flicker fixed (or at least toned down, it can't be completely eliminated with the LED backlighting)
Scheduler tweaks backported from later kernel versions
Some governor tweaks of my own for responsiveness
To install this, just flash the zip in ClockworkMod. This shouldn't harm your device, but I make no promises. I trust it enough to run it on my device, if that means anything to y'all. I also attached a zip to flash back to the stock kernel (..but why would you break my heart by doing so..? ;P).
Next Up:
I REALLY want to get 1Ghz+ working, and my code is sound (I'm sure of that) but it won't boot on my device. I think I just need to find the right voltage, or I could have a bad die for OC'ing. This is the first thing I will work on.
Maybe the interactive CPU governor
Look into the 2-point touch limitation
Source:
Source is available on my GitHub at https://github.com/geniusdog254/Quickie
I will not flat out ask for donations, however I do appreciate them. So if you're feeling generous or appreciate my work then it would help me out a lot if you could donate. I have my game Reflex-A-Tron on the Market for $1 if you'd like to donate like that, or there is a link under my name on the left side to donate, and one in my signature. The one on the left and in my signature is to donate via PayPal. Any amount is appreciated, but please don't feel obligated.
You can contact me here via PM, on Twitter @geniusdog254, or email me at [email protected]. Email or Twitter is the preferred method, because I really despise the XDA PM system.
Disclaimer:
If this breaks your Nook, kills your family/pets, or starts global thermonuclear war, do not blame me. You have been warned. If you break your device and blame me, I will point at you and laugh.
Changelog:
1-11-11 - Screamer:
Overclock to 950Mhz. Still chokes at 1Ghz, which tells me it's probably my device. 950 is stable.
Temp sensor drivers. Thanks to the Nookie FroYo guys!
Updated to 2.6.29.6.
Scheduling tweaks from 2.6.31.
Code idle time from 2.6.34.
Scaling fixed. Now scales properly between all 3 CPU levels. Adding more than 3 makes it choke for some reason. I'll look into it.
Test version set at 1Ghz added. Just because it doesn't work for me doesn't mean it won't work for you. Don't get your hopes up though, I've tried making it work every way from Sunday
Notes:
Screen WILL be unresponsive immediately after a boot. Just lock the device for several seconds, unlock it, and all will be fine until another reboot. I blame B&N, it happens with all custom kernels.
Yes, I know there are more versions of this kernel than there are Windows Vista. The middle one is the recommended one. If your Nook can't run at 950Mhz (crashing often, or just won't boot) try the one with the 900mhz tag. If you wanna try and push it higher, try the 1Ghz one. Be warned: very little success is reported with the 1Ghz kernel. The top level of these chips seems to be right around ~925-975Mhz. Very few devices will be able to hit 1Ghz.
You should probably wipe your cache partition after flashing this. You won't lose anything, and many people are reporting that it makes things more stable at the higher freqs for them.
MD5 Sums:
stock-1.0.1-kernel.zip — 78ccf8ab0cd35b988cc9a81bd8bbc310
quickie-1ghz-test.zip — 7076a88cae2229910478e698c0e19435
quickie-screamer.zip — 22e8c2cc21e42cca1d18377a92b49540
quickie-900mhz.zip — 40362515da86cb4baea37b0bc6358feb
Wow thanks so much for this. Gotta try it out!
wow very nice! going to have to give this a shot!
Awesome! But is it compatible with nookie froyo (2.2) or the stock BN (2.1)?
Update: It boots Nookie Froyo but powers off immediately after booting. I am looking forward to the release of the 2.6.32 version of your work. Keep up the good work!
Sent from Nook Color (Nookie Froyo microSd optional)
runhopskipjump said:
Awesome! But is it compatible with nookie froyo (2.2) or the stock BN (2.1)?
Sent from Nook Color (Nookie Froyo on emmc)
Click to expand...
Click to collapse
Just stock 2.1.
With the Nookie FroYo, it wouldn't flash the kernel to the SD for boot, plus (at least on th Epic) a 2.6.29 kernel won't boot on FroYo, it needs 2.6.32 or higher
Glad to have you part of the nook color family. You did awesome work on the Epic4G.
Looking forward to more great stuff from you.
Thanks
Sent from my LogicPD Zoom2 using Tapatalk
Loss of touch sensitivity
I loaded up the new kernel via Clockwork and all went smoothly with the install. I noticed immediately that my touch sensitivity has decreased. I now have to press and hold just about as long as you would press and hold to bring up a context menu or something. If I don't do that, my touch is ignored and not registered.
Interestingly enough, when I type an email on the keyboard, it recognizes my typing very quickly. No apparent loss of sensitivity when I'm using the keyboard. I wonder why and how that is???
I guess I need to recalibrate the screen again to regain sensitivity.
I did notice that Castle Crashers frame-rate has improved a good bit with the overclock. It's a noticeable and welcome difference.
Angry birds was a bit annoying to play with the loss of screen sensitivity.
Edit: I alleviated the loss of touch sensitivity by installing the LCDDensity app from the Android Marketplace and selecting a density of 200.
Tried to install via clockwork and I keep getting errors unable to install. an I missing something?
sent from my nookcolor using the xda app
Got it working with clockwork update... thanks!
Flashed. Am loving it, seems much snappier, and the keyboard response at 900mhzz is much improved. Keep up the good work!
NC overcklock
Hi,
Last month I made some tests with overcloking /undervolting. I was able to push the NC at 1.15GHz, with a little voltage tweaking. 1Ghz was achieved without voltage tuning. The smartreflex technology adjusts automaticaly the OPP voltages to minimize the power consumption. Maybe the L3 speed can be increased to 200 Mhz by setting DPLL at 400MHz (in u-boot).
Occip (working for 2.6.32 NC kernel)
deitiphobia said:
I loaded up the new kernel via Clockwork and all went smoothly with the install. I noticed immediately that my touch sensitivity has decreased. I now have to press and hold just about as long as you would press and hold to bring up a context menu or something. If I don't do that, my touch is ignored and not registered.
Interestingly enough, when I type an email on the keyboard, it recognizes my typing very quickly. No apparent loss of sensitivity when I'm using the keyboard. I wonder why and how that is???
I guess I need to recalibrate the screen again to regain sensitivity.
I did notice that Castle Crashers frame-rate has improved a good bit with the overclock. It's a noticeable and welcome difference.
Angry birds was a bit annoying to play with the loss of screen sensitivity.
Edit: I alleviated the loss of touch sensitivity by installing the LCDDensity app from the Android Marketplace and selecting a density of 200.
Click to expand...
Click to collapse
me too, seems touch for a while(XXms) take effect, less then that screen acts like nothing touch it. this drived me mad when using Gellery, switch pictures give terrible feeling.
i think this relay to the clock scaling, i will check this out using SetCPU.
thanks for your work!
Amazing work with the kernal. I flashed and changed density to 200 in Root Explorer /system/build.prop and it works great.
Also in Spare parts I change both animations to Fast instead of defaults.
occip said:
Hi,
Last month I made some tests with overcloking /undervolting. I was able to push the NC at 1.15GHz, with a little voltage tweaking. 1Ghz was achieved without voltage tuning. The smartreflex technology adjusts automaticaly the OPP voltages to minimize the power consumption. Maybe the L3 speed can be increased to 200 Mhz by setting DPLL at 400MHz (in u-boot).
Occip (working for 2.6.32 NC kernel)
Click to expand...
Click to collapse
Can you add me in GTalk? [email protected]
I have some stuff I'd like to ask about. How did you do the OC? Did you change the actual clock in u-boot so everything scales up? Or did you add more VDD_OPP* steps. I used some of the code I saw before for the Droid's 3430 chipset, using the OPP steps. The stock kernel has steps built in for up to 1.2Ghz, but if I enable them I can't make it boot, at least on my device.
I can't figure out the voltages either, probably because I fail at hex. If I understood that, it would help me a lot.
sugwacee said:
me too, seems touch for a while(XXms) take effect, less then that screen acts like nothing touch it. this drived me mad when using Gellery, switch pictures give terrible feeling.
i think this relay to the clock scaling, i will check this out using SetCPU.
thanks for your work!
Click to expand...
Click to collapse
Hrrm. It sounds like the CPU scaling is staying low, because I see absolutely no change in the touch sensitivity, and I didn't touch any of the code related to it. Try setting the CPU Governor to OnDemand or Performance in SetCPU if it isn't set there already.
Geniusdog254 said:
Can you add me in GTalk? [email protected]
I have some stuff I'd like to ask about. How did you do the OC? Did you change the actual clock in u-boot so everything scales up? Or did you add more VDD_OPP* steps. I used some of the code I saw before for the Droid's 3430 chipset, using the OPP steps. The stock kernel has steps built in for up to 1.2Ghz, but if I enable them I can't make it boot, at least on my device.
I can't figure out the voltages either, probably because I fail at hex. If I understood that, it would help me a lot.
Click to expand...
Click to collapse
diff is available http://nookdevs.com/NookColor:_Nookie_Froyo_Tips#Overclock_.5B100.25_untested_on_this_system.5D
occip said:
diff is available http://nookdevs.com/NookColor:_Nookie_Froyo_Tips#Overclock_.5B100.25_untested_on_this_system.5D
Click to expand...
Click to collapse
Odd. That's exactly what I've done (with a couple diff voltages) but it won't boot on my Nook. I guess I just got a bad die. Can you explain the voltage values? I know how to increase/decrease the hex number, but how does it correlate to the actual voltage? Like how is 0x38 = 1.35V in a stock kernel?
Definitely going to try this out. Thanks for the work. I'll report back with comments/questions/concerns.
nrune said:
Tried to install via clockwork and I keep getting errors unable to install. an I missing something?
sent from my nookcolor using the xda app
Click to expand...
Click to collapse
+1 I am getting the same. It installs half way then stops with a big exclamation mark, asks me to shut down and restart. I would love to try this. Any ideas?
EDIT: OK got it. CWM updated to 3005 and now it can go into recovery was on 3002 which did not.
This is very much appreciated.
Be expecting some monies so you can buy some candy in the near future.
keep up the good work.
Thanks!
First I am aware that overclocking is not "safe" and all that kind of stuff
However for some reason I am unable to OC my SGS2 and run the phone on a steady way.
I have tried several ROMs (stock and custom) with different kernels and OCing apps with no avail.
I am not even able to run at 1.4Ghz or 1.6Ghz without having my phone reboot or hard lock on me.
Is there a particular or recommended setting (most successful combination) that anyone out there can suggest me trying?
Sometimes it will hang under heavy gaming but sometimes even browsing app and regular stuff will cause the phone to reboot or lock. If I work with no OCing at all then everything is fine and dandy.
Thanks, you can see my current configuration @ my signature.
Sounds like a very temperamental cpu. Currently I have the same setup you do and have never had issue with 1400mhz or 1600mhz. Though I usually leave mine at 1200mhz. What app are you running when it hangs?
And just as important, do you have alot running in the background? The modified touchwiz launcher unnamed comes with can be enabled to show a red dot next to the apps that have been opened and are in the background.
If you could list the apps with the red dots.
Sent from my páhhōniē
gr8hairy1 said:
The modified touchwiz launcher unnamed comes with can be enabled to show a red dot next to the apps that have been opened and are in the background.
Click to expand...
Click to collapse
It does? That sounds more like one of the themes that includes TW4.5.
Not all CPUs can overclock - there's a reason it was sold as a 1.2 GHz chip.
Well as I've mentioned before, it could even hand when browsing through my apps menu, browsing the gallery, playing a game (non in particular) and the funny part is that the phone is not even hot to touch.
What I know for sure if that if no OC = no hangs, no reboots.
I do have the App monitor widget that comes with the stock ROM and currently using it on UnNamed 1.3.1 and I only have Widget Locker App. However I have try closing it and still will happen.
Not sure if maybe this CPU is somehow having an issue that makes it unstable as soon as I OC it.
Entropy512 said:
Not all CPUs can overclock - there's a reason it was sold as a 1.2 GHz chip.
Click to expand...
Click to collapse
Now that is new to me, I thought that all of them were OCable. Is there anyway to identify which can be or not OCed?
nope.. just by testing. it does have to do a little bit with the kernel and rom. the roms didnt originally have stable OC. i would assume that all of them do now. one thing you might try is giving them a little more voltage (just a little) at the higher clocks, but be careful. if you increase the voltage that means that you will sink more enery through the cpu and it will get hot quick. make sure you watch the temp.
i find that setcpu is less stable than the built in cm7 oc menu but cm7 doesnt have a voltage menu.
but on the same token... why OC? i can and i did but i dont need to... everything is like butter and i didnt see that huge a gain by OCing it anyways
tmckenn2 said:
nope.. just by testing. it does have to do a little bit with the kernel and rom. the roms didnt originally have stable OC. i would assume that all of them do now. one thing you might try is giving them a little more voltage (just a little) at the higher clocks, but be careful. if you increase the voltage that means that you will sink more enery through the cpu and it will get hot quick. make sure you watch the temp.
i find that setcpu is less stable than the built in cm7 oc menu but cm7 doesnt have a voltage menu.
but on the same token... why OC? i can and i did but i dont need to... everything is like butter and i didnt see that huge a gain by OCing it anyways
Click to expand...
Click to collapse
I know, this Exynos processor is the best out there right now, forget about Qualcomm's Snapdragon on the Skyrocket. I am just trying to OC for the fun of it
Guti1977 said:
I know, this Exynos processor is the best out there right now, forget about Qualcomm's Snapdragon on the Skyrocket. I am just trying to OC for the fun of it
Click to expand...
Click to collapse
Although it makes me wonder if the CPU could be having an issue, since it hard locks when attempting to.
Guti1977 said:
Although it makes me wonder if the CPU could be having an issue, since it hard locks when attempting to.
Click to expand...
Click to collapse
have you ever overclocked PC CPUs? if you have spent much time doing that, then you would know that not every chip, even within the same model/family, will clock the same. take 2 CPUs, from the same batch, same model, with identical hardware tied to them. you will probably find that one clocks higher stable speeds than the other.
its very likely the proc in your phone just cannot handle the overclocks that the next person's could.
Like pirate said, no two pieces of hardware are identical. Sort of shows how much variance there can be in a manufacturing process. Id guess theres a few chips that come off the same line that arent stable at 1.2 ghz, but they dont make it to the devices, whereas one that can handle a higher clock will. (No sense tossing one that exceeds minimum requirements, thatd just be throwing good hardware away)
You could try nudgin the voltage up and seeing how it behaves, just use caution.
Sent from my SAMSUNG-SGH-I777 using XDA App
garyd9 said:
It does? That sounds more like one of the themes that includes TW4.5.
Click to expand...
Click to collapse
My bad. You are correct.
Sent from my páhhōniē
To get mine to overclock to 1.4 and 1.6Ghz I had to actually INCREASE the voltage settings via Voltage control app. So my settings are: 1.6Ghz= 1475mV and 1.4Ghz=1325mV
Try those out and see if is better for you. I tried undervolting the higher voltages and would either lockup or reboot instantly until I tried adding voltages. So you may need to play with your settings to get it to work for you.
Sent From My KickAss ATT SGS2 SPORTING CM7
twiggums said:
Like pirate said, no two pieces of hardware are identical. Sort of shows how much variance there can be in a manufacturing process. Id guess theres a few chips that come off the same line that arent stable at 1.2 ghz, but they dont make it to the devices, whereas one that can handle a higher clock will. (No sense tossing one that exceeds minimum requirements, thatd just be throwing good hardware away)
You could try nudgin the voltage up and seeing how it behaves, just use caution.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Yup, or if they want to sell a "premium" device with a higher clock rate, they will take the parts that test well at 1.4 and sell them as such - meaning parts rated 1.2 will be LESS likely to be overclockable if a device comes out with CPUs rated at 1.4 - like the Galaxy Note did.
Before, anything that could meet the requirements of stable at 1.2 was sold to any Galaxy S II - but now, the premium parts are going into the Note.
RockRatt said:
To get mine to overclock to 1.4 and 1.6Ghz I had to actually INCREASE the voltage settings via Voltage control app. So my settings are: 1.6Ghz= 1475mV and 1.4Ghz=1325mV
Try those out and see if is better for you. I tried undervolting the higher voltages and would either lockup or reboot instantly until I tried adding voltages. So you may need to play with your settings to get it to work for you.
Sent From My KickAss ATT SGS2 SPORTING CM7
Click to expand...
Click to collapse
I am having the same issue as the original poster on my new GS2. I will have to try the settings you mention but would it be possible to do this and also apply /UV to the remaining lower (1000ghz to 200ghz) processor speeds and maintain stability?