Related
I am on CM 4.0.2. All my apps seem to work fine, but there seems to be some slight hesitation when lifting the app drawer - just slightly choppy. I saw a lot about the fix_permissions in console, does this address that? Or is that solely for apps that are not working? I am under the impression it does NOT help this.... but wanted to be certain. Does this mean I perhaps need to adjust my SD partitions?
Should one run that code even if all of the apps appear to be working correctly?
I did not see steps for running the script in all of the posts I saw... any help on this?
This will not help. You fix permissions to possibly help with FC.
Choppiness comes from not enough memory. Check what's running in the background and adjust accordingly. Check your comcache settings, adjust. Check your swap settings, adjust. Be advised though... there's only so much you can do, we are working with very limited hardware here.
FYI... I would really look into what's running in the background first. I run cm 4.02 with default comcache, no swapper. I have 7 widgets and it only stutters occasionaly, I barely notice. I would REALLY look into your backgrouds. Also, don't forget about GPS/Wireless location issue, that may be causing it too.
Good luck
Interesting... i use advanced task killer prior to rooting and when apps were killed i was around 55MB. Now, after root i can only get around 41MB. I never understood what made this lower... i assumed it was stuff cyan added to make his rom open. I do not use many widgets (3 maybe) and generally leave wifi and gps off.
Thoughts?
Anyone who uses system panel knows its the best task manager and the ONLY one that shows the device true multitasking. It's shows 3 categories, active running apps, cached inactive apps, and system processes. All 3 of this group shows up in 2.1. But in 2.2 froyo there is no longer cached apps group. It skips from active apps to system processes.
I asked the developer and he responded with the following:
http://androidforums.com/android-ap...eople-who-hate-task-killers-2.html#post882019
To Roger: sorry for delay in getting back to you as well, as far as I can tell the N1 with Froyo does not have any inactive/cached apps. I'm running the leaked Froyo version as well. On the other test phones (an Incredible, a Droid, and a G1) as well as in (non-Froyo) emulators I do see inactive processes as before.
Click to expand...
Click to collapse
Does anyone know what this means exactly? Has android 2.2 been changed where in no longer pre-loads apps? My observations on froyo using system panel shows that my running app list is now much larger than eclare with no cached apps at all, ever. Has Google changed this and removed cached apps? Or perhaps view are just now hiding it somehow so task managers cannot see this info?
If true then system panel would need an update. But that response from the developer seemed to not indicate that.
bump. so not ONE person noticed that froyo doesnt cache apps anymore?
RogerPodacter said:
bump. so not ONE person noticed that froyo doesnt cache apps anymore?
Click to expand...
Click to collapse
this may only be an issue with the pre-released Froyo.
harolds said:
this may only be an issue with the pre-released Froyo.
Click to expand...
Click to collapse
perhaps, but that seems like a pretty significant change to the OS. i'm wondering if they either changed the way the OS works completely, or if its just a bug that is being fixed for the final release of 2.2.
The 2.2 leak has a lot of missing code in it.
alot.
JCopernicus said:
The 2.2 leak has a lot of missing code in it.
alot.
Click to expand...
Click to collapse
i hope your right
RogerPodacter said:
bump. so not ONE person noticed that froyo doesnt cache apps anymore?
Click to expand...
Click to collapse
I don't have an N1 so can't answer your question, but I did notice that the developer you spoke to, TESTED FROYO ON A G1!!!
Seems logical to me to keep out until ready for final release testing, because you can test a lot faster if things aren't being swapped out and in.
cigar3tte said:
I don't have an N1 so can't answer your question, but I did notice that the developer you spoke to, TESTED FROYO ON A G1!!!
Click to expand...
Click to collapse
He's probably not a developer working on Android, probably just a application dev. Why would he be running a leaked version if he worked at Google.. Also, I think maybe he just doesn't know how to properly form a legible sentence since it would seem he meant other phones he has, not specifically that they are running 2.2, though I could see how you might think that reading what he said.
I would just hold off on questions like this until a final release is out, it's pretty pointless to worry about until Google drops an official OTA update.
Ok so now that the official froyo is released, and the multitasking STILL works differently, where do we find out what and how things have changed? Cached apps no longer exist, instead all apps show as running in system panel. I'm surprised there's not more mention of this since it seems a fundamental change in OS has occurred. Anyone have any insight?
On the technical side I can't speak, but for the end user experience, Froyo's multitasking has been the same or better than before. I experience less "jittery" lag and it seems like more programs are not unloaded (ie: run immediately, no load time at all) vs before if you used say Facebook, then browser, K9 mail, few other things, then back to Facebook it was ~1s to reload.. Maybe Facebook is a bad example here, as it seems to ALWAYS load fast, but you get the gist..
It of course could be the extra ram available now... 512M total vs the 256M before?
Well, if they did significantly change something, it was really for the better. Things just fly now switching back and forth.
Of course, I was only stock before and only had access to half the memory. So it could just be keeping a lot more of my apps in memory now that it has access to the full 512mb.
khaytsus said:
On the technical side I can't speak, but for the end user experience, Froyo's multitasking has been the same or better than before. I experience less "jittery" lag and it seems like more programs are not unloaded (ie: run immediately, no load time at all) vs before if you used say Facebook, then browser, K9 mail, few other things, then back to Facebook it was ~1s to reload.. Maybe Facebook is a bad example here, as it seems to ALWAYS load fast, but you get the gist..
It of course could be the extra ram available now... 512M total vs the 256M before?
Click to expand...
Click to collapse
Well using system panel shows that in froyo there is an entire group of missing app now, inactive cached apps, are just flat out gone in froyo. It doesn't seem to be related to the new available RAM in 2.2.
I noticed this on first day on 2.2
I think the possible reason is 2.2 support more than 256M RAM. So the 16MB free RAM threshold is hard to reach now.That's way we didn't see Inactive process. maybe we can try run alot of apps backgroud untill reach 16MB free RAM threshold. Then use systemplane to check if there is any inactive process.
luojs said:
I noticed this on first day on 2.2
I think the possible reason is 2.2 support more than 256M RAM. So the 16MB free RAM threshold is hard to reach now.That's way we didn't see Inactive process. maybe we can try run alot of apps backgroud untill reach 16MB free RAM threshold. Then use systemplane to check if there is any inactive process.
Click to expand...
Click to collapse
I've already tried that, gone down to 14 mb but they do not appear. They are completely gone from the OS, and system panel developer already confirmed that they are gone from 2.2 and It's just the way the OS is now. Check the link I posted earlier in the thread. What we need to find out is WHAT and WHY Google made these changes. Why isn't anything mentioned in the changelog etc?
Are you just interested in knowing why? Or is it affecting you in a bad way? Whatever reason they have, it has improved performance a lot. I just assume they are categorizing them differently now. Because the apps 'running' in the background still aren't really running, they are just waiting in memory in case you need them again.
Clarkster said:
Are you just interested in knowing why? Or is it affecting you in a bad way? Whatever reason they have, it has improved performance a lot. I just assume they are categorizing them differently now. Because the apps 'running' in the background still aren't really running, they are just waiting in memory in case you need them again.
Click to expand...
Click to collapse
I'm just wondering why, and what exactly the changed. My phone runs great with no issues.
Previously system panel showed 3 groups of apps, the first was running apps, and these are the ones actually using some type of resources typically. While the second group was inactive, "frozen" not using any resources.
But now in 2.2 everything goes into the first group. And the OS no longer starts a bunch of apps pre loaded upon boot up. It only loads apps you use now. So still I'm wondering if now these 2 groups are combined into the one active list, can we tell the difference? Or is there no difference anymore, and only running apps are now shown?
Ok, so the frozen category would be ones that were FCed to release their memory. Which could kind of imply that the OS would remember their state.
Android doesn't remember the state for you if it is no longer in memory. It is up to the app to save its state when it is told it is going into the inactive state.
So it could be that the frozen category wasn't actually anything special, just apps that were forced out of memory, and now they don't even mention them anymore.
You said that you couldn't force anything out of the list though, right? If you can't get anything automatically removed form the list, I would say they just combined the two categories.
Clarkster said:
Ok, so the frozen category would be ones that were FCed to release their memory. Which could kind of imply that the OS would remember their state.
Android doesn't remember the state for you if it is no longer in memory. It is up to the app to save its state when it is told it is going into the inactive state.
So it could be that the frozen category wasn't actually anything special, just apps that were forced out of memory, and now they don't even mention them anymore.
You said that you couldn't force anything out of the list though, right? If you can't get anything automatically removed form the list, I would say they just combined the two categories.
Click to expand...
Click to collapse
Another thing that changed is that its not possible to kill most apps. Browser and some others can be killed. But for. If most part if you kill something it just stays there running, or immediately pops back up.
But yes the frozen apps list is just plain gone. It was a useless list anyway. But I wonder what exactly they changed and what it means and how it works.
Can't see why this is the case (but it obviously is) as long as I have lots of free disk space and not many apps running at the same time. Any logic in this?
I've been experiencing the same issue and wondering the same thing...
Sent from my Samsung Galaxy S GT-I9000 using Tapatalk Pro
There seems to be several things causing this, but the two key issues are:
The moviNAND (the internal flash drive/"SSD") firmware seems to have an issue with fsync() taking extremely long. E.g., it slows down whenever a file is written/updated on the internal storage.
RFS, the file system used by Samsung is buggy as hell and corrupts data after a while.
There are several topics on these issues in the Android Development forum. There are also several "lag fixes" trying their best to overcome these issues. Go check them out
Einride said:
There seems to be several things causing this, but the two key issues are:
RFS, the file system used by Samsung is buggy as hell and corrupts data after a while.
Click to expand...
Click to collapse
We have no idea if that is ACTUALLY true.. Just because fsck picked some things up on 1 phone, doesn't mean it happens everywhere.. Furthermore, it doesn't mean the problems detected affect operations
that has no truth at all about more apps slowing down the phone, my phone is the prove
Before jpk i didn't noticed slowdowns with aprox 100 apps, now i do on jpk =/
Prolly that all pictures/links/info stays in his workmemory?
probably cause some of them run in the system memory or run at startup
KaliKot said:
probably cause some of them run in the system memory or run at startup
Click to expand...
Click to collapse
Bingo!
and that is what most people does not realize
they need to Optimize the phone, most people take it for granted
the phone is not a phone, the phone is a mini computer that fits in your hands
just like your big desktop PC it can go crazy if you don't take care of it
AllGamer said:
Bingo!
and that is what most people does not realize
they need to Optimize the phone, most people take it for granted
the phone is not a phone, the phone is a mini computer that fits in your hands
just like your big desktop PC it can go crazy if you don't take care of it
Click to expand...
Click to collapse
Can you tell me why with the same apps installed on the Nexus it doesn't lag like the SGS?
Can you stop blaming users when is the phone which doesn't work as expected?
Oletros said:
Can you tell me why with the same apps installed on the Nexus it doesn't lag like the SGS?
Can you stop blaming users when is the phone which doesn't work as expected?
Click to expand...
Click to collapse
utter ****e -i have well over 100 apps on my sgs and experience NO lag whatsoever!
bonehooch said:
utter ****e -i have well over 100 apps on my sgs and experience NO lag whatsoever!
Click to expand...
Click to collapse
Utter ****e? Why?
it was mentioned many many times
just install autorunkiller and a good task manager then all the problems will be gone
stock ROM is very fast when you maintain the phone
AllGamer said:
it was mentioned many many times
just install autorunkiller and a good task manager then all the problems will be gone
stock ROM is very fast when you maintain the phone
Click to expand...
Click to collapse
With autokiller the phone is still laggy.
And please, stop thinking I'm stupid or I don't know a **** about smartphones, ROM's changing, firmware or knowing how a phone must run.
AFAIK this topic and its responses are for the OP
I have about 190 Apps installed and do not experience any diferene in overall speed of the phone. But only because i know that a lot of the programms start on boot and stay in background.
I have more than 15 apps turned off with the full version of autorun killer to prevent the auto restart of the apps. Otherwise the phone would definetaly slow down.
It´s really incredible what apps start on the boot!
TMReuffurth said:
I have about 190 Apps installed and do not experience any diferene in overall speed of the phone. But only because i know that a lot of the programms start on boot and stay in background.
I have more than 15 apps turned off with the full version of autorun killer to prevent the auto restart of the apps. Otherwise the phone would definetaly slow down.
It´s really incredible what apps start on the boot!
Click to expand...
Click to collapse
Do you need to be rooted ti use all of the functions in autorun killer? I am not rooted.
Can you compile a breif list of the "biggest culprits" to stop with this utility to gain back the most speed and efficiency? I am a bit nervous that I will stop the wrong items and somehow damage my phone...
Autokiller and task killers are not the solution here! Quick lesson on Android, and why having even A SINGLE BAD APP is going to ruin your whole phone!
Android has something called an 'Intent'. In order to start an app, an intent is made by your launcher or a button you press, and the Android system reads this intent and works out what app it needs to start up.
There is a second type of intent though, called a 'Broadcast Intent'. This is an intent that is sent out to anything that is registered to listen to it. This means that an app can register to listen to all sorts of events, such as battery level changed, application start, or a tons of other things. Even if the application is closed, if it is registered as a listener, Android will start it right back up so it can deal with the intent. If the intent comes every 5 seconds, Android will run this app every 5 seconds even if you have a taskkiller killing the app.
The only real solution is to not install apps which are bad! Finding bad apps is a real mission, too. Hopefully in the future, utilities will be available to let us track down these terrible apps, but till then, you'll have to work it out yourself.
yiannisthegreek said:
Do you need to be rooted ti use all of the functions in autorun killer? I am not rooted.
Can you compile a breif list of the "biggest culprits" to stop with this utility to gain back the most speed and efficiency? I am a bit nervous that I will stop the wrong items and somehow damage my phone...
Click to expand...
Click to collapse
No need for Root to use all features of Autorun Killer. I would disable only the apps you know and which you do not need at startup and running in background, such as (in my case) Paypal, App Center from Androidpit, Daily Briefing, Photoshop Express, Word Press, TweetCaster, etc.
Every of these apps works normal, even when deactivatet on startup.
So unless you do not disable system apps (must be previously set enabled in settings) you are safe.
RyanZA said:
(...)There is a second type of intent though, called a 'Broadcast Intent'. This is an intent that is sent out to anything that is registered to listen to it.(...)
Click to expand...
Click to collapse
Is there any possibility/app to show what is registered for which app?
watching the apps
Samga said:
Is there any possibility/app to show what is registered for which app?
Click to expand...
Click to collapse
There is an app called Autostarts at 0.95$.
It shows what is launched au startup, when you enable/disable wifi etc.
It think it gives insight on how apps seems launching out of nowhere.
I also reccomend Watchdog Task Manager Lite, the free version.
It does not kill anything, but notifies and logs the bad apps that consumes over a certain CPU percentage.
Ok, so we all want the best of the best of experiences for our DX superphone. Well, I am here to tell you how I have my setup.
The goals of the ultimate setup are to:
1. Keep as much privacy as possible
2. Ensure the best performance
3. Ensure best method to extend battery life
4. Ensure best feel
5. Ensure HAPPINESS!
NUMBER ONE:
First things first; we need to install the absolute best ROM right now. The ROM is called FISSION 1.1 by Team DeFuse. You will most likely have to re-root the phone after installing though. It is worth the hassle.
Known issues with Fission 1.1 but I'm sure will be fixed:
1. Compass Calibration
2. No custom battery profiles
NUMBER TWO:
We need to install all of our applications.
NUMBER THREE:
If you don't have them already, download the paid version of Titanium Backup and the application called AUTOSTARTS and very very importantly, DROID WALL, SetCPU, CacheMate and also very importantly, Advanced Task Killer
NUMBER FOUR:
Restart phone. Upon reboot, we will first open up Droid Wall and give it root privileges. Then, we are going to fill in both boxes with checkmarks next to only the applications which you use a lot and need internet access! It is good practice to look at what all apps need access to when installing applications. If an app like Notepad for instance needs Internet Access, we know there is a problem. It is apps like these, we don't want to have access to the internet.
You will also have to have checkmarks next to "Media Server", "Browser", "Calender", "Calender Storage", "Email", "Google Search", "Maps", "Market", "Messaging", "Street View", and "Visual VM". Those are the ones which need to be allowed in order to not cripple your Android experience. Obviously, the remaining apps are UP TO YOU.
You should manually disable and re-enable the firewall after every reboot! You then want to kill Droid Wall and the other showing apps with Advanced Task Killer. Once Droid Wall sets the firewall rules, they stick regardless if the app is running or not. There is no need to leave it running.
NUMBER FIVE:
Now, we are going to open up the program AUTOSTARTS! It will take awhile to load all of the apps of your system. This app makes it so you can actually reliably use ADVANCED TASK KILLER without the apps you kill AUTOMATICALLY restarting and thus wasting precious battery.
You want to disable all your 3rd-party user apps in EVERY CATEGORY except for the Widget Categories at the bottom. For the first app you disable from starting, you will have to give AUTOSTARTS root privileges.
Don't disable "Google Voice", "Visual VM", "Dialer", "usb", "Dialer Storage", "Battery Manager", "Battery Manager (Power Profile Receiver)", "Google Partner Setup", "Google Services Framework", "Voice Dialer" (If you use it), "Email" (If you use it), "Messaging", "Bluetooth Share" (If you use Bluetooth), "Contacts Storage", "Droid Wall", "SetCPU", "ADW Launcher" (If use it), "Launcher Prof" (If use it) or "Launcher" (If use the stock launcher)
Everything else should be clicked on and disabled except for apps which are your widgets on your homescreens and in the Widget Categories!
You are going to notice a crazy increase in speed from this!!!!
NUMBER SIX:
We need to reboot. Upon reboot, open up ADVANCED TASK KILLER. We now need to put some apps on the ignore list.
The apps I have on my ignore list are:
SetCPU, Messaging, Music, Google Search, Market, Visual VM, Beautiful Widgets, Voice Search, K-9 Mail and Google Voice
You would also want to put any apps which are related to any widgets you have on your homescreens on the ignore list too!
This will effectively make it so any app we close, IS CLOSED FOR GOOD until we ourselves initiate it MANUALLY.
NUMBER SEVEN:
My phone is a dud; well at least the CPU is. It won't go over 1100mhz and be stable regardless of how much voltage I crank into 'er. So, for my phone, I modified the 1.1Ghz .zip folder which is installed in the Fission folder of your SDCard when you install Fission. I modified the setscaling.sh in text editor and changed the following values:
Changed the 800mhz to 900mhz. You may or may not have to raise the voltages that they have pre-set for the 800mhz and 1100mhz settings. If you are not stable, just give each of them a couple notches of increase.
NUMBER EIGHT:
Upon reboot, we need to setup SetCPU. We are going to create 3 profiles
1. Screen off --> 300min / 600max --> OnDemand
2. Charging AC/FULL --> 300min / 600max --> OnDemand
3. Charging USB/FULL --> 300min/ 600max --> OnDemand
We then go back to the homescreen "of SetCPU" and change our values of what we want the phone to do whenever the screen is on and it is not charging. Here we want to put 900mhz for the min and 1100mhz for the max.
For some reason, even if SetCPU is not disabled in AUTOSTARTS, it doesn't load the values upon reboot. You will have to manually open up SetCPU just one time for each reboot.
IMPORTANT: If you want to OC higher or maybe not even at all, have at it. However, I still think SetCPU and the profiles I listed above would be great for you.
NUMBER NINE:
This may not be an option for some of you, but I like to disable remembering form data, cookies, cache, passwords, and history on my browsers.
The best browser to use "IMHO" is the new XSCOPES version 6.
If you like some other browser, just change the privacy settings to those of above to be safe. If you can't live without, then just don't worry about it.
NUMBER TEN:
Install CacheMate for Root Users.
In the settings we want to have checked:
1. Clear TA Utility Caches
2. Close CacheMate on Close
3. Clear Admob and Google
4. Clear Flash Cache
5. Clear Temporary Cache
Then, we want to have everything checked in Data Experimental and SDCard which is Relevant to our phone. For any app you don't have, don't put a check next to it. If you use apps like APMobile (Associated Press), you want to uncheck that and apps like it so you don't have to set it up every time you open the app.
I don't really like letting CacheMate run all the time being set to automatically clear on intervals. I didn't mention it, but I NEVER leave ADVANCED TASK KILLER run all the time either.
Uncheck power clear on the main screen and clear the cache ever day or two.
NUMBER ELEVEN:
Install ADW Launcher. It is by far better than LauncherPro. Only continue to use LauncherPro if you can't live without its widgets.
In ADW Launcher, we want certain settings done.
1. In Screen Preferences, we want to have both Desktop Scrolling Speed and Desktop Overshoot set to "0"
2. In Drawer Settings, we want animated drawer check, show app labels checked, fade app labels checked and for background color, I like to use a dark color with some transparency!
For Zoom Effect speed, set it to its lowest setting of 300ms
3. Under System Preferences, we want to check Wallpaper Hack and set Scrolling Cache to "Auto". Obviously, if you have widgets, you will want to check scrollable widget support.
4. In UI Settings, I check everything besides:
Dockbar, Closing folder, Secondary ActionButtons and Show Desktop Indicator.
I have AB Scale Factor set to "5".
After you get your homescreens all set up EXACTLY how you want them, backup both the desktop configuration and backup ADW settings. Also, make sure to do another backup in Titanium so when you restore ADW Launcher after installing a new ROM, it is exactly how you had it before.
NUMBER TWELVE:
Open up the program which is already installed called Spare Parts. It will be in your App Drawer. Don't install it again from the market unless you for some reason don't already have it in your app drawer.
1. I have haptic feedback and compatibility mode checked.
2. Set the "Window Animations" and "Transition Animations" to FAST
NUMBER THIRTEEN:
Do a Titanium Backup via Batch operation.
1. There are only 2 options in the batch operation options which you should ever need to use!!! They are:
A) RUN - Backup all new apps & newer versions
B) RUN - Restore Missing Apps with data
Run the backup every once in awhile to keep the backup of your apps up to date.
IMPORTANT:
When restoring apps, UNCHECK ALL SYSTEM APPS FROM BEING RESTORED!
The paid version gives you HyperShell which means you don't have to manually click each app when it is restoring. It makes the process very simple.
You also want to uninstall the older version of Flash Player and get the newer one from the market.
I have followed this guide for Titanium and have installed numerous ROMS for the Droid 1, HTC Droid Incredible and now the Droid X WITHOUT EVER HAVING ISSUES!!!
NUMBER FOURTEEN:
Go into ROM Manager and install the AOSP Keyboard under /Download ROM/Drod2169/CHANGE OPTIONS-Focused-1.0/AOSP KEYBOARD
You will automatically have to check FIXED 8MP AOSP Camera as well. That is the camera installed by default on Fission 1.1 so it won't hurt anything. Don't check backup data or wipe data/cache!
Also, I would install both QuickOffice and DX_Music.zip under the SDCard/Fission/Add-Ons directory. You obviously have to do this in Recovery!!!
The Music player will be 100% identical to the one that comes installed by default on Fission 1.1, but it gives you the option to pause play and seek tracks from the lockscreen!
NUMBER FIFTEEN:
Install any themes or mods which are compatible with your ROM and set up your sounds and everything else you like to do and enjoy your android device to its fullest
I know I probably missed a couple things but will update when I remember.
VIVA LA ANDROID
EDIT: I had Fission 1.0 for some reason. I meant Fission 1.1. I'd also like to point out that Rubix 1.0 is the same exact thing as Fission but with more optimizations and tweaks. I ran them both but slightly prefer Fission 1.1
reserved...
Nice post!
Sent from my DROIDX using XDA App
Sleuth255 said:
Nice post!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Thanks a lot! That's all derived from months of obsessive learning along with trial and error
How dare you recommend Advanced Task Killer. You need to have your Android License revoke immediately.
Since we're talking about rooted phones and memory management, use Autokiller. It does what android already does natively, only better.
Nice write up, but do yourself a favor and get rid of ATK!
LexusBrian400 said:
How dare you recommend Advanced Task Killer. You need to have your Android License revoke immediately.
Since we're talking about rooted phones and memory management, use Autokiller. It does what android already does natively, only better.
Nice write up, but do yourself a favor and get rid of ATK!
Click to expand...
Click to collapse
Please don't get caught up on the ATK thing. I don't want this thread turning into a pro or con ATK. One will however say that ATK without AUTOSTARTS is pointless. Due to AUTOSTARTS, ATK is once again relevant and really beneficial.
If the app AUTOSTARTS or anything like it wasn't available, I wouldn't tell anyone to install ATK. With my setup, any app we kill with ATK will not be automatically restarting thus wasted battery. That was the biggest issue with ATK before AUTOSTARTS was available. Now, anything we kill are only apps we ourselves initiated.
Apps left running do still use CPU resources. The latest privacy study of Androids apps show that 50% or so of the tested apps sent private information to advertisers in the background.
When the Android system only has like ~40mb of free system RAM available, the system will no matter what bog down somewhat. We can get rid of this from ever happening.
Just put the little green ATK widget on your main homescreen and one tap and your done. The ATK widget takes the same amount of space as an icon. It is simple and easy.
Doing it like this ensure at no point EVER is the Android system going to lag.
Sleuth255 said:
Nice post!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Well was I happy seeing those post when did you get a Droid X.
-McMex
A few weeks ago. Excellent device too. I'm confident that the locked BL will be defeated. I'm running through some of luv2increase's mods now... I like the idea of being able to defeat autostart and place strict control over the apps I allow to run.
Sleuth255 said:
A few weeks ago. Excellent device too. I'm confident that the locked BL will be defeated. I'm running through some of luv2increase's mods now... I like the idea of being able to defeat autostart and place strict control over the apps I allow to run.
Click to expand...
Click to collapse
Yes it is an excellent device just today I posted on Twitter I have all the high end Android phones and the Motorola implementation of the Droid X is by far the best nice polish too. I been playing a lot with SetCpu profiles (removing bloatware via adb) and power saving settings and can get over 18 hours of heavy usage. Just starting to try these other ROMs out. As always if you need a tester or I can help you with something let me know I have been on Android a while now and have a lot of experience and a ton of apps.
A lot of you guys have no idea the asset that Sleuth is having a Droid X.
-McMex
Alot of great tips in the OP. I actually run with almost this exact setup. I am using Rubix 1.0, though. Great rom. These tips will help tremendously with performance and battery life. Thanks for passing this along.
I am running auto nooter on my nc (lovin it) but i have noticed that the available memory is slowly leaking. On reboot, i usually have around 300 available and that number slowly but surely decreases until its so low that it reboots automatically.
I have advanced task killer installed and periodically kill all the tasks to make sure nothing is running in the background.
Any idea what might be causing this?
Advanced Task Killer is not helping you. Google has come right out and said Task Killers will do more harm than good on your Android device. Here is a good read:
http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
The fact that you can see an application's process "running" does not mean the application is running or doing anything. It may simply be there because Android needed it at some point, and has decided that it would be best to keep it around in case it needs it again.
...
Once Android determines that it needs to remove a process, it does this brutally, simply force-killing it. The kernel can then immediately reclaim all resources needed by the process, without relying on that application being well written and responsive to a polite request to exit. Allowing the kernel to immediately reclaim application resources makes it a lot easier to avoid serious out of memory situations.
Click to expand...
Click to collapse
czarjohn said:
I am running auto nooter on my nc (lovin it) but i have noticed that the available memory is slowly leaking. On reboot, i usually have around 300 available and that number slowly but surely decreases until its so low that it reboots automatically.
I have advanced task killer installed and periodically kill all the tasks to make sure nothing is running in the background.
Any idea what might be causing this?
Click to expand...
Click to collapse
It will not reboot when it runs out of ram. My suspicion is you're seeing the 'random reboot' problem that happens on the stock B&N ROM. See here for a workaround: http://nookdevs.com/NookColor_Issues
mrapollinax said:
Advanced Task Killer is not helping you. Google has come right out and said Task Killers will do more harm than good on your Android device. Here is a good read:
Click to expand...
Click to collapse
I totally agree with this on 2.2 upwards... Unfortunately 2.1 is a little more lax about memory handling, and can sometimes get quite slow and jumpy and can benefit from a flush. I use System Panel and exclude all of my important tasks and widget, and if I see my NC getting jumpy or such, I'll kill all (which excludes those already excluded apps of course). But auto task killers are always a bad idea.
mrapollinax said:
Advanced Task Killer is not helping you. Google has come right out and said Task Killers will do more harm than good on your Android device. Here is a good read:
http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
Click to expand...
Click to collapse
Thanks for the post, that was a great read and I am uninstalling my task killer now.
Mike
Regarding task killing, I recommend something like Watchdog to monitor apps as opposed to an auto-task killer. Watchdog has a really nice widget for monitoring system resources and in the rare occasion that an app starts misbehaving, it will give you a notification and the option to kill it. Otherwise letting the OS handle things itself is the best option. I've been using computers for a very long time and idea of leaving apps running seems counter-intuitive, but in my experience there is no reason to not trust what Google says about the issue.
czarjohn said:
I am running auto nooter on my nc (lovin it) but i have noticed that the available memory is slowly leaking. On reboot, i usually have around 300 available and that number slowly but surely decreases until its so low that it reboots automatically.
I have advanced task killer installed and periodically kill all the tasks to make sure nothing is running in the background.
Any idea what might be causing this?
Click to expand...
Click to collapse
i am also having these problems but im on honeycomb
i dont have any task killer installed but i installed one last week to check if my memory was leaking or if the rom was just rebooting
Great stuff here. Thanks for all the info. I think it was the random reboot since it did seem to happen most often when i was putting the nc in to standby.
Lots of good stuff here. Gonna miss the little green widget on my home screen, but i guess google knows best...
czarjohn said:
Great stuff here. Thanks for all the info. I think it was the random reboot since it did seem to happen most often when i was putting the nc in to standby.
Lots of good stuff here. Gonna miss the little green widget on my home screen, but i guess google knows best...
Click to expand...
Click to collapse
well i installed honeycomb preview v2 on my eemc from samuallhaff and it seems to remove this problem
i suggest you switch to his rom if you want the memory leaks to stop
luigi90210 said:
well i installed honeycomb preview v2 on my eemc from samuallhaff and it seems to remove this problem
i suggest you switch to his rom if you want the memory leaks to stop
Click to expand...
Click to collapse
Don't confuse "memory leaks" with "weird wifi sleep reboot bug".