Related
I just flash a OC kernel to my sprint* hero. I am running Fresh 2.4 with the 710 OC kernel (chose 710 thinking it will be more stable, yes/no?). Before flashing this Kernel I was using AutoKiller on Optimum mode to help keep the phone in line. I am wondering now if AutoKiller is conflicting with my OC'ing of the phone. Should I uninstall the AutoKiller, or maybe change the mode to Chuck Norris? I just dont want the phone to act like a PC does with 2 anti-virus programs installed on it!
thanks
IN my opinion no one should have an autokiller app on there phone. The Android OS kills apps when it needs the space for another app. If it helps i use a program called FAST REBOOT that works pretty good. when the phone starts feeling sluggish i just fast reboot and it makes it run better.
on a side note....this is a Question and it belongs in the Q&A section not here in development.
Thanks for the input. I will try without it and check out Fast Boot!
Mods Please move thread to Q and A
t12icky0 said:
IN my opinion no one should have an autokiller app on there phone. The Android OS kills apps when it needs the space for another app. If it helps i use a program called FAST REBOOT that works pretty good. when the phone starts feeling sluggish i just fast reboot and it makes it run better.
on a side note....this is a Question and it belongs in the Q&A section not here in development.
Click to expand...
Click to collapse
The fact you called it "an autokiller app", as well as your explanation why you shouldn't have it, shows you really have no clue what AutoKiller is.
What you are referring to is a TASK killer, and I agree ... no one needs it because the internal memory manager does the same function much more fluidly and does not require an extra running process, hence is lighter on the system. AutoKiller (the actual app) simply allows you to customize the settings for that internal memory manager. This is pretty much necessary because the settings for this manager haven't changed at all since Android first debuted, and these settings basically leave you with around 25 MB remaining. That may be awesome for a G1, but for more powerful devices like our hero it is SLUGGISH, so upping the internal settings just performs the exact same function with more effective results for our devices.
To answer the original question, the only conflict that could exist is if the kernel itself has its own memory manager embedded. I've been on CM6 for some time, so I'm not sure if the kernel you chose has such a memory manager. If it does, however, it most likely has the same upgraded settings as you would hope to attain with AutoKiller. In this case, there is no need.
Hope this answers your question more completely.
tquetano said:
The fact you called it "an autokiller app", as well as your explanation why you shouldn't have it, shows you really have no clue what AutoKiller is.
What you are referring to is a TASK killer, and I agree ... no one needs it because the internal memory manager does the same function much more fluidly and does not require an extra running process, hence is lighter on the system. AutoKiller (the actual app) simply allows you to customize the settings for that internal memory manager. This is pretty much necessary because the settings for this manager haven't changed at all since Android first debuted, and these settings basically leave you with around 25 MB remaining. That may be awesome for a G1, but for more powerful devices like our hero it is SLUGGISH, so upping the internal settings just performs the exact same function with more effective results for our devices.
To answer the original question, the only conflict that could exist is if the kernel itself has its own memory manager embedded. I've been on CM6 for some time, so I'm not sure if the kernel you chose has such a memory manager. If it does, however, it most likely has the same upgraded settings as you would hope to attain with AutoKiller. In this case, there is no need.
Hope this answers your question more completely.
Click to expand...
Click to collapse
It does, Thanks! I do have the Advanced Task Killer (everyone has or had at one point! lol) and will lose that app right away! With the advanced task killer I still drop in free memory, so it doesnt seem to be doing anything, or what I want it to do. Just kills a few apps, like you said android will do that on it own. The Kernel I have is Darchstars Kernel vUV2 710mhz for roms using 2.1 RUU. It states in big letters "BUGS IN zIMAGE FREEMEMKILLER" just wondering if the AutoKiller has the same issues as the FreeMeKiller? My memory will drop to 50 right now, that is with autokiller set to optimum, I want to raise it higher to keep more free memory, didnt want a conflict though.
cordell12 said:
It does, Thanks! I do have the Advanced Task Killer (everyone has or had at one point! lol) and will lose that app right away! With the advanced task killer I still drop in free memory, so it doesnt seem to be doing anything, or what I want it to do. Just kills a few apps, like you said android will do that on it own. The Kernel I have is Darchstars Kernel vUV2 710mhz for roms using 2.1 RUU. It states in big letters "BUGS IN zIMAGE FREEMEMKILLER" just wondering if the AutoKiller has the same issues as the FreeMeKiller? My memory will drop to 50 right now, that is with autokiller set to optimum, I want to raise it higher to keep more free memory, didnt want a conflict though.
Click to expand...
Click to collapse
If you are using a kernel made for 2.1, you should not be using it. CyanogenMod 6 is built on Android 2.2, so either use the stock kernel or UncappedKernel from Decad3nce. Second, having the processor clocked at 710Mhz will NOT make the phone more stable. If anything, it will become unstable because of the added heat and power needed to run the processor. A good overclock that I've found that should be stable on our phones is from 650-690Mhz. Although I've been running my phone at 590Mhz, and I haven't found any real-life difference in the speeds. Like said above, tweaking the minfree (the Android internal task killer) is perfectly fine. What you do NOT want to do is use a program like Task Killer or Advanced Task Killer, since those will both end unnecessary processes, which will then have to be restarted, in effect using more battery and CPU cycles. So the best way, if you want, is to tweak the minfree settings with a program like Autokiller.
mrinehart93 said:
If you are using a kernel made for 2.1, you should not be using it. CyanogenMod 6 is built on Android 2.2, so either use the stock kernel or UncappedKernel from Decad3nce. Second, having the processor clocked at 710Mhz will NOT make the phone more stable. If anything, it will become unstable because of the added heat and power needed to run the processor. A good overclock that I've found that should be stable on our phones is from 650-690Mhz. Although I've been running my phone at 590Mhz, and I haven't found any real-life difference in the speeds. Like said above, tweaking the minfree (the Android internal task killer) is perfectly fine. What you do NOT want to do is use a program like Task Killer or Advanced Task Killer, since those will both end unnecessary processes, which will then have to be restarted, in effect using more battery and CPU cycles. So the best way, if you want, is to tweak the minfree settings with a program like Autokiller.
Click to expand...
Click to collapse
I am using Fresh 2.4, not CyanogenMod 6. I think there is a lower OC than what I am using. I will have to check, I knew the 768 would be way to much so I chose the 710 (middle option), so yes there is a lower OC. I have uninstalled the advanced task killer, it seems to be doing fine with AutoKiller set to "Strict" that keeps my memory around 60, before it would drop to low 40s I am new to all this so trial and error on my part will help me find a happy medium. I am getting a lot of help here and at android forums, thats how I found this site My wife has the same phone and is jealous of my speed but is scared to let me flash a rom to hers. She watched me stressing out when I was getting stuck in boot loops! I kept trying to partition my SD card to get apps2sd working, every time I after my partition I would get stuck in a dang boot loop. Seems after I partition the SD I need to re-flash my rom in order to get Fresh to see the partition. Or I think thats the issue? As of now I dont have a class 6 SD card, just found out I will need one so I am gonna wait for the apps2sd thing.
thanks
691 is the lowest Kernel, so either 691, 710, or 768. Will the 691 make that much of a difference than the 710? Stock is 528 I think
tquetano said:
The fact you called it "an autokiller app", as well as your explanation why you shouldn't have it, shows you really have no clue what AutoKiller is.
What you are referring to is a TASK killer, and I agree ... no one needs it because the internal memory manager does the same function much more fluidly and does not require an extra running process, hence is lighter on the system. AutoKiller (the actual app) simply allows you to customize the settings for that internal memory manager. This is pretty much necessary because the settings for this manager haven't changed at all since Android first debuted, and these settings basically leave you with around 25 MB remaining. That may be awesome for a G1, but for more powerful devices like our hero it is SLUGGISH, so upping the internal settings just performs the exact same function with more effective results for our devices.
To answer the original question, the only conflict that could exist is if the kernel itself has its own memory manager embedded. I've been on CM6 for some time, so I'm not sure if the kernel you chose has such a memory manager. If it does, however, it most likely has the same upgraded settings as you would hope to attain with AutoKiller. In this case, there is no need.
Hope this answers your question more completely.
Click to expand...
Click to collapse
yea my bad..lol. i had a brain fart. thought it said task killer.
cordell12 said:
I am using Fresh 2.4, not CyanogenMod 6. I think there is a lower OC than what I am using. I will have to check, I knew the 768 would be way to much so I chose the 710 (middle option), so yes there is a lower OC. I have uninstalled the advanced task killer, it seems to be doing fine with AutoKiller set to "Strict" that keeps my memory around 60, before it would drop to low 40s I am new to all this so trial and error on my part will help me find a happy medium. I am getting a lot of help here and at android forums, thats how I found this site My wife has the same phone and is jealous of my speed but is scared to let me flash a rom to hers. She watched me stressing out when I was getting stuck in boot loops! I kept trying to partition my SD card to get apps2sd working, every time I after my partition I would get stuck in a dang boot loop. Seems after I partition the SD I need to re-flash my rom in order to get Fresh to see the partition. Or I think thats the issue? As of now I dont have a class 6 SD card, just found out I will need one so I am gonna wait for the apps2sd thing.
thanks
Click to expand...
Click to collapse
Like I said, I'm on CM6, but I run Aggressive with no problem. In reality, either Strict or Aggressive works well, but if you up it above that then it basically starts interpreting every application running in the background as an extraneous app and kills it aggressively whether you're using it or not. Also, because the system is constantly trying to increase the memory thats available to meet the thresholds, it is constantly working to close programs that aren't there, and then it becomes a bog on the system again. Long story short, stick to Strict and you should find that perfect balance and remain smooth.
Hello Guys...I'm new here and I hope that we can benefit greatly from each other.
Any way I have a Question and I hope you answer it for me.
I had a galaxy s and I noticed when I open the Android Assistant App (Task Manager, App Uninstaller..etc), I find lots of apps that are running without opening them. Resulting a decrease of my ram. Now I'm using an XPERIA X10 and my ram is 384mb approx. How Can I Prevent Those Apps From OPENING?
Most of them aren't actually running, they're just cached.
It happens so that if you want to run one of these, it doesn't have to be read from internal memory, and it'll load much faster. And they can be removed from memory without delay if you want to run something else.
There is no reason to remove them from memory just so you can have more. The only reason to do so would be if one of them is misbehaving and draining battery or making the phone lag.
I am running Froyo from Samsung web site.
Anyways, I know froyo was supposed to free up 512 ram. I know about 100 goes to gpu. However my phone is left with 339 ram to use (as seen in task manager). However it is always using at least 220mb, even when I close everything and restart the phone. When I open up advanced task killer it says 116m free. Why so little? How can I get more easily? without having to use ROMs or kernels?
Or is this how it is for everyone? I feel kind of cheated!
First of all, you should never need to use anything like Advanced Task Killer now that you have froyo. There are legitimate uses, but its really something you can go without. See http://www.reddit.com/r/Android/comments/cwovf/in_light_of_all_the_discussions_right_now_about/ for a good writeup.
Your phone, just like a computer, uses an optimal amount of RAM at all times. That does not mean minimal. Android phones dynamically allocate RAM for applications and the OS. Why have 200MB of RAM free when you can instead have 100MB free and have the phone be more responsive? 2.2+ manages memory more effectively, and if you are not using an application, will close it. Its fairly difficult with any normal usage scenario to cause your phone to run out of memory.
In short, you don't really need to worry about it because its that way on all Android devices (and generally any modern computing device), and that if is not affecting the usability then its not an issue
Completely agree With first comment. Everyone is concerned about keeping as much ram free as they can but it does not speed their phone up at all. Ram its just like quadrant scores a useless numbers if the phone is response and speedy in actual use
Sent from my SAMSUNG-SGH-I897 using XDA App
U could try reading this: Android Memory Management
your ram usage does seem a little high, you may have an app that is using a lot of it. the 339mb available is normal. some kernels will show quite a bit lower than that but the never seeing more than 116 free is odd. the rom im curently on fluctuates from about 140mb used to 240mb used. i only know that because i clear ram before running benchmarks, have you tried clearing ram in the built in taskmanager? or are you only going off the task killer? because the task killer doesnt necessarily clear ram.
all i know is task killers are pretty useless unless you have an app that freezes and for that the taskmanager built in to many of the samsung roms should be enough for that though it does not show every process that is in a saved state or system processes. task killer programs do more harm than good but i cant seem to get people off them. danm verizon store sets people up with them and poeple use them religiously. i figured out in the first few days of using android on my aria that getting better speed and battery life by killing tasts was a futile effort. there are few market apps that use resorces when running in the background and if you exit the app with the back button it doesnt save the state or run in the background. not that saved state is a problem. i only found that the phone uses more battery restarting processes that are designed to be running and has more lag than when you just use the phone and ignore the running processes.
Personally the only time you should be ever worried about ram is when watching a flash video or viewing a webpage with a lot of stuff. Other than that, as said, if the phone runs smooth, who cares about ram?
Whats best way to free up the more ram? I have root and froze the safe stuff. The lowest I can get free is about 185MB / 328MB.
Rooting and freezing apps doesn't give you more RAM, since there is only 512MB of RAM and the OS takes part of that to run.
You can free up internal app storage space, by deleting bloatware, or cut/paste the bloatware into a folder on the SDcard (I call mine VZWBloat) and that will save you space.
You can run a task killer to kill off apps that you don't need but you have to be careful, Android does need certain apps to be available in the background and it will just reopen automatically and that will put them into a cycle and drain the battery.
rcb929 said:
Whats best way to free up the more ram? I have root and froze the safe stuff. The lowest I can get free is about 185MB / 328MB.
Click to expand...
Click to collapse
Please do not post Questions or problems in Android Development
Moving to General
RaptorMD said:
Rooting and freezing apps doesn't give you more RAM, since there is only 512MB of RAM and the OS takes part of that to run.
You can free up internal app storage space, by deleting bloatware, or cut/paste the bloatware into a folder on the SDcard (I call mine VZWBloat) and that will save you space.
You can run a task killer to kill off apps that you don't need but you have to be careful, Android does need certain apps to be available in the background and it will just reopen automatically and that will put them into a cycle and drain the battery.
Click to expand...
Click to collapse
Hey im using root explorer when im in system/app/ how do i single out the bloatware apps?
rcb929 said:
Whats best way to free up the more ram? I have root and froze the safe stuff. The lowest I can get free is about 185MB / 328MB.
Click to expand...
Click to collapse
Freeing up that much RAM is probably detrimental to the overall efficacy of the memory management system, I've never seen mine at 185MB, and if I did I'd worry something was wrong.
If you really want to free up more RAM, for no benefit whatsoever, use something like Advanced Task Killer and set it to allow killing of the lowest level processes it can, then kill everything. Bam, tons of free'd up RAM. Again, this has pretty much no benefit whatsoever and for a short time will probably make your phone more sluggish and slow.
In Android (Linux) free memory is considered wasted memory.
That said, I remember on my galaxy S that the phone ran snappier when I tweaked the memory management of the phone.
Task killers are generally considered a bad idea on android, so I would avoid using one of them to free up memory. However, there is a poorly named app called auto killer that is actually just an interface to tweaking androids built and memory management. I recommend giving it a try, here's a link: http://market.android.com/details?id=com.rs.autokiller
Note that it is not a task killer per se, it is just a tweak for android phone memory management schemes.
I haven't used it on my droid charge yet, but play with the settings maybe starting with aggressive. Good luck and let us know how it works for you.
Sent from Thunderbolt
I don't have my phone with me right now, but you need to make the folder read/write and then hit menu and multi-select or select multiple. This thread http://forum.xda-developers.com/showthread.php?t=1082588 shows what is ok to freeze, but I am not familiar enough with those to say you can remove all of them. Typically I would look for the Verizon specific apps, games like lets gold, guitar hero etc. If you remove anything related to touch wiz (widgets) you need to remove both of the associated files. I am pulling this from memory on my previous TB.
These are the ones I recognize, but the others in that long list I would like to see better clarification of what they are and how they are tied into the TouchWiz UI so we don't get errors. Please exercise caution when doing this.
• Bitbop 1.0
• Blockbuster 0.6
• City ID 1.1.4
• Lets Golf 2 3.2.2
• Rhapsody 1.0
• Rock Band 4.4.3
• Slacker 2.1.170
• TuneWiki 2.2
• VCAST Media Manager 4.2.96.3
• VVMService 1.0.30
• VZ Navigator 7.1.2.87
• WeatherBug Clock 11.04.07.01
rcb929 said:
Whats best way to free up the more ram? I have root and froze the safe stuff. The lowest I can get free is about 185MB / 328MB.
Click to expand...
Click to collapse
BY FAR.... BAR NONE.... The best way to free up memory and keep it free without messing with task killers is to use a program called startup auditor. This app prevents apps from starting up automatically on startup and throughtout the day without interfering with normal app processes. You can shut down or enable any app you want.
Even cooler, if you select the option menu and hit disable all, it only disables programs that won't interfere with the phone operation so it knows which apk's are critical for phone integrity. PRETTY COOL!!!
burningembers said:
Freeing up that much RAM is probably detrimental to the overall efficacy of the memory management system, I've never seen mine at 185MB, and if I did I'd worry something was wrong.
If you really want to free up more RAM, for no benefit whatsoever, use something like Advanced Task Killer and set it to allow killing of the lowest level processes it can, then kill everything. Bam, tons of free'd up RAM. Again, this has pretty much no benefit whatsoever and for a short time will probably make your phone more sluggish and slow.
Click to expand...
Click to collapse
NEVER USE ADVANCE TASK KILLER... See other post
http://forum.xda-developers.com/showthread.php?t=1106265
RaptorMD said:
Rooting and freezing apps doesn't give you more RAM, since there is only 512MB of RAM and the OS takes part of that to run.
You can free up internal app storage space, by deleting bloatware, or cut/paste the bloatware into a folder on the SDcard (I call mine VZWBloat) and that will save you space.
You can run a task killer to kill off apps that you don't need but you have to be careful, Android does need certain apps to be available in the background and it will just reopen automatically and that will put them into a cycle and drain the battery.
Click to expand...
Click to collapse
DON"T USE A TASK KILLER ON ANY SAMSUNG DEVICE. See other post
http://forum.xda-developers.com/showthread.php?t=1106265
I wasn't really condoning the use of task killers. I disagree with them 99% of the time (there are some edge cases). I just gave the OP an option if he really, really wanted to for no reason whatsoever.
@OP: I would recommend leaving the pasture gate open.
rcb929 said:
Whats best way to free up the more ram? I have root and froze the safe stuff. The lowest I can get free is about 185MB / 328MB.
Click to expand...
Click to collapse
There is an app called Greenify. Its available on Play store.
Just check it out.
It also helps to maintain the juice of the battery.. !!
To Free Ram
A more easy way to delete a minimum of 1gb of space which by doing so also frees up ram is to delete the dump state log cat. See every time your device has an error or force close issue, date is collected / written to the log file and this can take up ane enormous amount of space which when space is low also means your device user more ram. To do this go to your dial pad and type in *#9900#
This will automatically brings up options and then just choose to delete the dump state/log cat. Let it clear for a few minutes and that's it's. Try seeing how much space you have before and after and you'll realise this is a blessing.
Hello everyone, I have my nexus for a month now running NSCollab, pretty much everything is working right with it except one thing that is driving me mad. It autocloses background apps all the time.
For example, I have my manga reader(Mango), a file manager and eBuddy running normally with plenty of RAM available. If I try to run the browser it usually closes everything.
Is there any way to make multitasking work as it is supposed to work?
Get more RAM or set a less aggressive RAM management (lower min ram before clearing)(dunno how, but it's possible).