[Q] suggest settings - Motorola Droid 3

what would be some ideal setting for cpu and others that r avilable in romtoolbox for tethering? is there a good throttling hack that i can do? im running d3 with mav rom 4.0. i have rom toolbox, set cpu, and root browser to make any suggested settings. thanks

Related

Set CPu

I searched but couldnt find a clear answer. Is there any reason my set cpu only goes up to 998 max?
That's the native clock speed of the CPU? I don't get your point
SetCPU isn't an over-clocking app, you want a higher speed, you have to flash a kernel that supports the speed you want.
I figured out my problem..I was running a sense rom on my G2 which let me overclock. Its been a while just got my nexus repaired and back from htc i just need a custom rom to overclock..sorry guys

[Q] Best CPU monitor with Froyo 2.2.1

Thinking of installing the CPU monitor SystemPanel App for my SGS running 2.2.1
Need to know whats killing my battery life.
I have heard that it might slow it down though. Can anyone recommend a good CPU monitor app to work with 2.2.1?
Thanks.
I would first recommend if your phone is rooted, to get Titanium Backup and freeze/delete bloatware from phone. SetCPU is a nice app to help downclock your phone's processor by setting up profiles for when you want it to kick in.

Speed up your Nook Color running ICS+

Hello all, today I will be showing you how to speed up your Nook Color a bit... these methods should work for CM9/CM10/CM10.1/Paranoid Android/etc., but I personally found these out while running PA ICS. The apps you may need to make your phone faster are Ram Manager (Free OR Pro) and No Frills CPU Control (In the case that your ROM doesn't have overclocking in settings). Basically, using these "tweaks" (minus overclock, as whenever I flash a ROM the first thing I do is overclock it), I went from a painfully slow (as in, I was ready to go back to Gingerbread) device to a somewhat faster device. I've seen huge differences in launching games and apps especially, and opening to app drawer seems to be smoother also.
CPU Overclock
Either using No Frills CPU Control or the built-in overclock, set your max CPU speed to the highest on the list (not exceeding 1200, but it shouldn't show anything above that anyhow). Change your governor to either Ondemand or Performance (I personally use Ondemand and have no problems with it). Most of you are probably already overclocked though, so please don't look at me like I'm stupid.
Swap Space
Open up RAM Manager and there should be an option to change your swap space at the bottom. I changed mine to about 48 and am content with that, although I must add it may make your SD card's life shorter. This will increase your RAM, thus allowing you to have more apps open at once.
Force GPU rendering
Open Developer Options in your settings app and check "Force GPU Rendering"... I'm guessing this is one of the biggest factors to my tablet becoming smoother, as from research it helps lower end devices achieve a better framerate, although it may decrease your battery life. Also, I cannot guarantee every app will run great with this. I tested a game (Dynamite Jack) with this setting enabled and it wasn't too shabby at all! But yes, I can definitely see a difference in the overall speed of my Nook Color.
Please tell me how these work for you
I tried these settings, but unfortunately didn't perceive any performance improvement.
Good call on RAM manager. Hadn't seen that before, its going on my NC and RAZR now
Can anyone tell me a good reason for that RAM Manager app to have the permissions it does? Location, Identity, and full network access?
Does NOT work. All this app " no frills CPU" does is provide a GUI front end for the settings already found for our nook color using CM 10+ in its "performace" settings. Also this app does not provide over clocking above our set 1100 MHz. You will need a custom over clocking kernel for the encore for this. Check over on the CM 10 kernel thread n the development section.

[Q] Fastest Setting

Hello, I would like to know which ROM you currently O2X users are using and what is the best configuration for ROM for better use of the device performance. I would like a current ROM and know a configuration relative to the kernel, they use a configure script, OC, zram, swappiness, Governor, Shoulder I / O, launcher, and what applications that improve the performance of this device. Thank you.

N910T3 Ram management Issues

Hi guys, my n910t3 is on Tekxodus 5.1.1 with root and xposed. It always seems to close the background apps. In the task manager, my ram usage rarely ever goes to 2gb/2.72gb. I have my background processes set to the standard limit. I have tried apps like memory locker and ram manger(root), both of them not working :crying:. I tried to do the build.prop fix that the s6 and note 5 use, but I could not find the ro.config.dha file anywhere. I don't think that Tekxodus is the problem because I always had these problems, and thought that installing a custom rom would fix the problem. Any help would help
michaelw911 said:
Hi guys, my n910t3 is on Tekxodus 5.1.1 with root and xposed. It always seems to close the background apps. In the task manager, my ram usage rarely ever goes to 2gb/2.72gb. I have my background processes set to the standard limit. I have tried apps like memory locker and ram manger(root), both of them not working :crying:. I tried to do the build.prop fix that the s6 and note 5 use, but I could not find the ro.config.dha file anywhere. I don't think that Tekxodus is the problem because I always had these problems, and thought that installing a custom rom would fix the problem. Any help would help
Click to expand...
Click to collapse
The build.prop edit you were talking about (ro.config.dha) has to be added as a new line to the build.prop and you can do that with any root editor. I use 3C Toolbox to add the lines and edit the existing ones.
But honestly, if the RAM management apps aren't able to change it I would try going back to stock software and seeing if the RAM issue still happens. If it does it there too you could have bad RAM blocks (more likely) or the T3 may have a totally different memory management routine that we don't know about (unlikely).

Categories

Resources