Often imitated, never duplicated! Focused 1.8.6

[ScottyDsntKnow]

If you head into one of the juiced theme threads, he should have a link to his build.prop mods in his sig. I'm using the one without the screen density mod (although I tried it and didn't like it) and I do notice a difference. With his build.prop and the new Focused I have battery life like never before with light use/gaming over the last day or so now that I've settled on Focused vs Blurry.

One other thing I noticed and am not sure if it is the new build.prop or Focused but the signal bars are now actually accurate vs before I would either get full bars everywhere or 1-no bars (when I'm inside at work). Now the bars actually mesh with what the actual DPM signal is which makes me kind of mad that Verizon (and the rest do it too) would fudge the signal status so you think you're getting great coverage everywhere.

 

[gmenfan83]

If you head into one of the juiced theme threads, he should have a link to his build.prop mods in his sig. I'm using the one without the screen density mod (although I tried it and didn't like it) and I do notice a difference. With his build.prop and the new Focused I have battery life like never before with light use/gaming over the last day or so now that I've settled on Focused vs Blurry.

One other thing I noticed and am not sure if it is the new build.prop or Focused but the signal bars are now actually accurate vs before I would either get full bars everywhere or 1-no bars (when I'm inside at work). Now the bars actually mesh with what the actual DPM signal is which makes me kind of mad that Verizon (and the rest do it too) would fudge the signal status so you think you're getting great coverage everywhere.

Please post link I can't find for some reason

 

[droydhead]

Hey guys.. I wrote yesterday about how my phone kept switching to 1X mode constantly. It's still doing it today, and yes, I did the *228 right after I installed 1.8.6. I've also tried using Fission 2.1 and Im getting the exact same thing.. I have a feeling it has something to do with 2.2.1.. When I was on 1.6 my 3G was pretty rock solid, it wasn't perfect but definitely not like it is now.

For example, if I put my phone side to side with my wife's LG Ally, her's has full 3G and never drops to 1X, while mine drops out and switches to 1X 2 or 3 times in a 10 minutes time span..

Is anyone else having this issue? If not, then maybe it's my phone, but like I said, 1.6 was pretty good. Maybe I'll try an SBF when I get home and start over.

If any of the devs know of this issue, I'd be more than happy to help and do some testing.

Do you still have a nandroid of your 1.6 install? If so, could verify it there as well... (??).

I do have a nandroid of my 1.6.. I tested it and the 3g doesn't drop like it does with 1.8.6.. It does drop every once in a while but not constantly. Actually, 1.6 dropped 3G the least out of any custom rom or stock rom.

I've always had minor 3G dropping issues even with the original stock 2.1, 2.2 OTA and all roms but it wasn't really a big deal. Now it is really noticeable. Also, I've had 3 or 4 different X's(because of pixels, speaker buzz, etc.) and all of them had the same issue, but again, it was minor.

I'm sure I will have the same issue if/when verizon does the new OTA if that's what this new rom is based off of.

Not a big deal if I have to go back to 1.6, since it runs awesome anyways.. I'm just surprised no one else is having this problem.

Hey guys.. I just wanted to update my post here about my 3G constantly dropping.. I did an SBF and reinstalled 1.8.6. My phone is now flawless.. I've been running solid 3G since the SBF, not one single drop... In fact, my phone has been running the best it ever has. :icon_ banana:dancedroid

I dont understand why but it worked. When I installed 1.8.6 the first time, I wiped dalvik, battery stats, wiped data and cache but apparently the SBF goes even further. I will be doing an SBF before every major rom upgrade from now on .

Thanks again Drod for such a solid rom!!

 

[droydhead]

sephtin and drod, thank you both for the work and help.

coming to focused 1.8.6 from blurry .3/1.0 has been good so far, but ive got a couple of the same problems blurry had along with a few new ones.

blurry1.0 had an issue with usb and connecting to my laptop/desktop for some reason. when connected on anything but windows media sync, the phone would dismount the sd card and it would be available to the pc. same thing is happening now on focused 1.8.6.

im having issues with the signal completely dropping. phone calls still work fine while showing no bars whatsoever. it comes back after a few seconds.

the memory and random resetting issue. i understand from the faq that this is a framework issue with moto looking for blur. is this something that would be worth going back to blurry (1.x now) or hang on? i like this so far; however really had no real issues with blurry 1.0 other than the usb issue.

sound settings. am in retarded to where i cannot find anything to change the acoustis settings. was that a moto/blur app or what can i use to change the dsp settings of the phone?

the phone contacts list. is there an alternative that shows the dialer on the right side of the screen, similar to the recent call history where its a one click dial?

for ****s and giggles, im interested in the build.prop mods that alter quad scores. not for the purpose of being the coolest dude on the earth ever, but more to prove a point of how useless quad scores are altogether.

apologies if some of this has been covered before. just starting on the 35 pages backwards now.

Not sure about your other problems but for the signal drop issue, try doing an SBF and start from scratch. I had signal dropping issues and the SBF fixed mine 100%. It might even clear up the rest of your issues at the same time.

 

[sephtin]

So, you're saying that Facebook doesn't add the Facebook option under accounts? It's not there until you add the application.. or did I miss something.

No I'm saying facebook itself doesn't have a sync now function. It only has an option to change what "sync now" does under accounts > facebook. but that sync now isn't a function of facebook its a function of Accounts and Sync Settings.

BUT, it's possible that the fault of the "Sync Now" function could still be the contacts app. It could be that opening the contact to get the pic works in Contacts, but that the sync now function for some reason doesn't play well with the contacts apk itself.
I'm not talking about this screen, or that screen, I'm talking about the application as a whole, same with facebook (which includes the facebook functionality in the accounts settings menu).

No because the sync now function of gmail works fine with the contacts app. This is because the "sync now", which again is a function of Accounts and Sync Settings, not the contacts app or facebook, is successful in pulling the information from gmail, whereas it is unsuccessful in pulling the information from facebook.

THIS is where the confusion is coming from... Drod didn't exactly remove the blur, he simply didn't include the components with Blur in the first place.
It's possible that adding back some packages or pieces of framework (blur based, or not) could make this work differently, or .. otherwise. But when I say I'm blaming "the framework".. I'm saying that the apps are probably not playing well with the framework components that tie everything together... Especially since they are from completely different sources.

Sorry for the confusion, but in all honesty, It's much more likely that it's a pairing of incompatible pieces of a puzzle, than it is a missing piece that will magically resolve this issue.

As more and more of the framework is replaced with AOSP, etc. rather than the Moto Derived (SDK or otherwise) stuff.. then we'll see more things work properly..
Due to the locked boot loader, it's limited as to what Dev's can do.. With what he has to work with, Drod has put together an amazing ROM...

Right, so I was responding to you saying 'framework won't be changing unless there's a big update' and so I shouldn't 'look for a big change to this issue anytime soon'. I'm pointing out that this isn't really to do with the framework, but more to do with the partial restoration of apps responsible for facebook syncing to contacts, specifically, this is a problem with account and sync settings pulling the information from facebook. currently, it does nothing when given the order to sync facebook information.

Put simply, the problem is with the contacts app retrieving information from facebook. the pathway is Contacts <-> Accounts and Sync Settings <-> Facebook. We've already established that it isn't a problem with the contacts app tying into accounts and sync settings because gmail works just fine, even with contact images. That leaves the pathway between Accounts and Sync Settings and Facebook as the culprit. Now we look for another standard: In blurry, which doesnt have this problem, the same facebook app is used as in focused, which does have this problem. The difference between the two roms lies in Accounts and Sync Settings, and other blurred apps that are missing. The culprit is then narrowed down to Accounts and Sync Settings not having the required collaborative support.

Sounds like you've got it figured out! Let us know when you have the fix!

 

[droidxchat]

FIX: Sysctl.conf

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:

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:

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.

 

[Inkarnit]

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:

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:

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.

Thanks for figuring this out! I was trying to figure out how to make it permanent and you did. Excellent. As for the vm.vfs_cache_pressure=12 line, I completely agree. Through my research I found that this does indeed cause a slowdown over time and was going to suggest leaving it alone as well. I'll try adding that vm.oom_kill_allocating_task=1 line in there as well to test its performance out. There's another tweak or 3 that I'm testing out too and I'm sure Drod will include in future builds if they turn out to work as hoped.

 

[Droid74]

im so sad

So my battery issues continue. My phone was at 100% when i went to bed last night. When I got up it was at 80%. After 2 brief phone calls my phone is at 50%. I would love for someone to help me with this or for it to be addressed. As it is this ROM is nonfunctional for me =(. Maybe ill try the new Blurry or go back a version =(. Im very upset about this.

 

[cpjr]

So my battery issues continue. My phone was at 100% when i went to bed last night. When I got up it was at 80%. After 2 brief phone calls my phone is at 50%. I would love for someone to help me with this or for it to be addressed. As it is this ROM is nonfunctional for me =(. Maybe ill try the new Blurry or go back a version =(. Im very upset about this.

Its most likely not the ROM but how/what you have installed. I have been running this ROM since release along with all the previous version with EXCELLENT battery life.

You need to tell us what exactly you did when you installed it and how your phone is set up.

PS- Have you tried using your phone completely stock for a few days to see if you still have battey issues? It could even be your battery.

 

[jasonx9]

How do I get my contacts back this things kinda confusing I am not sure how to use it yet.

 

[Inkarnit]

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:

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:

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.

So my battery issues continue. My phone was at 100% when i went to bed last night. When I got up it was at 80%. After 2 brief phone calls my phone is at 50%. I would love for someone to help me with this or for it to be addressed. As it is this ROM is nonfunctional for me =(. Maybe ill try the new Blurry or go back a version =(. Im very upset about this.

Did you try wiping battery stats after FULLY CHARGING your phone?

 

[NattyBee]

So my battery issues continue. My phone was at 100% when i went to bed last night. When I got up it was at 80%. After 2 brief phone calls my phone is at 50%. I would love for someone to help me with this or for it to be addressed. As it is this ROM is nonfunctional for me =(. Maybe ill try the new Blurry or go back a version =(. Im very upset about this.

Its most likely not the ROM but how/what you have installed. I have been running this ROM since release along with all the previous version with EXCELLENT battery life.

You need to tell us what exactly you did when you installed it and how your phone is set up.

PS- Have you tried using your phone completely stock for a few days to see if you still have battey issues? It could even be your battery.

Haha, I was ready to say basically the same thing...I'm experiencing excellent battery life, I did nothing special, I applied 1.8.6 over 1.6 only wiped cache...I deleted ADW and otherwise made no changes...I've been off charge now since 7am and I'm at 90%...so 3.5 hours...I'm sure some who've done tweaks/etc. have better batt life, but 1.8.6 is proving the best life since I bought the X.

Another thing I wanted to mention, I'm thinkin his phone may be picky with the rom, mine gives me Handcent issues regardless whatever I did on SSX (even after sbf), but nobody else could reproduce the issues, and the issue was only present on SSX... just a thought...

 

[NattyBee]

How do I get my contacts back this things kinda confusing I am not sure how to use it yet.

Once you log into your google account, it should automatically sync your contacts...just give it time...

 

[Irish Cream]

1.8.6 had my phone running FLAWLESSLY with the exception of battery life, but I am a battery hog running streaming music or winamp the whole time and listening via bluetooth.

I did notice certain themes magnified this issue..

Don't want to spoil anything, but there are some awesome changes coming!!!

 

[cpjr]

Ive been unplugged for 2 1/2 hours (not long) but have sent a few txts, made a few phone calls and such....and am still showing 100% battery.

The first full day I was running the ROM I was at around 70% after 12 hours of use. Making calls and texting with some playing inbetween.

I also run overclocked medium voltage @ 1.45ghz, performance governer. I could underclock and get even better battery life