159 replies to this topic

[Nnnnr12]

The only supercharger I got to is 8.2 I think

Sent from my DROID RAZR MAXX Overclocked using Tapatalk 2

To get my over clock to work I had to change the svesels to 54

Sent from my .215 leak razr on arctic215 rom do you wanna get cut?

[capt8210]

If you follow the directions on the first post of this forum should be no problems

Sent from my DROID RAZR MAXX Overclocked using Tapatalk 2

[capt8210]

And if you know what you are doing the paid version of setcpu will let you change gpu control. I don't have a clue on it.

Sent from my DROID RAZR MAXX Overclocked using Tapatalk 2

[miewter]

Sent from my DROID RAZR MAXX Overclocked using Tapatalk 2

ohhh, okay I choose "is executable" my problem is that SetVsel keeps on returning the value on 86% even I am setting it to 52%.

[capt8210]

ohhh, okay I choose "is executable" my problem is that SetVsel keeps on returning the value on 86% even I am setting it to 52%.

Are clicking apply+quit after settingvesel

Sent from my DROID RAZR MAXX Overclocked using Tapatalk 2

[Pitbull82]

I posted links last night for this. U must get setvesel and drop to 58-52 then apply for the over clock to be stable Sent from my DROID RAZR MAXX Overclocked using Tapatalk 2

I downloaded setvsel and have'nt seen a place to change the values. Just the percentages for each vsel to take over at the bottom?? Also, where did you find a 1375 script? I'm trying to find a 1325 script as thats where my phone was stable before. Right now my speeds are all over the place aka no stability, so I need to figure out how to change the vsel or vesel whatever its called? lol

[Nnnnr12]

Are clicking apply+quit after settingvesel

Sent from my DROID RAZR MAXX Overclocked using Tapatalk 2

Are we supposed to click that?

Sent from my .215 leak razr on arctic215 rom do you wanna get cut?

[capt8210]

See the circle with a lightning bolt slide that

Sent from my DROID RAZR MAXX Overclocked using Tapatalk 2

[Pitbull82]

See the circle with a lightning bolt slide that

Sent from my DROID RAZR MAXX Overclocked using Tapatalk 2

yeah I figured out that there is only 1 scale for our phones. In your screenshot you have your set at 86, I set mine at 53 and it seems to be staying where it should now in set cpu. Should I check apply sd card fix as well? Thanks for your input by the way.

[capt8210]

I did don't know if there's a difference tho

Sent from my DROID RAZR MAXX Overclocked using Tapatalk 2

[Pitbull82]

I did don't know if there's a difference tho

Sent from my DROID RAZR MAXX Overclocked using Tapatalk 2

okay, thanks again. I am loving this speed boost that I had back when gingerbread was still our operating system. I know it is still in its infancy, so hopefully it just gets better from here. On gingerbread my phone preferred 1325 but so far so good. Then again I haven't started playing any games like mass effect infiltrator yet. I think you said your phone is clock thats 1375 correct? Where can I find a script for that as well as 1325? I have the old ones from gingerbread but they don't work

[capt8210]

On xda whirleyes forum on overclocking

Sent from my DROID RAZR MAXX Overclocked using Tapatalk 2

[miewter]

My battery gets hot after placing the OC Profile on the root/system/lib/module, i had to place the profile there coz the the SD and SD-EXT won't allow the profile take effect. Any suggestion how to tweek for the battery not to get hot? I am at 52% at setvsel and at 1350MHz Profile.

[capt8210]

Increase vessel to save battery so 80% will help battery

Sent from my DROID RAZR MAXX Overclocked using Tapatalk 2

[PsyberEMT]

Anyone else having issues where the clock gets stuck at 300 after sleep / power on? The OC ran great, phone felt new agian. After a few hours, however, everytime I turn the phone on, the clock is stuck at 300. Open SetCPU and it shows that it's max 1350 min 300, but I have to change the max to something else, then back to 1350 to get it to stick. Same process after a sleep / power on. Was running the 1350 script at boot, thought that was the issue, so I removed it. Now when I boot without running the OC script, I get stuck at 300/300 with 1200 as the max. Run the script manually and 1350 becomes an option, but same issue...once it goes to sleep it gets locked at 300/300.

[bmangia1]

Anyone else having issues where the clock gets stuck at 300 after sleep / power on? The OC ran great, phone felt new agian. After a few hours, however, everytime I turn the phone on, the clock is stuck at 300. Open SetCPU and it shows that it's max 1350 min 300, but I have to change the max to something else, then back to 1350 to get it to stick. Same process after a sleep / power on. Was running the 1350 script at boot, thought that was the issue, so I removed it. Now when I boot without running the OC script, I get stuck at 300/300 with 1200 as the max. Run the script manually and 1350 becomes an option, but same issue...once it goes to sleep it gets locked at 300/300.

I noticed this too. I deleted the fumoto.ko file, set setvsel back to defaults, rebooted and so far it's been normal operation again. I can't seem to run 1350 anyway. Just not stable on my device so stock it is I guess. Unless there's a 1300/1325 option that I'm missing.

[Nnnnr12]

I noticed this too. I deleted the fumoto.ko file, set setvsel back to defaults, rebooted and so far it's been normal operation again. I can't seem to run 1350 anyway. Just not stable on my device so stock it is I guess. Unless there's a 1300/1325 option that I'm missing.

My phone couldn't handle it either. I guess we have to keep waiting.

Sent from my .215 leak razr on arctic215 rom do you wanna get cut?

[garywojdan81]

Been flawless on mine so far with pegasusq/sio combo. I'm using RTB to run the scripts & System Tuner Pro to set the gov/sched with an init.d script.

Sent from my Droid Razr using Tapatalk 2

[miewter]

I noticed this too. I deleted the fumoto.ko file, set setvsel back to defaults, rebooted and so far it's been normal operation again. I can't seem to run 1350 anyway. Just not stable on my device so stock it is I guess. Unless there's a 1300/1325 option that I'm missing.

you can try this:

place the OC Profile in your root/system/lib/module
set permission of the user to R/W/Exe
use SManager to set the OC Profile to 1350MHz
at SetVsel, set % to 80
(i use hotplug plus noop)
reboot and check OC again

that should prevent your phone from returning to stock profile, had this issue before. Also battery keeps on heating so I adjust the Battery % at SetVsel

[capt8210]

I'm not having any problems on mine

Sent from my DROID RAZR MAXX Overclocked using Tapatalk 2