What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Often imitated, never duplicated! Focused 1.8.6

So, when the rumored 2.2.1 update for the X launches, are we still gonna be able to install this rom over the ota?

Sent from my DROIDX using DroidForums App
 
DropC said:
So, when the rumored 2.2.1 update for the X launches, are we still gonna be able to install this rom over the ota?

Sent from my DROIDX using DroidForums App
Click to expand...

This ROM would replace the OTA update soooo, theres no point in updating if your planning on using this ROM.
 
droidxchat said:
The following is a fix for the known bug - sysctl.conf tweaks not being applied.

1) In /etc/install-recovery.sh, underneath #!/system/bin/sh, add:

Code: 
busybox sysctl -p /etc/sysctl.conf
this cause the tweaks to be executed at boot, and therefore persistent through reboot

2) In /etc/sysctl.conf, change your code to look like this:

Code: 
vm.swappiness = 0
vm.min_free_kbytes = 2048
vm.dirty_ratio = 95
vm.dirty_background_ratio = 60
vm.oom_kill_allocating_task=1
3) Reboot, then go to terminal emulator or adb and type cat /proc/sys/vm/dirty_ratio. If you get a value of 95, you were successful.

I quickly fixed this up yesterday when it was pointed out that the tweaks weren't active, but decided to test the tweaks for a while to give you guys some better feedback.

You'll notice that i removed vm.vfs_cache_pressure=12. The parameter affect's the kernel's tendency to reclaim dentries and inodes, and lowering it favors retaining over reclaiming. By removing it, the parameter defaults to 100. I prefer to keep it at 100, because I noticed that the value of 12 caused my phone to be much snappier at boot and in the first few hours, but as time went by it got slower and slower. By hour 8 it was turtling so hard that I had to reboot just to get back to homescreen.

You'll also noticed that I added vm.oom_kill_allocating_task=1. This changes the parameter to 1 from the default of 0. With a value of 0, if your phone detects that an app is using too much memory, it will go down your list of running apps and terminate some of them to free up memory. With a value of 1, your phone will terminate the app that is using too much memory instead. I prefer a value of 1, this way memory leaks are dealt with swiftly.

I can also confirm an increase in battery life, with no sacrifice to speed.
Click to expand...
**NOOB ALERT**
I am total noob about tweaking the system. Can you tell me how do I get to /etc/install-recovery.sh, underneath #!/system/bin/sh? Is it ADB Shell that I heard about? If it is true, is there any instruction how to do it ?
 
update on the USB issue.

i reflashed back to stock 2.2. reinstalled a fresh focused 1.8.2 and booted and running stable. my USB was working fine. it would charge fine, recognize by the laptop fine. charging only mode working perfectly.

i rebooted the phone WITH it still plugged in the laptop, and thats when the issues started. when the phone rebooted while plugged in, it didn't acknowledge being plugged in at all. i pulled the usb from the phone and back in, nothing. i plugged it on my desktop, nothing. the phone wouldn't acknowledge the usb connection at all.

took the phone off the laptop and plugged it in to the wall, started charging fine. rebooted the phone again, waited for it to boot and load up and plugged it in the laptop and now its MOTHERFU*KING unmounting the sd card in charge only mode again. EVERY mode but windows media sync dismountes the sd card from the phone. PLEASE can anyone help with this. i do not want to SBF back to stock 2.2 again and relive the last 4 hours.
 
CloudySky said:
droidxchat said:
The following is a fix for the known bug - sysctl.conf tweaks not being applied.

1) In /etc/install-recovery.sh, underneath #!/system/bin/sh, add:

Code: 
busybox sysctl -p /etc/sysctl.conf
this cause the tweaks to be executed at boot, and therefore persistent through reboot

2) In /etc/sysctl.conf, change your code to look like this:

Code: 
vm.swappiness = 0
vm.min_free_kbytes = 2048
vm.dirty_ratio = 95
vm.dirty_background_ratio = 60
vm.oom_kill_allocating_task=1
3) Reboot, then go to terminal emulator or adb and type cat /proc/sys/vm/dirty_ratio. If you get a value of 95, you were successful.

I quickly fixed this up yesterday when it was pointed out that the tweaks weren't active, but decided to test the tweaks for a while to give you guys some better feedback.

You'll notice that i removed vm.vfs_cache_pressure=12. The parameter affect's the kernel's tendency to reclaim dentries and inodes, and lowering it favors retaining over reclaiming. By removing it, the parameter defaults to 100. I prefer to keep it at 100, because I noticed that the value of 12 caused my phone to be much snappier at boot and in the first few hours, but as time went by it got slower and slower. By hour 8 it was turtling so hard that I had to reboot just to get back to homescreen.

You'll also noticed that I added vm.oom_kill_allocating_task=1. This changes the parameter to 1 from the default of 0. With a value of 0, if your phone detects that an app is using too much memory, it will go down your list of running apps and terminate some of them to free up memory. With a value of 1, your phone will terminate the app that is using too much memory instead. I prefer a value of 1, this way memory leaks are dealt with swiftly.

I can also confirm an increase in battery life, with no sacrifice to speed.
Click to expand...
**NOOB ALERT**
I am total noob about tweaking the system. Can you tell me how do I get to /etc/install-recovery.sh, underneath #!/system/bin/sh? Is it ADB Shell that I heard about? If it is true, is there any instruction how to do it ?
Click to expand...

I used Root Explorer. Navigated to the /etc folder, and found the file. Pressed the "Mount R/W" button, then pressed and held the filename until I got a pop-up and scrolled down to 'Open in text Editor.

Made the changes manually (moved very slowly at this step to insure typing accuracy). After changes made, pressed the menu key and chose "Save & Exit". Put phone back in charger to get to full charge. Once full charged did reboot to recovery and cleared Batt stats.

Will be watching battery performance closely this weekend while backpacking. Hoping to get through a day and a half with at least 20% left. Will report on Sunday when back to civilization.
 
Today, after 8 hours unplugged so far....about 20 phone calls, a handful of txting and some playing around Im at 80% battery still. This also being medium voltage overclocked to 1.45ghz.
 
cpjr said:
DropC said:
So, when the rumored 2.2.1 update for the X launches, are we still gonna be able to install this rom over the ota?

Sent from my DROIDX using DroidForums App
Click to expand...

This ROM would replace the OTA update soooo, theres no point in updating if your planning on using this ROM.
Click to expand...

I realize that, but I want my phone to have an up-to-date OTA nandroid. I might not use this ROM anymore if it doesn't support installing over the latest OTA updates.


Sent from my DROIDX using DroidForums App
 
DropC said:
cpjr said:
DropC said:
So, when the rumored 2.2.1 update for the X launches, are we still gonna be able to install this rom over the ota?

Sent from my DROIDX using DroidForums App
Click to expand...

This ROM would replace the OTA update soooo, theres no point in updating if your planning on using this ROM.
Click to expand...

I realize that, but I want my phone to have an up-to-date OTA nandroid. I might not use this ROM anymore if it doesn't support installing over the latest OTA updates.


Sent from my DROIDX using DroidForums App
Click to expand...

That probably needs to be answered by the devs then.

PS- Im not trying to pick, but why? Who cares if you have a nandroid of the current OTA? I mean, it really doesnt matter.
 
jasonx9 said:
I still dont know how to get my contacts back threw back up assisant

Sent from my DROIDX using DroidForums App
Click to expand...

You can't with this ROM. Backup assistant utilizes Motorola's Blur which is removed with this ROM. You should really start using the contacts in your GMail account to maintain your contact list if you are going to be flashing ROM's.
 
Dam can I take the numbers from my verizon account and put them on the sd card ?

Sent from my DROIDX using DroidForums App
 
droidxchat said:
The following is a fix for the known bug - sysctl.conf tweaks not being applied.

1) In /etc/install-recovery.sh, underneath #!/system/bin/sh, add:

Code: 
busybox sysctl -p /etc/sysctl.conf
this cause the tweaks to be executed at boot, and therefore persistent through reboot

2) In /etc/sysctl.conf, change your code to look like this:

Code: 
vm.swappiness = 0
vm.min_free_kbytes = 2048
vm.dirty_ratio = 95
vm.dirty_background_ratio = 60
vm.oom_kill_allocating_task = 1

3) Reboot, then go to terminal emulator or adb and type cat /proc/sys/vm/dirty_ratio. If you get a value of 95, you were successful.
Click to expand...

I hadn't seen this post when I posted this morning. Good work. One problem, though, is that these fixes will be wiped out again if OC settings are changed using JRummy's app. This, I think, is the root of the problem (at least it was for me). Another problem is that this doesn't reapply _all_ of Drod's tweaks; it only runs the stuff in sysctl.conf. Thus, the following should be a complete fix:

1. Navigate to /system/etc/sysctl.conf. If you want to use Drod's original settings, the values should be:


Code: 
vm.swappiness = 0
vm.min_free_kbytes = 2048
vm.dirty_ratio = 40
vm.dirty_background_ratio = 15
vm.vfs_cache_pressure = 12

If you want to use droidxchat's and Inkarnit's tweaks, the values should be:

Code: 
vm.swappiness = 0
vm.min_free_kbytes = 2048
vm.dirty_ratio = 95
vm.dirty_background_ratio = 60
vm.oom_kill_allocating_task = 1

2. Navigate to /system/etc/install-recovery.sh

Make sure the following is there, underneath #!/system/bin/sh:

Code: 
#Run Scripts From init.d
chmod 755 /system/etc/init.d/01cpu
chmod 755 /system/etc/init.d/02vm
busybox run-parts /system/etc/init.d

#Ensure Bootstrap In Case Something Goes Wrong
echo "1" > data/.recovery_mode
sync

You'll notice that you needn't insert the call for busybox to run sysctl.conf in install-recovery.sh. This is because Drod has already inserted this call into the 02vm file. Running the contents of the init.d folder will run sysctl.conf. I should also mention that this isn't a bug with rubix. As far as I can tell, Drod's set this thing up perfectly, it's just that JRummy's app wipes these entries before it writes it's own OC entries. Drod's said he's currently looking for other places to insert these scripts to avoid this conflict. I notified JRummy about this problem a week or so ago, but I'm uncertain if he got the message. Anyhow, both devs do a kickass job and I'm sure they'll figure it out. So, for the moment at least, this process will need to be repeated if you change OC settings using JRummy's app. Alternatively, if you don't use JRummy's app, you shouldn't have to do anything because your install-recovery.sh should be intact.
 
Last edited:
You must log in or register to reply here.
Back
Top