2233 replies to this topic

[ZKK007]

Well the only reason I overclock is to run high-end games such as Dead Trigger [Highest Graphics Setting] as smoothly as possible as well as have apps start faster and the overall UI experience be smoother and faster.

Besides, Ive got a Razr MAXX and I charge it every night while I'm asleep. Gotta find someway to actually use all 3300 mAh of that MAXX battery in an average day

On ICS I was stable while overclocked to 1375 MHz on stock Interactive Governor! Man this thing was quick and benchmarked into the sky, but became extremely hot and way too quicky while gaming and I felt it was too risky. I figure 1250 MHz - 1325 MHz would be the ideal top frequency in a MAXX.

So I love your choices, but they dont stick, what I am finding is:
- Under NoFrills CPU Control, after applying and making sure "Apply On Boot" is checked, it will say it was a success and SuperUser Permissions successfully grant it access.
- If the phone is used or idles for 10-15 minutes, and you go back to NoFrills, it will say 1325 in the requested box but the current will reset to 1200. Doesnt matter which Governor you choose.
- After Reboot, SuperUser grants NoFrills its access and says application on boot was a success, but you go into NoFrills and it will say the current is again 1200 max.

I kinda wonder if a permissions fix would solve this, but have no idea when to do it (before using utility to install overclocking? After? Before Applying Values? After?)

I also wondered if using SuperSU instead is safe. Ive always preffered SuperSU because its automatic Grant Permissions feature actually works and makes working on a ROM 10 times easier. I installed Super SU and then used Motomizer to remove SuperUser.apk and it seems to be working, but maybe this is my problem? The Binary did update so I doubt its SuperSU, but it is a possibility.

That is interesting. Please let me know if your values stick now that you have SuperSU. I have no problem baking it in if it solves the problem!

[wallacengineering]

That is interesting. Please let me know if your values stick now that you have SuperSU. I have no problem baking it in if it solves the problem!

Well I found something problematic already. I was in Motomizer about to backup all my apps and data in case something goes wrong while I mess with permissions, and I get this message:

"BusyBox Compatibility is Low, Upgrade is Recommended"

Is there a way to update BusyBox?

[ZKK007]

Well I found something problematic already. I was in Motomizer about to backup all my apps and data in case something goes wrong while I mess with permissions, and I get this message:

"BusyBox Compatibility is Low, Upgrade is Recommended"

Is there a way to update BusyBox?

When I made 2.0.0 I updated to the latest busy box (that was about 2 weeks ago). I will check when I get home if there was another version released

[lazer]

My No Frills CPU control/OC seems to stick fine without any issue. Even verified with Temp/CPU widget which shows the operational Mhz. My only issue with this rom is the "Beats Audio" otherwise it is stellar!

[ZKK007]

My No Frills CPU control/OC seems to stick fine without any issue. Even verified with Temp/CPU widget which shows the operational Mhz. My only issue with this rom is the "Beats Audio" otherwise it is stellar!

Good to hear! Im playing around with AC!D so that will be fixed in the next build

I think there are some isolated issues still floating around though. I just noticed that my phone isn't going into deep sleep and the only thing I've done is delete, recreate and flash on other ROM slots. So I'm a bit confused as to why this has started all of a sudden

[wallacengineering]

Good to hear! Im playing around with AC!D so that will be fixed in the next build

I think there are some isolated issues still floating around though. I just noticed that my phone isn't going into deep sleep and the only thing I've done is delete, recreate and flash on other ROM slots. So I'm a bit confused as to why this has started all of a sudden

My No Frills CPU control/OC seems to stick fine without any issue. Even verified with Temp/CPU widget which shows the operational Mhz. My only issue with this rom is the "Beats Audio" otherwise it is stellar!

I believe I have found a source for a cure on the Beats Audio problem.

As an advid hacker I always have multiple custom ROMs running on my device (All four SafeStrap slots are filled LOL).

Yesterday I filled the final slot with the Android Agression ROM by prstorero found

Please Login or Register to see this Hidden Content

I have been testing it and have used the Beatz application and it is fully functional and working! There is no stock Audio Effects app and so it seems his idea was similar to the temporary solution I found for Aviator.

On a side-note, I believe it could just be No-Fills having reading issues on overclocking. I used the Aviator Tool to push OverClock Modules into Android Agression and again on this ROM NoFrills reads that the current Max Frequency resets to "1.2 GHz" after 20 minutes or a reboot. However, I found that Quadrant Standard (Benchmarking App) states under system information that the Max Frequency is still 1250MHz.

I am going to test 1300 and 1325MHz OverClock modules on Aggression and then reboot and without going to No-Frills at all, go to Quadrant after a 30 minute idle and see if the overclock stuck and then see if No-Frills still resets the information.

I will then boot into Aviator and try all the tests again as well.

This may take a few days as I just rebooted into Aviator to do Battery Calibration for it last night (never got around to it earlier). I am doing the full optional drain until the phone dies and then recharge fully without powering on (ensures the absolute most perfect calibration) and wow does your ROM have some battery life! 9 Hours, 37 Minutes on battery thus far and still 74% battery remaining. Its gonna be a looooooonnnnnnnggggggg calibration lol.

[ZKK007]

On a side-note, I believe it could just be No-Fills having reading issues on overclocking. I used the Aviator Tool to push OverClock Modules into Android Agression and again on this ROM NoFrills reads that the current Max Frequency resets to "1.2 GHz" after 20 minutes or a reboot. However, I found that Quadrant Standard (Benchmarking App) states under system information that the Max Frequency is still 1250MHz.

I am going to test 1300 and 1325MHz OverClock modules on Aggression and then reboot and without going to No-Frills at all, go to Quadrant after a 30 minute idle and see if the overclock stuck and then see if No-Frills still resets the information.

I would use caution when pushing scripts into other ROMs as all ROMs are set out slightly differently when it comes to the init.d scripts. In Aviator the "Modules" script is what contains the OC values as well as the pre-set governor loader. I believe in Android Aggression the script is call "90Modules." So when you use the aviator utility to push the script, you will end up with two module scripts. I don't think this will cause a huge problem, but you might want to look into what each one contains just so you don't have double ups which might cause things to change upon reboot. It sounds like you know what you are doing, but I thought I'd mention anyway

[wallacengineering]

I would use caution when pushing scripts into other ROMs as all ROMs are set out slightly differently when it comes to the init.d scripts. In Aviator the "Modules" script is what contains the OC values as well as the pre-set governor loader. I believe in Android Aggression the script is call "90Modules." So when you use the aviator utility to push the script, you will end up with two module scripts. I don't think this will cause a huge problem, but you might want to look into what each one contains just so you don't have double ups which might cause things to change upon reboot. It sounds like you know what you are doing, but I thought I'd mention anyway

Honestly You know alot more than I do and I will heed your warning.

I am a computer nerd and have been building, overclocking and fixing Windows computers since age 12, but I am still very new to Android. This is my first ever Smart Phone and I have only had it since September 2012.

More than this, I have only been hacking since January this year. Before 2013 my Razr was just stock lol. But I am always eager to learn more and troubleshooting custom ROMs is exactly the sort of thing that will do just that

[ZKK007]

Just in case anyone else had issues of the phone not entering deep sleep, I found clearing wiping cache and dalvik cache fixed it

[rickw]

my oc'ing works just fine from utility

[islandfever]

Is there any reason why my Handcent keeps forclosing on this? But not Go SMS?

Ive done all the cahce clearing, uninstall reinstall, fix perm etc....I am stumped

[OldBaldy]

Is there any reason why my Handcent keeps forclosing on this? But not Go SMS?

Ive done all the cahce clearing, uninstall reinstall, fix perm etc....I am stumped

Use handcent all the time and have never had a force close on this Rom.

Sent from my DROID RAZR

[islandfever]

Use handcent all the time and have never had a force close on this Rom.

Sent from my DROID RAZR

Might be bcuz I removed Messaging.apk before I loaded ROM...trying again....

[islandfever]

OK, starting to get frustrated....installed this on diff slots, wiped....done it ALL 4x over....and still every time I cant get the SMS apps to work, even stock now. wtf?

Actually I think it might be a system file I am restoring from Titanium from the version 1.8 Rom

[ZKK007]

I've added a poll. Now that everyone has tired the AOSP messaging app, I want to see if you all still prefer it to the Stock messaging app. I know either way there will still be people who wont like what is built into this ROM, but I'd like to try make most of you happy

Just an update: I've been working with AC!D audio, but I'm finding small issues (volume slide wont show movement when changing volume) so I'm working on finding a perfect mix. I haven't been working too hard on the next update as I have been busy with other stuff, but I'm also waiting to see if we do get official JB anytime soon

[ZKK007]

OK, starting to get frustrated....installed this on diff slots, wiped....done it ALL 4x over....and still every time I cant get the SMS apps to work, even stock now. wtf?

Actually I think it might be a system file I am restoring from Titanium from the version 1.8 Rom

Yeah, you should not restore system files with TiBu

[ZKK007]

Ok guys, here is a test build that you may try:

Please Login or Register to see this Hidden Content

It will have 2.0.1 in some places so just ignore the version numbers.

Beats is more or less the only thing I have changed with this test. I do have a poll going on which messaging app you guys prefer, so please vote. The one which gets the most votes will be in the next update.

I changed my mind and decided to fix Beats instead of changing it to AC!D. So please make sure Beats is working for you This has the AOSP Mms.apk and it should still be able to send pictures.

This test should be compatible with all themes and the utility that is posted for v2.0.1. If some testers could confirm these for me that would be great

Enjoy!

P.S. The wallpaper is just an idea at the moment. It is Jupiter's rings

[Brian]

Downloading Now!

[lazer]

Dirty flashed over 2.0.1

All seems well. Beats seems to be working (No force close) just hard to tell through speakers if EQ is working so will test later with BT in my car.

Pics both send and receive - I'm using GO SMS

Utility works for both "simple battery" and OC to 1300!

Thanks for the update!

[wallacengineering]

Ok guys, here is a test build that you may try:

Please Login or Register to see this Hidden Content

It will have 2.0.1 in some places so just ignore the version numbers.

Beats is more or less the only thing I have changed with this test. I do have a poll going on which messaging app you guys prefer, so please vote. The one which gets the most votes will be in the next update.

I changed my mind and decided to fix Beats instead of changing it to AC!D. So please make sure Beats is working for you This has the AOSP Mms.apk and it should still be able to send pictures.

This test should be compatible with all themes and the utility that is posted for v2.0.1. If some testers could confirm these for me that would be great

Enjoy!

I have found the source of my overclocking problems but do not have a fix for it. You can use my method to see if you have the same problems.

To ACTUALLY check CURRENT CPU information accurately:

- Download a ROOT file explorer (i.e. Root Explorer or ES File Manager [If using ES, be sure system directory is mounted as Read/Write (r/w)])
- Start the ROOT running file explorer
- Follow this path EXACTLY to get to your CPU Info (You should start at just "\", meaning ssystem base, otherwise go up levels until just that slash appears): \sys\devices\system\cpu\cpu0\cpufreq\
- Once you are here there there are SIX files you need to open in Text Viewer, these files are:

• cpuinfo_max_freq
• scaling_available_frequencies
• scaling_available_governors
• scaling_governor
• scaling_max_freq
• scaling_setspeed

PROBLEMS I FOUND (After Using Aviator Utility to OverClock Aviator ROM, then using NoFrills CPU control to apply overclock with "PegasusQ" Governor and "sio" Scheduler [1300 MHz Selected]):

I will list what each of my four files said and then I will explain why this means my CPU CANNOT OverClock (Opened in Text Viewer):

cpuinfo_max_freq: 1300000
scaling_available_frequencies: 300000 615000 850000 1100000 1300000
scaling_available_governors: boostedASSv2 pegasusq smartassV2 hotplugx interactivex hotplug ondemand userspace interactive performance
scaling_governor: pegasusq
scaling_max_freq: 1200000
scaling_setspeed: <unsupported>

NOTE:
If I set OverClock using NoFills and then WITHOUT rebooting or allowing my device to sit and idle (usually under 10 minutes), and immately use RootExplorer and view the six files , this result appears:


cpuinfo_max_freq: 1300000
scaling_available_frequencies: 300000 615000 850000 1100000 1300000
scaling_available_governors: boostedASSv2 pegasusq smartassV2 hotplugx interactivex hotplug ondemand userspace interactive performance
scaling_governor: pegasusq
scaling_max_freq: 1300000
scaling_setspeed: <unsupported>

WHAT DO THESE RESULTS MEAN?:

Basically, the Scaling Max and CPU Info Max not displaying the same values is why my "Current Max Clock Frequency" reverts to "1.2 GHz" after my phone idles for about 10 minutes OR is rebooted. The Scaling Speed is controlled by "scaling_setspeed" and the fact that mine says "unsupported" means there is an issue. There is obviously a set speed because my phone will change frequencies on PegasusQ and use the 300, 615, 850, and 1100MHz frequencies, but will not use the 1300.

I believe the Scaling Set Speed is "unsupportive" of custom modules/clocks. If I open it using text editor and delete the "<unsupported>" and then "save and exit", it will fail and say no changes were applied. this will mean that when No-Frills attempts these changes, it will fail as well.

The cpuinfo_max_freq not being the same as scaling_max_freq is why my OverClock seems to work at first and reverts later. Basically, cpuinfo is just an information database that benchmarks and other applications use when you hit "system information". In basic terms, my phone is lying about its capabilities LOL. Scaling Max is the "REAL" value.

A SIMPLE WAY TO TEST YOUR SYSTEM:
- Go to the adroid Play Store and download an app called "CPU Benchmark"
- Go into NoFrills CPU Control and set your overclock of choice.
- Allow your phone to idle/screen-off and do not touch it for 10-15 minutes
- Start the CPU Benchmark app
- Click "Run Test" and watch the "CPU Speed" field
- Go to NoFrills again and set your values again
- DO NOT allow your device to idle/screen-off and go directly into CPU Benchmark
- Click "Run Test" and watch the "CPU Speed" field
- Reboot
- Let Phone Idle for 5 minutes after startup to allow apps to settle and allow NoFrills to apply its CPU settings
- Without doing ANYTHING else to your phone at ALL, goto CPU Benchmark and click "Run Test" and watch "CPU Speed"
- Post your results on this forum thread

ZKK007, I hope this helps you in your development!