Often imitated, never duplicated! Focused 1.8.6

[scubieman]

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

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

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

No it will not do the OTA update. But rom developers usually update these ROMS before verizon will even release the OTA updates.

 

[blackdraggin]

love your work

bought u a red bull so u cant stop, wont stop, get it get it

 

[DropC]

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

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

No it will not do the OTA update. But rom developers usually update these ROMS before verizon will even release the OTA updates.

I don't want to be able to OTA from the ROM... I know that's not possible. I just want to know if the ROM can be installed over the OTA when it comes out.

 

[DropC]

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

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

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.

I'm not completely sold on the ROM yet, just for the few incompatibilities with the AOSP framework and the hardware on the X. I really do like the ROM, but I want the latest stock OTA to be there, too. I jump between the two literally every other day.

 

[scubieman]

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

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.

I'm not completely sold on the ROM yet, just for the few incompatibilities with the AOSP framework and the hardware on the X. I really do like the ROM, but I want the latest stock OTA to be there, too. I jump between the two literally every other day.

So stay with OTA then root it. Or go 100% back to stock.

 

[sephtin]

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

Won't really know untill it releases. It's very possible that they could update things to close the exploit that allows us to tap into the logwrapper, and DroidXBootstrapper would no longer work... that would mean no ROMs at all.
I know it currently isn't the case with the version of 2.3.20 that was available for the Droid2... but just saying. Could be other things that cause serious problems for ROMs as well...

If/when the OTA comes out, I recommend giving it a week or two to see both what the advantages, AND disadvantages are...

 

[cpjr]

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

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.

I'm not completely sold on the ROM yet, just for the few incompatibilities with the AOSP framework and the hardware on the X. I really do like the ROM, but I want the latest stock OTA to be there, too. I jump between the two literally every other day.

It takes the place of whats there....its not a mixture of both, lol.

 

[sephtin]

i think my issues regarding the restarting are b/c of my lcd density mod in the build.prop. another reason im going back to blurry as it never had the issue.

looking forward to an update and coming back to focused once the bugs are worked.

contacts not a big deal, it just creates a second step in the dialing process.

the build.prop edits ill have to take a look at again. ive done my own manual build.prop editing each release but didn't look for those specific mods.

thanks again for the support. i was quite happy with blurry and have been VERY impressed with focused so far. id really like to stay on focused, but im really at the point of phone to wall contact b/c of the usb and sound issues right now. to save my insurance deposit im going to sbf back, see how blurry 1.5.2 does then consider focused in the near future.

The reboots are certainly made worse by changing LCD Density. This is a known issue with Focused.

The sound application wasn't designed for the framework that's in place.. and don't know of anther that's available.. not sure if this will change...

Regardless, enjoy Blurry, it's also a great ROM!

 

[sephtin]

I still dont know how to get my contacts back threw back up assisant

Sent from my DROIDX using DroidForums App

Dam can I take the numbers from my verizon account and put them on the sd card ?

Sent from my DROIDX using DroidForums App

There IS a patch to make BUA work, but it's not worth the hassle. Just save yourself the headaches, and migrate those contacts to Google Contacts:
Migrating contacts from "Phone" (BackUp Assistant), to Google Contacts

 

[sephtin]

Usb issues

For the few that are having USB Issues...

Someone over on DroidXForums was having the issue, and has stated that they fixed it by going into ROM Manager, and choosing the FixPermissions option...

If anyone tries this, please report back and let us know if it helps!

 

[droidxchat]

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:

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:

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:

#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.

Thanks humungus! I would choose not to use 01cpu since it modifies cpu threshholds and sampling rates, and i had considered this to be redundant if using jrummy's app. 02vm is the memory management tweak that drod made, and also, as you mentioned, will call busybox sysctl, though there would be no difference between that being in 02vm and that being in install-recover.sh since install-recovery.sh is calling 02vm. But as you pointed out, the problem still remains:

For anyone using jrummy's OC app, if you change any of your boot settings, on your next reboot you will lose persistance of sysctl.conf, meaning you won't have the tweaks being applied after that.

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?

 

[sephtin]

I don't want to be able to OTA from the ROM... I know that's not possible. I just want to know if the ROM can be installed over the OTA when it comes out.

Ahh, that makes more sense.

There is NO WAY to know if ANY ROM will install over the next OTA, until the OTA is in the hands of the developers...

 

[unseenme]

Another update...just downloaded JRummy's OC app & SetCPU, set it to low voltage, set the frequencies 1200/66, 1000/60, 850/59, 400/38. Much more stable & smooth! Quadrant score went to 1573. This phone CONTINUES to get better & better!

Swyped from the BIGGEST BADDEST machine on the planet

 

[scubieman]

For the few that are having USB Issues...

Someone over on DroidXForums was having the issue, and has stated that they fixed it by going into ROM Manager, and choosing the FixPermissions option...

If anyone tries this, please report back and let us know if it helps!

I used titanium backup to restore my apps. I reinstalled and started 100% fresh. I then did not use titanium backup and so far im doing good.

 

[Droid74]

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