1609 replies to this topic

[garywojdan81]

Can I ask what you are using to overclock... I thought I have been keeping up but did not see anything in the thread or on the ROM which let you overclock.. would be interested....

The cpu control module is already there. All I did was find the script & put it in the init.d folder & give it all permissions. The first line has to direct to wherever you have busybox installed& you can tweak the voltages/frequencies by editing the script.

Sent from my DROID RAZR using Tapatalk 2

[heatonb1]

Ok so I did my due diligence and searched all 28 pages for 45 minutes and could not find a post about my issue so if I missed it then sorry for the repost,

First off i love this ROM so great work but I am having terrible battery life and data issues. I was on Simplex and had great battery life about 8 hours with heavy usage, now i get about 6 hours with very little usage. I did adjust the CPU in settings, turned off Google now and just wiped cache so I will see how that does over the next few days. FYI this morning I took it off the charger at 6am made two calls, no browser, facebook, email etc.. yet and now at 9am i am at 66% battery.

For the data it keeps telling me it cant find data and needs to change to global when i do it sometimes finds data other times I have to switch back to GSM/LTE. Either way whether if I am on Global or GSM/LTE I will rarely have 4g. Even at my work which is downtown about a half mile from the tower I will get 4g for about 1-2 bars for maybe 15 minutes then it will change to 3g with full bars then 20 minutes later switch back to 4g with 1-2 bars, any suggestions? I am on the current update .10 Sept. 7th version

Thanks for any suggestions that people may offer

[james]

I meant the source of your phone calendar ... Google calendar, Exchange calendar or what?

Google calendar

[rickw]

Ok so I did my due diligence and searched all 28 pages for 45 minutes and could not find a post about my issue so if I missed it then sorry for the repost,

First off i love this ROM so great work but I am having terrible battery life and data issues. I was on Simplex and had great battery life about 8 hours with heavy usage, now i get about 6 hours with very little usage. I did adjust the CPU in settings, turned off Google now and just wiped cache so I will see how that does over the next few days. FYI this morning I took it off the charger at 6am made two calls, no browser, facebook, email etc.. yet and now at 9am i am at 66% battery.

For the data it keeps telling me it cant find data and needs to change to global when i do it sometimes finds data other times I have to switch back to GSM/LTE. Either way whether if I am on Global or GSM/LTE I will rarely have 4g. Even at my work which is downtown about a half mile from the tower I will get 4g for about 1-2 bars for maybe 15 minutes then it will change to 3g with full bars then 20 minutes later switch back to 4g with 1-2 bars, any suggestions? I am on the current update .10 Sept. 7th version

Thanks for any suggestions that people may offer

first off,any rom you install needs to settle a couple days to adjust before you can ever test battery life,next don't use google now as it tears the battery up,check for any apps that might be using battery,i don't ever mess with govs and cpu and have great battery life

[dimitri407]

Is anyone still having the double widget selection screen when trying to add a widget in the stock launcher?

[jibroney]

The cpu control module is already there. All I did was find the script & put it in the init.d folder & give it all permissions. The first line has to direct to wherever you have busybox installed& you can tweak the voltages/frequencies by editing the script.

Sent from my DROID RAZR using Tapatalk 2

There is no need to add another script to init.d to overclock. The "90modules" script in init.d already does this. The problem is the "99test" script (also in init.d) runs later in the boot sequence and resets the cpu frequency table back to stock specs.

The "99test" script does nothing but write the word "done" to a temp file. It is used as a test to make sure init.d is working properly on initial setup. For whatever reason, the Devs decided to use this script to reset the freq table back to stock. Long story short, If you want to overclock you can simply edit or delete /etc/init.d/99test . If you choose to edit the file, keep the first and last two lines of the script and delete everything else. Save and reboot. This will set the set the frequency table to 300MHz, 500MHz, 750MHz, 1000MHz and 1350MHz.

The only caveat is that not everyone's device responds well to being overclocked to 1350 MHz. You may also have to edit the "90modules" script and change the line "echo 4 1350 1410 > /proc/cpu_control/tweak_cpu" to something like "echo 4 1325 1405 > /proc/cpu_control/tweak_cpu", or "echo 4 1300 1400 > /proc/cpu_control/tweak_cpu".

HTH

[heatonb1]

@rickW

thanks for the reply. Yeah I am not to worried about battery i usually give each rom about a week to settle before really looking in depth into battery. As for the screen usage it is at 58% but only 28 mins of usage, voice calls is 18% with only 15 mins usage all rest is 5% or below but as being at 100% battery at 6am and 5 hours later at 44% with the above usage still seems as though the battery is being drained awfully fast. i also use juice def ultimate and so wifi and data is off when screen not on. as for the data at home I did a speed test and on wifi i get 20 down 5 up which is typical on 4g i get 5 down 512k up which i use to get about 15 down 8 up. I have worked in telecom for over 8 years in engineering design so I understand how speed test aren't always accurate and mobile data is diff than consumer data but with those stats it appears that my 4g data is not working optimally. as of now ive been on this rom for 2 days so i still have testing left to do

[quangtran1]

Google calendar

When I get back to my office, I'll give you some suggestions. I'm on the road ATM.

[nightwatcher]

There is no need to add another script to init.d to overclock. The "90modules" script in init.d already does this. The problem is the "99test" script (also in init.d) runs later in the boot sequence and resets the cpu frequency table back to stock specs. The "99test" script does nothing but write the word "done" to a temp file. It is used as a test to make sure init.d is working properly on initial setup. For whatever reason, the Devs decided to use this script to reset the freq table back to stock. Long story short, If you want to overclock you can simply edit or delete /etc/init.d/99test . If you choose to edit the file, keep the first and last two lines of the script and delete everything else. Save and reboot. This will set the set the frequency table to 300MHz, 500MHz, 750MHz, 1000MHz and 1350MHz. The only caveat is that not everyone's device responds well to being overclocked to 1350 MHz. You may also have to edit the "90modules" script and change the line "echo 4 1350 1410 > /proc/cpu_control/tweak_cpu" to something like "echo 4 1325 1405 > /proc/cpu_control/tweak_cpu", or "echo 4 1300 1400 > /proc/cpu_control/tweak_cpu". HTH

Thanks for the update.. looks good so far at the 1350...

[aety9]

Flashed at work today. was a bit surprised with the loading screen music XD

A little loud for my taste, but the ROM works very well! Nicely done!

[Shinare]

There is no need to add another script to init.d to overclock. The "90modules" script in init.d already does this. The problem is the "99test" script (also in init.d) runs later in the boot sequence and resets the cpu frequency table back to stock specs.

The "99test" script does nothing but write the word "done" to a temp file. It is used as a test to make sure init.d is working properly on initial setup. For whatever reason, the Devs decided to use this script to reset the freq table back to stock. Long story short, If you want to overclock you can simply edit or delete /etc/init.d/99test . If you choose to edit the file, keep the first and last two lines of the script and delete everything else. Save and reboot. This will set the set the frequency table to 300MHz, 500MHz, 750MHz, 1000MHz and 1350MHz.

The only caveat is that not everyone's device responds well to being overclocked to 1350 MHz. You may also have to edit the "90modules" script and change the line "echo 4 1350 1410 > /proc/cpu_control/tweak_cpu" to something like "echo 4 1325 1405 > /proc/cpu_control/tweak_cpu", or "echo 4 1300 1400 > /proc/cpu_control/tweak_cpu".

HTH

I'm wondering what the reason they did this... so as to not brick phones? Was going to do as suggested and realized I'm happy with its speed now, and bricking it would make me not happy with the speed. heh

[garywojdan81]

<br />There is no need to add another script to init.d to overclock. The "<em>90modules</em>" script in init.d already does this. The problem is the "<em>99test</em>" script (also in init.d) runs later in the boot sequence and resets the cpu frequency table back to stock specs.<br /><br />The "99test" script does nothing but write the word "done" to a temp file. It is used as a test to make sure init.d is working properly on initial setup. For whatever reason, the Devs decided to use this script to reset the freq table back to stock. Long story short, If you want to overclock you can simply edit or delete /etc/init.d/99test . If you choose to edit the file, keep the first and last two lines of the script and delete everything else. Save and reboot. This will set the set the frequency table to 300MHz, 500MHz, 750MHz, 1000MHz and 1350MHz.<br /><br />The only caveat is that not everyone's device responds well to being overclocked to 1350 MHz. You may also have to edit the "90modules" script and change the line "echo 4 1350 1410 > /proc/cpu_control/tweak_cpu" to something like "echo 4 1325 1405 > /proc/cpu_control/tweak_cpu", or "echo 4 1300 1400 > /proc/cpu_control/tweak_cpu".<br /><br />HTH

<br />Thanks, I learn something new everyday
Just tried this method to implement overclock & it works perfectly.
<br /><br />Sent from my DROID RAZR using Tapatalk 2

[Kebob]

I used to have oc but testing it out some peoples devices had issues so i put them stock. I may have some surprises for those of you with stable phones

[RHChan84]

I used to have oc but testing it out some peoples devices had issues so i put them stock. I may have some surprises for those of you with stable phones

Sounds good. Can't wait

[rosso]

wow how did u get them to sync mine says sync is not available right now

That is what happened when i was on arctic 214....i tried many things short of reinstalling the entire rom....

[SpyderMan]

Coming soon... QuickSettings from RAZR M. Thanks to fastboot_oem_unlock and others.

Please Login or Register to see this Hidden Content

Showing it off on my CM10 HTC One S

@ All, I d/l'ed this file, wiped cache & dalvik & rebooted after the system updated & it gave me an error msg saying that homescreen stopped… ??

I restored my nand backup, & tried again - no luck.

Any ideas? tia,

[madmunkey]

I am having terrible battery life. Screen using 66% today
...mod use

Tried a few different governors
Google now off
Underclocked to 1.0

Any recs on governor or settings to try?

I'm having the same issue. Otherwise it's great!

[wyld]

Going on 12 hours now still have 55% battery left Og Razr. Screen 66%...light to moderate use.

Sent from my DROID RAZR using Tapatalk 2

[srzero]

Here are my tweaks

Please Login or Register to see this Hidden Content

[Rom](Razr-Cdma)-Flick-1.3.0-[9/09/12]#entry95351

[milkshed27]

What purpose do the numbers in the script names in the init.d folder serve? For example, 90modules, 91zipalign, 99test. I've also seen the scripts numbered from 1-13. Is it the order in which the scripts are run? If so can one choose any number sequence?