I'm still running the stock version of froyo on my Droid... Is an alternate rom really that much better? I don't have too many complaints about it as it stands - just that sometimes my home screens take a long time to reload my widgets if I change orientation or run a memory hog of a program.I ran bugless beast on my Moto Droid, which was a great mod. My current Droid X is rooted, but I haven't bothered with running a custom mod on it, as Motorola's new locked bootloaders make it more time consuming than I really care for. The first Moto Droid was a plethora of openness, everything else from Motorola is not. As much as I love my X, I think I might move to HTC for my next phone. I'm waiting to see what the mod community does for the thunderbolt.
The rom I used included a lot of tweaks and optimization for running a custom kernel and overclocking, both of which I enjoyed tinkering with. Aside from that, there really wasn't a huge reason to run a custom over stock, especially when stock froyo works so well.I'm still running the stock version of froyo on my Droid... Is an alternate rom really that much better? I don't have too many complaints about it as it stands - just that sometimes my home screens take a long time to reload my widgets if I change orientation or run a memory hog of a program.
Best to use the latest nightly instead of RC2. A few bugs were fixed just after the RC hit.HTC Aria running cyanogen 6. I might update now that RC2 is up.
Androids not a bad system, but it's not yet great by any means. The battery life is atrocious if you actually want to use your phone, I might try windows phone 7 once my contract is up, or go back to the iPhone.
They will remain in memory, but they won't use battery. The only time apps use battery is if they're putting a strain on the processor, or (this is the big one) accessing the mobile network. Android uses memory differently than windows or other operating systems most people are used to. Windows wants to keep as much memory as free as possible, but the opposite is true for Android. Android will hold apps in cache to improve speed and performance, but it takes no more battery power to hold 20 apps in memory than it does to hold nothing in memory. By using a task killer and constantly clearing the cache, you're forcing android to rebuild that memory list, and this will drain your battery faster than if you leave it alone.please enlighten me, whats wrong with using a task killer? I find that if I don't go through and close my contact, kindle, browser etc through my task killer they stay open the entire time and kill my battery faster than a boy on prom night.