Often imitated, never duplicated! Focused 1.8.6

[.paul]

Question: For those of you seemingly having battery issues, are you running Screebl by chance?

Didn't know what that was, so I looked it up. There's no chance I'd use that lol.

I'm gonna wipe the phone tonight when I get home and reload 1.8.6 again. I'm not that worried about it right now, as I can just jump back to 1.6. Right now I think I'm going slightly crazy.

 

[Inkarnit]

In regards to the post about adjusting dirty ratios...

dirty_background_ratio – This is the lowest (percent) amount of memory where a dirty page flush can stop.
dirty_ratio – This is the highest (percent) amount of memory that can be stored before a force flush happens.

The changes you made means that it will store memory until 80% then flush down to 50% if I read right... That does sound like it could increase battery performance, but at what cost to the system?

Edit: more info -
vm.dirty_background_ratio contains 15, which is a percentage of total system memory, the number of pages at which the pdflush background writeback daemon will start writing out dirty data. However, for fast RAID based disk system this may cause large flushes of dirty memory pages. If you increase this value from 15 to 20 (a large value) will result into less frequent flushes.

vm.dirty_ratio contains the value 40, which is a percentage of total system memory, the number of pages at which a process which is generating disk writes will itself start writing out dirty data. This is nothing but the ratio at which dirty pages created by application disk writes will be flushed out to disk. A value of 40 means that data will be written into system memory until the file system cache has a size of 40% of the server's RAM. So if you've 10GB ram, data will be written into system memory until the file system cache has a size of 4GB.

 

[Haigot]

Anyone noticing any issues with Wifi?

I'm struggling to find the network at work where i know I previously had full signal.

My work around currently is using wifi tracker and that must be forcing it to do a full scan and find my network.

Anyone have this issue or know a better fix?

 

[Droid74]

Did you install the Pulse RSS Reader? IIRC, Pulse saves images in the SX.jpg format, and isn't smart enough to drop a .nomedia file in there. Check your SDCard for a Pulse folder, and see if it's full of SX files.

EDIT: Pulse creates folders named S1, S2, etc and fills them with images from your news feeds. Different detail, same basic concept. I'd put dollars to cents you installed Pulse (which just became free, like, yesterday, so I bet most people installed it).

This is a really sloppy, unprofessional oversight on the Pulse developers part.

Oh bah...now i feel like an idiot..I certainly did install pulse to check it out...jeeze! Thanks for pointing me in the right direction...now im going to go stick my head in the sand..:frown:

about the battery issue...Im not running screeble.

 

[deathshead]

Hey is anyone running the onix Galaxy S theme over this? I dont know How I would live without it!

 

[detox]

After upgrade, i decided to run a quadrant standard @ 1.45ghz just to see what it would do and a blew my previous high of 1804 out of the water. This is nice!

Sent from my DROIDX using DroidForums App

 

[Boblank]

Auto reboot in recovery

Sorry for the duplicate post, i asked this early this morning and did not see any response, does anyone know how to remove or disable the auto reboot into recovery that seems to have been implemented in this version. Thank you to anyone who may know the answer to this.

 

[soccerman316]

I am having an odd issue that I wanted to see if anyone else was experiencing. I was having this same problem with 1.0 and 1.6 and can't figure it out. I did a clean install of the rom (clear data/cache) and I go into battery manager before doing anything else on the phone and I can set up the custom battery saver. Then within an hour i try to go into into the custom setting and it shoots me back to the settings menu. Like i said, this is without installing anything after flashing.

 

[willwillywilson]

Wireless Tether & 3G Hotspot

Pardon me if this question has been asked before but Wireless Tether (from both the market and dev page) didn't work for me on 1.6 and doesn't work for me on 1.8.6 either. I can connect to my device, I see the upload ticker count up, but nothing will download. Also, on 1.8.6, I'm not seeing 3G Hotspot. Am I missing something?

 

[Haigot]

Pardon me if this question has been asked before but Wireless Tether (from both the market and dev page) didn't work for me on 1.6 and doesn't work for me on 1.8.6 either. I can connect to my device, I see the upload ticker count up, but nothing will download. Also, on 1.8.6, I'm not seeing 3G Hotspot. Am I missing something?

The app worked for me if I didn't change any settings

 

[jdhas]

Sorry for the duplicate post, i asked this early this morning and did not see any response, does anyone know how to remove or disable the auto reboot into recovery that seems to have been implemented in this version. Thank you to anyone who may know the answer to this.

To remove auto recovery at boot, just install Droid X Bootstrap, run Droid X Bootstrap, press the "Bootstrap Recovery" button. This will restore the bootstrap recovery to its default behavior.

 

[Inkarnit]

Question: For those of you seemingly having battery issues, are you running Screebl by chance?

I've found that most task managers kill the battery (fastest task killer doesnt effect it much ... if your into task managers). I also re-tweeked the sysctl.conf to

vm.dirty_ratio = 80
vm.dirty_backround_ratio = 50

seems to squeeze 24+ hours out of the extended life battery with 1.25Ghz undervolted cpu with moderate-light use.
Yesterday I was on it pretty much 100% of the time I was awake and got an easy 16 hours of use. WOW!!!

So I did some more research on this and it does indeed seem that these values should be increased for increased battery performance... What I found shows that vm.dirty_ratio at 95 and vm.dirty_background_ratio at 60 are the best settings. That being said, I don't think the sysctl.conf file is actually being applied. I ran cat /proc/sys/vm/dirty_ratio and got a result of 20 and then ran cat /proc/sys/vm/dirty_background_ratio and got a result of 5. What do we need to do to get these settings to apply?

 

[Boblank]

Sorry for the duplicate post, i asked this early this morning and did not see any response, does anyone know how to remove or disable the auto reboot into recovery that seems to have been implemented in this version. Thank you to anyone who may know the answer to this.

To remove auto recovery at boot, just install Droid X Bootstrap, run Droid X Bootstrap, press the "Bootstrap Recovery" button. This will restore the bootstrap recovery to its default behavior.

Thank you very much for the reply. I did what was suggested, but it still boots into recovery on a standard reboot. Any other suggestions?
Thank you

 

[jdhas]

Sorry for the duplicate post, i asked this early this morning and did not see any response, does anyone know how to remove or disable the auto reboot into recovery that seems to have been implemented in this version. Thank you to anyone who may know the answer to this.

To remove auto recovery at boot, just install Droid X Bootstrap, run Droid X Bootstrap, press the "Bootstrap Recovery" button. This will restore the bootstrap recovery to its default behavior.

Thank you very much for the reply. I did what was suggested, but it still boots into recovery on a standard reboot. Any other suggestions?
Thank you

I'm stumped! You could try doing the same thing in ROM Manager -- set the Bootstrap Recovery there. I swear that one of these reset my bootstrap recovery to the default behavior.

Though, to be honest, how often are you powering off your phone that this is really a problem? Not trying to be snide, just curious.

 

[TopHatDrew]

Awesome!! :greendroid: