Often imitated, never duplicated! Focused 1.8.6

[sephtin]

so since my battery life still sucks I thought I would try and SBF again. I do have a question...is it a problem if my device does not show up in RSD Lite? It still starts running and doing its thing without my device listed (in that left window).
Thanks

Think it only shows the device info, if you hit the show device button.. (?).
I don't pay attention, if you hit start, and it goes through the motions, and says 100%, complete... then boots into Stock MotoBlur.. I wouldn't worry too much about it.

 

[drod2169]

Quick questions -- Why would you want to modify the permissions at each boot before it's called? Why not just modify them once and remove that step from the calling procedure? Also, 03banner and 04screen will be called when you run parts, but these have the same initial permissions as 01 and 02, yet you're not modifying their permissions, so then wouldn't they not be recognized at all regardless?

First of all, all of you are WAY smarter than you look

Jokes aside, I'm glad everyone has been getting involved. The sysctl tweaks are (were, as of Focused 1.8.9 test build) beta. I was adjusting and trying to find all different ways to have the same stability and speed, while making battery life sky rocket.

Inkarnit was nice enough to test some things out for me, and ironically, the SAME day he sent me the first pm about adjusting dirty ratio and dirty background ratio, i already adjusted the values and added a few more. Draining ~6% battery over a period of an hour with moderate use, and ~10% with heavy use.

Now to the permissions question..
When I first released 1.0, the permissions wouldn't set for init.d in my update script, I patched install-recovery right away to give the correct permissions, which at the time, I only had those two.

I have found a different spot to call upon startup scripts with the help of jrummy (amazing guy, by the way) and it is now in place. I HIGHLY recommend to LEAVE sampling rate and up threshold how I adjust them, and NOT adjust them through setcpu or through jrummy's app. 1.8.9 will be out as soon as some more testing is done to verify everything is good dancedroid

edit: One thing I forgot, please please please, every one, stop looking at quadrant scores. The next release will prove disappointing if you follow quadrant scores and let that placebo effect take over you. My phone has literally NEVER run this fast before.

 

[Droid74]

One more question...It finished, rebooted and asked me to reboot the phone manually. I did that but it never said complete after i rebooted the phone. Everything seems fine tho. I would assume it completed the process even tho it didn't say complete...correct?
Thanks

 

[drod2169]

One more question...It finished, rebooted and asked me to reboot the phone manually. I did that but it never said complete after i rebooted the phone. Everything seems fine tho. I would assume it completed the process even tho it didn't say complete...correct?
Thanks

yeah. that's actually a bug with rsd lite. to get it to finish via that ui, you have to actually hold the buttons to boot it back into the bootloader when the phone is rebooting after the sbf is finished.

 

[Droid74]

One more question...It finished, rebooted and asked me to reboot the phone manually. I did that but it never said complete after i rebooted the phone. Everything seems fine tho. I would assume it completed the process even tho it didn't say complete...correct?
Thanks

yeah. that's actually a bug with rsd lite. to get it to finish via that ui, you have to actually hold the buttons to boot it back into the bootloader when the phone is rebooting after the sbf is finished.

oh crap..does that mean i have to do it again??? so when i reboot i have to hold the volume keys with the power button and when i get to bootloader ill be good?

 

[droidxchat]

First of all, all of you are WAY smarter than you look

Jokes aside, I'm glad everyone has been getting involved. The sysctl tweaks are (were, as of Focused 1.8.9 test build) beta. I was adjusting and trying to find all different ways to have the same stability and speed, while making battery life sky rocket.

Inkarnit was nice enough to test some things out for me, and ironically, the SAME day he sent me the first pm about adjusting dirty ratio and dirty background ratio, i already adjusted the values and added a few more. Draining ~6% battery over a period of an hour with moderate use, and ~10% with heavy use.

Now to the permissions question..
When I first released 1.0, the permissions wouldn't set for init.d in my update script, I patched install-recovery right away to give the correct permissions, which at the time, I only had those two.

I have found a different spot to call upon startup scripts with the help of jrummy (amazing guy, by the way) and it is now in place. I HIGHLY recommend to LEAVE sampling rate and up threshold how I adjust them, and NOT adjust them through setcpu or through jrummy's app. 1.8.9 will be out as soon as some more testing is done to verify everything is good dancedroid

edit: One thing I forgot, please please please, every one, stop looking at quadrant scores. The next release will prove disappointing if you follow quadrant scores and let that placebo effect take over you. My phone has literally NEVER run this fast before.

Nice! can't wait!! And for those of you who don't want to wait for the new version to have your sysctl.conf fix, here's it is:

UPDATED FIX to KNOWN BUG - SYSCTL.CONF NOT BEING EXECUTED ON BOOT

This will set your sysctl.conf to the following variables:

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

This will also make those changes persistent after reboot, even if you use jrummy's app and change frequencies at boot!!

This will also enable 01cpu, 02vm (which calls sysctl.conf), 03banner, and 04screen in init.d. I was going to remove 01cpu, but by drod's suggestion in the above quote, I decided to leave it because he probably knows better than I do. Drod intended each of these to be enabled but because of a conflict, they haven't been enabled persistently (until this fix).

Install this fix as you would any other fix, by MAKING A BACKUP and then installing zip from sdcard in bootstrap recovery. You do NOT need to wipe data/cache.

I am not responsible for damage to your phone, and this fix is not supported by the rom developer.

 

[bignadad]

BIG Credit to dev on this ROM....

Was on OTA Froyo 2.3.15 and wanted something different. After much searching and reading i decided to go with RubiX Focused 1.8.6... WOW! Didn't think a blurless ROM would make that much difference but it does... The functionality of the device is so much smoother now. And FAST! This ROM is noticeably faster that stock Froyo OTA with tweaks... Just and incredible job with this ROM...

Also, i liked it so much that i am making a theme to work with it
here is a preview...

 

[drod2169]

First of all, all of you are WAY smarter than you look

Jokes aside, I'm glad everyone has been getting involved. The sysctl tweaks are (were, as of Focused 1.8.9 test build) beta. I was adjusting and trying to find all different ways to have the same stability and speed, while making battery life sky rocket.

Inkarnit was nice enough to test some things out for me, and ironically, the SAME day he sent me the first pm about adjusting dirty ratio and dirty background ratio, i already adjusted the values and added a few more. Draining ~6% battery over a period of an hour with moderate use, and ~10% with heavy use.

Now to the permissions question..
When I first released 1.0, the permissions wouldn't set for init.d in my update script, I patched install-recovery right away to give the correct permissions, which at the time, I only had those two.

I have found a different spot to call upon startup scripts with the help of jrummy (amazing guy, by the way) and it is now in place. I HIGHLY recommend to LEAVE sampling rate and up threshold how I adjust them, and NOT adjust them through setcpu or through jrummy's app. 1.8.9 will be out as soon as some more testing is done to verify everything is good dancedroid

edit: One thing I forgot, please please please, every one, stop looking at quadrant scores. The next release will prove disappointing if you follow quadrant scores and let that placebo effect take over you. My phone has literally NEVER run this fast before.

Nice! can't wait!! And for those of you who don't want to wait for the new version to have your sysctl.conf fix, here's it is:

UPDATED FIX to KNOWN BUG - SYSCTL.CONF NOT BEING EXECUTED ON BOOT

This will set your sysctl.conf to the following variables:

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

This will also make those changes persistent after reboot, even if you use jrummy's app and change frequencies at boot!!

This will also enable 01cpu, 02vm (which calls sysctl.conf), 03banner, and 04screen in init.d. I was going to remove 01cpu, but by drod's suggestion in the above quote, I decided to leave it because he probably knows better than I do. Drod intended each of these to be enabled but because of a conflict, they haven't been enabled persistently (until this fix).

Install this fix as you would any other fix, by MAKING A BACKUP and then installing zip from sdcard in bootstrap recovery. You do NOT need to wipe data/cache.

I am not responsible for damage to your phone, and this fix is not supported by the rom developer.

That is likely the cause of the crappy battery, the lack of tweaks running. STILL don't know what caused it, cause after 1.8.6 was released I immediately made a new version with different tweak values to test and it worked fine..

One thing I noted, is 03banner was causing run-parts /etc/init.d to error out, so I'd recommend removing that. It's in other places as well, don't you worry, my rom is safe (which by the way, if you opened it, you've found my "security measure that a few people got scared over)

 

[Droid74]

cant wait for that theme!!!

 

[droidxchat]

First of all, all of you are WAY smarter than you look

Jokes aside, I'm glad everyone has been getting involved. The sysctl tweaks are (were, as of Focused 1.8.9 test build) beta. I was adjusting and trying to find all different ways to have the same stability and speed, while making battery life sky rocket.

Inkarnit was nice enough to test some things out for me, and ironically, the SAME day he sent me the first pm about adjusting dirty ratio and dirty background ratio, i already adjusted the values and added a few more. Draining ~6% battery over a period of an hour with moderate use, and ~10% with heavy use.

Now to the permissions question..
When I first released 1.0, the permissions wouldn't set for init.d in my update script, I patched install-recovery right away to give the correct permissions, which at the time, I only had those two.

I have found a different spot to call upon startup scripts with the help of jrummy (amazing guy, by the way) and it is now in place. I HIGHLY recommend to LEAVE sampling rate and up threshold how I adjust them, and NOT adjust them through setcpu or through jrummy's app. 1.8.9 will be out as soon as some more testing is done to verify everything is good dancedroid

edit: One thing I forgot, please please please, every one, stop looking at quadrant scores. The next release will prove disappointing if you follow quadrant scores and let that placebo effect take over you. My phone has literally NEVER run this fast before.

Nice! can't wait!! And for those of you who don't want to wait for the new version to have your sysctl.conf fix, here's it is:

UPDATED FIX to KNOWN BUG - SYSCTL.CONF NOT BEING EXECUTED ON BOOT

This will set your sysctl.conf to the following variables:

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

This will also make those changes persistent after reboot, even if you use jrummy's app and change frequencies at boot!!

This will also enable 01cpu, 02vm (which calls sysctl.conf), 03banner, and 04screen in init.d. I was going to remove 01cpu, but by drod's suggestion in the above quote, I decided to leave it because he probably knows better than I do. Drod intended each of these to be enabled but because of a conflict, they haven't been enabled persistently (until this fix).

Install this fix as you would any other fix, by MAKING A BACKUP and then installing zip from sdcard in bootstrap recovery. You do NOT need to wipe data/cache.

I am not responsible for damage to your phone, and this fix is not supported by the rom developer.

That is likely the cause of the crappy battery, the lack of tweaks running. STILL don't know what caused it, cause after 1.8.6 was released I immediately made a new version with different tweak values to test and it worked fine..

One thing I noted, is 03banner was causing run-parts /etc/init.d to error out, so I'd recommend removing that. It's in other places as well, don't you worry, my rom is safe (which by the way, if you opened it, you've found my "security measure that a few people got scared over)

i'm not getting any errors with running it, just checked in terminal and alogcat. should i have my update remove it anyway?

 

[drod2169]

Nice! can't wait!! And for those of you who don't want to wait for the new version to have your sysctl.conf fix, here's it is:

UPDATED FIX to KNOWN BUG - SYSCTL.CONF NOT BEING EXECUTED ON BOOT

This will set your sysctl.conf to the following variables:

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

This will also make those changes persistent after reboot, even if you use jrummy's app and change frequencies at boot!!

This will also enable 01cpu, 02vm (which calls sysctl.conf), 03banner, and 04screen in init.d. I was going to remove 01cpu, but by drod's suggestion in the above quote, I decided to leave it because he probably knows better than I do. Drod intended each of these to be enabled but because of a conflict, they haven't been enabled persistently (until this fix).

Install this fix as you would any other fix, by MAKING A BACKUP and then installing zip from sdcard in bootstrap recovery. You do NOT need to wipe data/cache.

I am not responsible for damage to your phone, and this fix is not supported by the rom developer.

That is likely the cause of the crappy battery, the lack of tweaks running. STILL don't know what caused it, cause after 1.8.6 was released I immediately made a new version with different tweak values to test and it worked fine..

One thing I noted, is 03banner was causing run-parts /etc/init.d to error out, so I'd recommend removing that. It's in other places as well, don't you worry, my rom is safe (which by the way, if you opened it, you've found my "security measure that a few people got scared over)

i'm not getting any errors with running it, just checked in terminal and alogcat. should i have my update remove it anyway?

Nah.. nevermind then. It must of just been in the test build I have.

 

[migdroid]

Great rom. I had to skip 1.6 and loved 1.0 but this one is a killer. No f/c with lcd 200 o/c 1.35 lv and great battery life. linpak or quadrat are not even install. But it feel faster

 

[ToastPlusOne]

I'm not sure if this has been reported or if I'm in the right place but my screen has been randomly turning on in my pocket or while I'm talking. It wont go back off unless I do it manually. This means I'll have to notice it. Needless to say, its been a major battery drain. Ideas?

Only other complaint I have is the keyboard. Other than that, I love the rom. It's awesome.

 

[sephtin]

I'm not sure if this has been reported or if I'm in the right place but my screen has been randomly turning on in my pocket or while I'm talking. It wont go back off unless I do it manually. This means I'll have to notice it. Needless to say, its been a major battery drain. Ideas?

Only other complaint I have is the keyboard. Other than that, I love the rom. It's awesome.

Have not seen this.
Have you made any other mods? Theme? ??
Try loading Focused again, don't wipe cache/data, see if you can recreate this after...

 

[scubieman]

So is this ROM suppose to be great with battery life? Okay? or not so good?