So do you guys use it and what does it exactly do? And also what does 3g turbocharger and kick ass kernel tweak do?
Basically everytime the memory drops below the thresholds set by v6, the system will start killing of apps running in the background which frees up memory that you most probably aren't using, Im currently on the aggressive settings so everytime my memory drops below 150mb the system starts killing apps. Its basically just tweaking the internal task killer to be slightly more aggressive. It also locks the launcher so the system cannot kill it if the memory drops too low.
The 3g tweaks, I think adjust or add some settings to the build.prop which supposedly make it faster although I haven't noticed much difference with that and the kernel tweaks I'm not too sure where the changes are made but again I don't see a great change from it. Definitely recommend v6 supercharger though.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
Basically everytime the memory drops below the thresholds set by v6, the system will start killing of apps running in the background which frees up memory that you most probably aren't using, Im currently on the aggressive settings so everytime my memory drops below 150mb the system starts killing apps.
Click to expand...
Click to collapse
Great. Let's take 150MiB of RAM and then don't do anything useful with it. Processes aren't supposed to be killed unless you actually run out of memory.
Scratch0805 said:
It also locks the launcher so the system cannot kill it if the memory drops too low.
Click to expand...
Click to collapse
That seems innocent, but it won't help you if the launcher has a memory leak. If the launcher kept getting killed, it was telling you that your low memory thresholds are too high. Under normal circumstances, the launcher won't get killed. But if it grows too much, it'll get killed and the OS won't crash.
When you force close an application through the application manager, it shows you a warning. There's a reason for that (exactly what it says). And since Android 2.2, the framework can take care of itself just fine. No need for any 3rd party task killers.
Lol..... Thought you'd have something to say on it, actually mate the way my phone is usually setup there is nothing running in the background to kill anyway, thanks to autostarts I only have apps running that I need and make sure that I close things properly after use, so it really doesn't matter which settings I use whether they be low such as 30mb before it starts killing the first lot of empty apps or high such as 150mb as my setup rarely drops below because there is only the bare minimum running in the first place.
Sent from my HTC Wildfire using xda premium
Allright, it's not that RAM would slowly wear and tear by using it but at least you're not buying that it's better for performance. And I just wonder how these apps are made, as a thought experiment to figure out the mindset of whoever wrote this task killer.
...So let's make an app which looks real cool and doesn't do anything useful in particular! Wait, no one would download that! Hmm... Oh, I know! Let's call it "V6 Supercharger"! Yeah, that sounds awesome! Now people will download it for sure! It's the coolest thing since sliced bread!
It's the same with those programs like "Registry Booster". How did that happen? Someone must've woke up one day, turned on his PC, started poking in the registry, saw lots of keys which aren't really strictly necessary but are there anyway and thought like "Hmm, what if I made a program which removes all these unneeded keys? MS-Windows would be ZOMG faster!!111eleventyone". Then made it look real slick with a custom skin and a speedometer showing progress and say at the end that the registry has been "boosted". And since this guy is such a nice fellow, he threw in some extra free toolbars into the mix as well. Users always appreciate having more toolbars to click on and agreements to ignore.
Ok, I'll stop ranting now. Enjoy your week
Try explaining that to the dev who created it here. Honestly, it would be better, because, I am pretty sure most members here are not as technically inclined as you.:
http://forum.xda-developers.com/showthread.php?t=991276
You're just setting him up so I can tear him apart... aren't you?
The poor bastard doesn't even know what it is... he thinks it's a task killer app... heh
No, I would like him to discuss all the technical aspects with you. Because, clearly, he's wasting his effort as a developer here educating non-technical people like me, and the majority here on the Wildfire Forums.
And before you accuse me of trying to set people up, I can assure you I have nothing against you / your script or anything. Rather, I have used your script, and came away impressed with it.
I know you you weren't doing anything like that... I'm always putting down these clowns that think that suffocating the phone is good... idiots lol
Like I say, what the hell good is phone if you can't make a call because of some crap hogging the ram?
Besides, I doubt very much he has any technical skills at all... like I said before, he doesn't even know what it is so he's not very techinical
dud3me said:
what does it exactly do?
Click to expand...
Click to collapse
It makes you feel good.
And I definitely noticed a 0.00001ms speed difference when opening apps.
Another liar
zeppelinrox said:
Another liar
Click to expand...
Click to collapse
Yeah lol. Most people in this forum are wannabe developers who know **** about developing but they like to act like they do. Apart from few people who actually know stuff and the others like me who acknowledge the fact that we don't know anything
Fact is, those who know they don't know learn more than those that think they know it all
Less than a year ago, I knew 0 about android.
And when I started the supercharger script, I knew nothing about linux scripting.
Just started off with a few commands and everytime I wanted to try something new or add something... I googled it up.
And I'm still figuring it out.
For example, I set my 256mb device to have 25mb free with the number I use in slot 3.
So whatever memory tool I use will show I have 25 or 30mb free... great - that's what I want
But when I was doing up the recent update and enhanced the Fast Engine Flush, I wanted to show before and after using the "free" command.
To my surprise, system tuner shows that I have 30mb free while the free command shows I have only 5mb free!
So what's that mean? Why that difference of 25mb?
It means that all that "free ram" is actually being used for cache.
And it's giving me speed
So to those that think it's great to have ram clogged with apps when the system is starving for space to use for cache...
BOOYA!
Really have trouble using your scripts and I think after enabling 3gturbotweak thing my 2g data isn't working haven't tried 3g.
I can't recall it affecting 2g... so I assume 2g used to work (I don't get 2g - it's unavailable)
But if you unturbocharge, the 2g/3g goes back to normal, no?
zeppelinrox said:
I can't recall it affecting 2g... so I assume 2g used to work (I don't get 2g - it's unavailable)
But if you unturbocharge, the 2g/3g goes back to normal, no?
Click to expand...
Click to collapse
Well I had to format system data and cache and wiped everything and now it's working again so I'm not completely sure if it was the turbocharge thing.
The idea that you can magically "supercharge" your OS by freeing up memory is fundamentally flawed.
what the hell good is phone if you can't make a call because of some crap hogging the ram
Click to expand...
Click to collapse
If this is really a problem on your phone, you're doing it wrong. I haven't done anything to free up ram and the amount of ram available on my wildfire is currently 108,48MiB. I start 10 random apps, Angry Birds, and Angry Birds Rio. 40,68MiB still free. I start Angry Birds Seasons and end up with 49,66MiB free and 9 apps died, including the first angry birds. Running out of ram is in general not a failure mode of Android and at no point was I unable to place a call. I close the 2 remaining open instances of Angry Birds the normal back-button way, 147,68MiB free.
I'm always putting down these clowns that think that suffocating the phone is good... idiots lol
Click to expand...
Click to collapse
I just wanted to quote that.
And when I started the supercharger script, I knew nothing about linux scripting.
Just started off with a few commands and everytime I wanted to try something new or add something... I googled it up.
Click to expand...
Click to collapse
That's exactly the impression I had. Now take it from someone who has run Linux both embedded and on his desktop for the past 12 years. Your app doesn't improve anything, and I'd be glad to be proven wrong because you would've actually made a discovery we can use to improve Android and Linux with. From your post I understand it you change vm kernel parameters such that the oom killer is invoked sooner. This is actually detrimental to the stability of the OS, the oom killer is only meant to be invoked as a _last_resort_. The Android framework has its own means to free up memory, including calling onLowMemory in any application and doing a gc run. This does not cause instability and is completely transparent to the user. I've only ever had to manually kill applications in a broken state and others for debugging purposes, which is why the Force Close button exists.
It means that all that "free ram" is actually being used for cache.
And it's giving me speed
Click to expand...
Click to collapse
If the output looks anything like this:
Code:
total used free shared buffers cached
Mem: 3456 3325 131 0 10 93
-/+ buffers/cache: 3221 235
Then you've just never bothered to look. You can clearly see in the second line it makes a calculation for you which is exactly what it says in the leftmost column. And of course completely disregard the fact that cached pages are invalidated on a write (marked dirty) and reads from an mtd are really fast already anyway.
So to those that think it's great to have ram clogged with apps when the system is starving for space to use for cache
Click to expand...
Click to collapse
This is not how it works! For starters, ram cannot be "clogged". A drain pipe can be clogged but ram is made of digital circuitry, not plumbing. And second, there is no resource starvation in the page cache. It's just an old optimisation to keep data pages in memory for longer to serve repeated reads and give them back whenever they're needed for something else. More apps in ram can actually mean less reads are necessary because the data is already there (especially if you tend to switch between recent apps). Since Android 3.0, application developers are encouraged to use Loaders which cause filesystem I/O to be performed on a background thread. And applications which actually use the available ram always trump applications designed to use as little ram possible in performance. Between a collection of loaded objects and a cached filesystem, the collection always wins. You have 256 to 512 MiB of RAM in a typical Android device. The average application is 18 to 30 MiB. It can manage. Especially when you consider the fact that the UI only shows 1 task at a time and pressing the back button usually destroys the activity you were in. The gc takes care of its remains.
Now here's something which will actually improve write speeds on /data: Open up settings, applications, manage applications. Sort by size. Remove the biggest apps you don't need and move the rest to SD if you can (you can use "pm setInstallLocation 2" as root to move non-froyo-aware apps to SD). I've been using the market a lot lately so I just removed aDosBox, Albert Heijn, PocketCloud, Pulse and moved Dolphin Browser to SD which meant 47.25MiB free on /data. On a 175MiB partition, 30% of it is about 52MiB so I'd try to keep the available space around 50MiB. If your phone is low on storage, doing this will perceivably improve performance.
dud3me said:
Well I had to format system data and cache and wiped everything and now it's working again so I'm not completely sure if it was the turbocharge thing.
Click to expand...
Click to collapse
Same thing happened to me, but every time i turned 3g on the phone rebooted and i got stuck in a bootloop, i had to use the ruu update to restore phone.
I would stay away from the network tweaks. It doesnt improve speed anyway.
Sent from my HTC Wildfire using xda premium
henkdv said:
The idea that you can magically "supercharge" your OS by freeing up memory is fundamentally flawed.If this is really a problem on your phone, you're doing it wrong. I haven't done anything to free up ram and the amount of ram available on my wildfire is currently 108,48MiB. I start 10 random apps, Angry Birds, and Angry Birds Rio. 40,68MiB still free. I start Angry Birds Seasons and end up with 49,66MiB free and 9 apps died, including the first angry birds. Running out of ram is in general not a failure mode of Android and at no point was I unable to place a call. I close the 2 remaining open instances of Angry Birds the normal back-button way, 147,68MiB free.
Click to expand...
Click to collapse
All that you said is very informative.
What are your minfrees?
Set them to something like 6, 12, 16, 18, 26, 30.
Run a bunch of apps...
See how great it runs then
Fact of the matter is, user's with 1GB ram devices notice a real improvement.
Not placebo.
Pressing the home or back button has an instant effect without hesitation - which indeed happens on stock roms.
Yes in theory I'm sure it all makes sense and I apologize for using layman's terms such as "clogging".
An android phone is not a Linux PC so I believe it's not a great idea to configure it like it is a Linux PC.
They have difference purposes.
Anyway, in theory, a bumble bee can't fly - but it does.
Related
Trying to figure out what's a problem and what's not. Advanced Task Manager....says 18 apps are open. Is that fibbing?
ok so not 18...10.
Voice search, gallery, maps, car home, clock, settings, gmail, voice dialer, weatherbug, mp3 store....the G1 never had that many going at once in memory.
and the phone still zips around im hoping?
it does give very small lag when they are all running, then when i kill them all it speeds up. i actually recorded a video of the whole process.
Mine has 31 currently running?!?! WTF??? Some are running twice like AK Notepad and The Weather Channel? I'm thinking 2.1 is having issues managing applications. I keep hitting my end all widget and it's always like 20+ apps running. So much for the extra ram, things just keep restarting for now reason!
EDIT: After more playing around, it looks like the Back button does not close applications like it does on the G1 and MT3G. Great, better get used to using the Task Manager Widget or nothing will close!!!
setzer715 said:
Mine has 31 currently running?!?! WTF??? Some are running twice like AK Notepad and The Weather Channel? I'm thinking 2.1 is having issues managing applications. I keep hitting my end all widget and it's always like 20+ apps running. So much for the extra ram, things just keep restarting for now reason!
EDIT: After more playing around, it looks like the Back button does not close applications like it does on the G1 and MT3G. Great, better get used to using the Task Manager Widget or nothing will close!!!
Click to expand...
Click to collapse
Do we *really* need to kill apps though? We have ample memory to cope, right?
Either that or Advanced Task Manager is giving a false report...I don't know which. But yeah the back button doesn't seem to exit the app.
I'm waiting for this video to finish rendering and I'll post it up on Vimeo. It clearly shows the phone lagging, then speeding back up when they are all killed.
spr33 said:
Do we *really* need to kill apps though? We have ample memory to cope, right?
Click to expand...
Click to collapse
I don't think they all need to be running at once though, no matter how much memory we have. I don't want it running unless I open it, with the exception of the few that have to run if your using widgets.
spr33 said:
Do we *really* need to kill apps though? We have ample memory to cope, right?
Click to expand...
Click to collapse
According to Task Manager before I started launching apps I had 109Mb avail mem. After launching and backing out of a bunch I was down to 49Mb. That was withing 5min. Can you imagine a full day of not ending apps?
I just emailed the developer to rule out a false report with his app and Android 2.1.
setzer715 said:
According to Task Manager before I started launching apps I had 109Mb avail mem. After launching and backing out of a bunch I was down to 49Mb. That was withing 5min. Can you imagine a full day of not ending apps?
Click to expand...
Click to collapse
Android manages that for you, it utilises the most amount of RAM possible. It'll end apps once it needs more RAM
efeltee said:
Android manages that for you, it utilises the most amount of RAM possible. It'll end apps once it needs more RAM
Click to expand...
Click to collapse
I never encountered this with my G1 though. It never ran that many apps at once.
OK video is here:
http://www.vimeo.com/8604778
Video mark 2:48 and go from there.
Some would probably call this "finicky" but I don't expect any lag on a $500 phone. I also understand that not everyone moves as fast as I do.
nphaskins said:
OK video is here:
http://www.vimeo.com/8604778
Video mark 2:48 and go from there.
Some would probably call this "finicky" but I don't expect any lag on a $500 phone. I also understand that not everyone moves as fast as I do.
Click to expand...
Click to collapse
Like has been said.. Android is managing this for you. Unused RAM is worthless RAM. this is the same issue people tried to ***** about with Windows Vista. The system is keeping the application in memory incase you switch back to it. If you do, you avoid the load times. If you don't keep applications in RAM then switching between them would take forever and pretty much negate the ability to multitask.
THIS IS BY DESIGN.
Nedlinin said:
Like has been said.. Android is managing this for you. Unused RAM is worthless RAM. this is the same issue people tried to ***** about with Windows Vista. The system is keeping the application in memory incase you switch back to it. If you do, you avoid the load times. If you don't keep applications in RAM then switching between them would take forever and pretty much negate the ability to multitask.
THIS IS BY DESIGN.
Click to expand...
Click to collapse
I'd like to think that we could have a civil and professional conversation without jumping in with your panties in a wad. Do you see my post count? Do you tink I was here when people we're complaining about this? Oh that's right we we're born with knowing how Android works that's right.
At any rate....I appreciate your response.
I think he got irritated you were jumping the gun a bit, you went even so far to post a video of it lagging..that kinda seems to lower the credibility of the device for people without that specific knowledge.
nphaskins said:
I'd like to think that we could have a civil and professional conversation without jumping in with your panties in a wad. Do you see my post count? Do you tink I was here when people we're complaining about this? Oh that's right we we're born with knowing how Android works that's right.
At any rate....I appreciate your response.
Click to expand...
Click to collapse
My apologies for seeming harsh. But, there is another thread on this exact same topic already in which this answer has already been stated :-/
If for some reason it really worries you, just use the Taskiller widget or something.. but, it really isn't anything to worry about. The slight second long pause in your video is simply from Android being notified it is low on memory and killing off a background process to make room for the one you are loading up. You shouldn't see it too often and the fact that it keeps the programs/apps in RAM is part of the reason the phone feels so snappy compared to a G1/MyTouch
hmmm, the only lag I saw in the video was the occasional having to press the touch sensitive buttons one more time?
Correct me if Im wrong?
Thing is: the more you use taskiller the slower it'll get unlike what everybody thinks...
Just leave the apps in the RAM and they'll load from the RAM (= instantly) otherwise they'll load from storage card (=milliseconds of delay)
All I can say from the video is that the Nexus is hugely fast. When you started the camera I thought "alright sit back & relax for 5sec like on most Androids" but this was insane!
nphaskins said:
I never encountered this with my G1 though. It never ran that many apps at once.
Click to expand...
Click to collapse
"It'll end more apps once it needs more ram".
The G1 had less rom and therefore had to end apps earlier because it needed to free up ram for the Os/new apps.
On the nexus one there is about 500 mb of ram. Whenever I put my phone on and I kill all my tasks, I only have 120 mb. This is not the biggest problem because after about 30 minutes of using the phone, no matter if I kill all the apps, the ram goes to 70mb - 79mb.
Android 2.2 should fix this.
Or you can use a custom ROM such as cyanogen, with which i have over 230MB free RAM after closing apps
There are already a million and now one threads on this subject, search and you shall find all you could ever care to know about the subject.
You should be using the RAM, not freeing it. The only way you lose battery is if the Application/Widget is downloading or using the CPU/GPU. On your PC, do you go to task manager and kill apps every time?
I know it's a hard habit to kick coming from a G1 where it seemed necessary. But on a Nexus, you really don't need to. The only times I have to use it are when an application hangs.
What the **** is up with everyone not wanting the memory in their phones/computers to be used? That is what it's for! If its not being used it is going to waste.
If you guys are using task managers you have failed.
lol chillout!
People are obviously fine with it and welcome not to moan on the internet to people about not being able to use it.
Install a custom ROM if you want to dry your tears about not being able to use the extra RAM.
mets3214 said:
On the nexus one there is about 500 mb of ram. Whenever I put my phone on and I kill all my tasks, I only have 120 mb. This is not the biggest problem because after about 30 minutes of using the phone, no matter if I kill all the apps, the ram goes to 70mb - 79mb.
Click to expand...
Click to collapse
Killing apps is 100% unnecessary on the Nexus One.
It actually wastes MORE power to kill apps and have them restart all the time, than it does to just leave them alone.
For the next week, uninstall all your task killer apps.
Then tell us how it went.
Ram goblins got to your ram, oh noes!
I'll answer his question. currently the nexus one only has half of the 512mb of RAM freed up, so you only have 256 mb right now. the next update is freeing up the other half.
RogerPodacter said:
I'll answer his question. currently the nexus one only has half of the 512mb of RAM freed up, so you only have 256 mb right now. the next update is freeing up the other half.
Click to expand...
Click to collapse
Sorry, you're right we didn't really directly answer his question I guess. But the point is, people shouldn't be looking at the free memory measurements anymore. Anything that isn't being used by applications will be used by the operating system for caching and other such things (this is a good thing). As soon as another applications starts up and needs that space, the kernel will give it up. Free memory doesn't use less power than memory that is in use by a sleeping process.
While you are correct that not all of the current memory of the device is addressable with the current kernel, when this limitation is removed in the next update (assuming it will be) it still wont solve the OP's problem. All it is going to mean is that even more memory will be taken up as cache space and buffers by the kernel and applications will be closed down even later so you'll still see a pretty small amount of "free" memory. If close to half of the RAM is going completely unused, then that's a lost opportunity by the kernel to cache or prefetch something.
Don't use task managers. They aren't needed and provide nothing. All they do is give fodder to the Steve Jobs' of the world that claim you need to manually micro manage memory on android devices as evidence by the number of people that use them.
Nerd rage much?
So just to clarify, apps don't really "run" in the background, they are just more readily available if they have ram dedicated to them? I'd rather not use a task manager but if it saves any of this pathetic battery I would sacrifice some performance...
DMaverick50 said:
So just to clarify, apps don't really "run" in the background, they are just more readily available if they have ram dedicated to them? I'd rather not use a task manager but if it saves any of this pathetic battery I would sacrifice some performance...
Click to expand...
Click to collapse
The only thing task managers do is kill your battery. If you find that your phone is sluggish , doesn't respond well etc, uninstall some bad apps. Some apps aren't coded very well and remain active all the time killing your battery. Having an app checking all the time if another app is killing your battery is also killing your battery.
Bottom line: Don't use a task killer unless you find it absolutely neccesary to keep your phone running at decent speed.
DMaverick50 said:
So just to clarify, apps don't really "run" in the background, they are just more readily available if they have ram dedicated to them? I'd rather not use a task manager but if it saves any of this pathetic battery I would sacrifice some performance...
Click to expand...
Click to collapse
Look at the link in my signature, it'll explain how the android system manages programs.
The task manger on this device is killing me!!! It gets so frustrating to have the browser killed every time I push the home button. Is there anyway to disable it? I would rather kill tasks on my own. My previous Android devices would let me run a lot more applications in the background before killing them. Maybe Verizon and Samsung have loaded this thing down to much.
andrewhair said:
The task manger on this device is killing me!!!
Click to expand...
Click to collapse
I agree... with the stock the minfree are IMO far to high that your launcher I use ADW often is killed the ro.APP_HOME_ADJ=0 did not help much...
What helps for me on a rooted device it to tweak
/sys/module/lowmemorykiller/parameters/minfree
If you have root you can do this easily by getting MinFreeManager on market by decreasing the values
I used EzyKernel v1 but went back on stock, nothing bad with this ROM but went back to stock to apply an update.
So I'm on stock + rooted and I can use MinFreeManager. Since I have no init.d script support, when I reboot need to set the values back. Basically for me it helps.
What might help even further is to tweak the
/sys/module/lowmemorykiller/parameters/adj
Actually EzyKernel provides a script that is suppose to improve memory killer kicking in... see
S97Ramscript
http://forum.xda-developers.com/showthread.php?t=1513413
I played a bit on this with my pone a Galaxy ACE as I had a ROM supporting A2SD and creating a swap you will see that android Gingerbread can use swap but not as much as you defined. The recommendation being 64 MB with swapiness of 10 for what I recall. anything above was dimmed foolish for what I understand ( not from a necessarily from an SDCARD performance stand point but more the OS) . And anyway did not help ie 128 MB swapiness of 100 and expecting to fill it .....
The memory killer is probably very clever, and made for lambda users making sure they don't run out of memory on critical process. But most of us here like to play with our device and I would prefer to be able to control what get killed instead of the OS making clever guess... The fact is that I never prevented the memory killer to kill APP (only delay it) changing minfree and or adj as well as using swap ( on Gingerbread ) The device seemed to kill un-ecessarily IMO.
I hope ICS will help in this respect. People mention it uses far less memory so it should in principle.
It is a very interesting subject quite covered about on XDA and internet. The question I would have ( no definite answers) is are there a way to totally prevent apps to get killed no mater what if it makes sense or not? it is more a curiosity from me. It could of course depend the way the APP got developed...
What I know is when I changed
/sys/module/lowmemorykiller/parameters/adj
it took the changes but after launching APPs etc it went back to initial default values... that was still testing on gingerbread. For testing I use Cigyc as it is big in memory launching many APP...it seemed to me APP got killed when not used for sometimes regardless memory left.
anyway
HTH
Also I am truly desperate getting getting ICS on this wonderfully device... Surely not the only one
Anyone with nice rumors for me to get patient.... April is what I got...
As surely love 7.7 hardware I must say I hate samy for there software and update policy...
In this case I definitely would recommend other manufacturers and could only dream about Apple kind of support on that...
Sent from my GT-P6800 using xda premium
i can only open about 3-4 app before my ram is full and its forcing to closing app . seriously ? wtf is this .
i feel like this phone is worse than n95 .
if i open a web page one youtube link and i still have in memory my message app it will start closing app and sometime it even close the Touch wiz widget so they have to re appear and load for 4 second . i cant believe they only putted 1gb of ram with all there touchwiz bloarware.
Ram issues
Check what apps are running on the background, i would check primarily things you log into that are always logged in like FB, Gtalk, Skype. although even with all those running you shouldnt have issues, maybe try doing a cache and dalvik cache wipe reboot and check changes.
MY BEST FIX is rooting, flashing an AOSP based rom that normally for me they use 350 to 400mb on a normal basis instead of 550-600mb in a sammy based rom.
mine is usally 800-1g and im constantly clearing memory. I dont get it either.
1slow4G said:
mine is usally 800-1g and im constantly clearing memory. I dont get it either.
Click to expand...
Click to collapse
S3 has a horrible memory management.
1 gb ram ain't enough for the beast.
Launcher redraw on a Top end phone is an Epic fail.
Selina40Kyle said:
S3 has a horrible memory management.
1 gb ram ain't enough for the beast.
Launcher redraw on a Top end phone is an Epic fail.
Click to expand...
Click to collapse
I agree, I just opened every app i have and went up to 1.26gb.. and when i have no apps open it jumps from 800-1gb on its own.. so i guess its all in the system that takes up most of the space
Selina40Kyle said:
S3 has a horrible memory management.
1 gb ram ain't enough for the beast.
Launcher redraw on a Top end phone is an Epic fail.
Click to expand...
Click to collapse
Jeez 1gb is more than enough
Problem is with the Samsung bloatware. Kies, Remote Controls and all those other services. Delete kiesexe and freeze the Samsung crap inc SVoice..
I see no need to sync to Samsung and Google. The Google services are enough.. The Samsung store is only worth unfreezing for those free offers. The four tracking services ain't needed etc I use Avast to do that etc.
Getting 285M free apx after bootup, same as ICS, on 4.1.2 now. 12 widgets, FB, G+, Fancy widgets, Jorte etc
Also make sure not to run supercharger. It kills multitasking!
Disable all the Bloatware or freeze it using link2sd.
(all share, talk back, s-voice)
Still sitting between 540mb and 630mb maximum
Sent from my GT-I9300 using xda app-developers app
Kojaes
My 2gb i747m really makes use of the extra ram. It not only can handle 50 background apps with stock rom as apposed to 15-20 for the 1gb version (assuming there is enough ram), but it will boot with about 1.6-1.7gb available, about 700mb used, and 1gb free, and will use memory up to about 200mb free before killing apps to make room for new apps. Bottom line, it multitasks like a S.O.B. My opinion based on 2.5 years Android experience...is that 2gb ram helps big time...especially if you do not optimize your system.
If I had the 1gb version, I would consider a lighter rom as some have mentioned, but also the V6 Supercharger app with specific settings to allow maximum multitasking while remaining stable...which might take some experimenting. I would install Titanium Backup Pro and freeze as many non needed apps to prevent them from loading at boot and using up precious ram. Also, for some apps, I use AutoRuns to prevent them from loading at boot time.
Also remember...that some apps will stay in RAM when it's plentiful. But other apps are programed to allow Android to kill them after a certain length of idle time when they haven't been used.
Ram management is fine on the S3.
If you are not happy with it use a task killer, custom rom/kernel and/or supercharger v6 script.
Also if your ram<100 then you should start making complaints.
My free ram is at 120mb-160mb and i'm happy,no lags,no slowdowns,nothing at all.
Android preloads apps in memmory in order to open faster when we launch them.
Free ram really is wasted ram...it cancels multitasking and if you've bough a 600$ phone and can't multitask with it then you're worth of your fate.
nfsmw_gr said:
Ram management is fine on the S3.
If you are not happy with it use a task killer, custom rom/kernel and/or supercharger v6 script.
Also if your ram<100 then you should start making complaints.
My free ram is at 120mb-160mb and i'm happy,no lags,no slowdowns,nothing at all.
Android preloads apps in memmory in order to open faster when we launch them.
Free ram really is wasted ram...it cancels multitasking and if you've bough a 600$ phone and can't multitask with it then you're worth of your fate.
Click to expand...
Click to collapse
The fact that an user has to get task killer and manage memory by him own: FAIL!
I know android pre loads stuff in memory, but it got the priority all wrong.
Why does it keep killing msging, phone and the GODDAMN launcher .
While it never kils the stupid stuff like "Google Book mark Sync", unless you freeze it.
There's no denying that 1gb has crippled S3 badly.
You can claim "Free ram is wasted ram" and throw down links, but at the end of the day it is giving me a bad experience.
Case in point:
1) Launcher Redraw:
Two points to it:
->Bad priority (I'm not sure if it's either a Samsung fault or Android; OOM 6 isn't the way to go).
-> Less ram.
The fact that browsing through play store for 15 mins and then hitting Home button results in launcher redraw is pathetic.
Less ram is the culprit( atleast one of the).
On such an expensive device this is just EPIC FAIL.
Sure we can do Super recharge and try removing the bloatware, but these are quick fixes and doesn't get rid of the main problem.
Not to mention not every one finds all this stuff easy.
The fact that you have to do tweaking on the 'supposedly greatest android phone' to make it work smoothly is an EPIC FAIL.
Custom Roms for an device as expensive as S3, should be there to enhance functionality and increase features. Not to make it works the way it should have out of the box.
2) Sh**ty Multitasking:
Trust me, my iPod touch does better multi tasking that S3 for day to day experience. (I am not an apple troll, btw)
And it doesn't even have a true multitasking and the specs are no where near S3.
When I pause a game, and resume it after an hour it starts from exactly same place . Try that with S3.
Try to use your phone when many apps are getting updated and notification bar is constantly changing.
It'll lag the hell out.
There's no defending to these points.
This is where Apple excels , by giving user everything perfect from out of the box.
Sure you can't do much, but what ever you can, you do it smoothly.
What makes me sad is that Samsung is so close to it, yet they screwed the experience.
And I'm not even going to talk about Contacts and Phone apps.
nfsmw_gr said:
Ram management is fine on the S3.
If you are not happy with it use a task killer, custom rom/kernel and/or supercharger v6 script.
Also if your ram<100 then you should start making complaints.
My free ram is at 120mb-160mb and i'm happy,no lags,no slowdowns,nothing at all.
Android preloads apps in memmory in order to open faster when we launch them.
Free ram really is wasted ram...it cancels multitasking and if you've bough a 600$ phone and can't multitask with it then you're worth of your fate.
Click to expand...
Click to collapse
Sorry but this is complete and utter drivel. Stop quoting websites and Google and start wising up.
If you have a game that needs to run and it uses 100mb and the phone has no free ram it kills something else.
This would be fine if the phone loaded the apps quickly but it doesn't.
Custom ROMs do not fix the lack of ram and neither do any of the memory management scripts.
My phone has around 200mb to 300mb though and it still loads and reloads phone and messaging and browser randomly.
Sgs3 is useless at memory management and anyone who says otherwise is living in a dreamland.
No lags and slowdowns is just blatantly not true as your messaging app and phone app will frequently take up to two seconds to load if you are using any Samsung ROM.
biffsmash said:
Sorry but this is complete and utter drivel. Stop quoting websites and Google and start wising up.
If you have a game that needs to run and it uses 100mb and the phone has no free ram it kills something else.
This would be fine if the phone loaded the apps quickly but it doesn't.
Custom ROMs do not fix the lack of ram and neither do any of the memory management scripts.
My phone has around 200mb to 300mb though and it still loads and reloads phone and messaging and browser randomly.
Sgs3 is useless at memory management and anyone who says otherwise is living in a dreamland.
No lags and slowdowns is just blatantly not true as your messaging app and phone app will frequently take up to two seconds to load if you are using any Samsung ROM.
Click to expand...
Click to collapse
True that.
I have no idea what is stored for 500-600Mb ram if not the important things like Phone, Msg and Launcher.
Useless stuff.
It is just marketing and business politics, Samsung knew that 1GB is not at all future proof but that is exactly what they need so they can sell the Note 2 and the i9305.
And still they sold over 30M i9300 devices.
eggman89 said:
True that.
I have no idea what is stored for 500-600Mb ram if not the important things like Phone, Msg and Launcher.
Useless stuff.
Click to expand...
Click to collapse
Man, Android loads that stuff itself based on usage, OOM settings and Minfree values. The other stuff is services that need to run full time so that Kies sync, Location and other Samsung bloat that is really not doing anything most of the time.
Ya I know.
I wonder how can the most important thing, launcher, has an OOM of 6.
Stupid really.
Is it a fault of Android or Samsung messed it up.
In all the galaxy nexus videos I've never seen launcher redraws.
So maybe Samsung messed up for whatever reason.
Sent from my Samsung Galaxy S3
"Free ram is wasted ram"
Click to expand...
Click to collapse
that remark has been misused greatly by people that can't code for ass and fail at memory optimisation.
It was originally in reference to the Superfetch feature in Vista/7 storing frequently accessed data in ram for faster application startup. It wasn't meant to be applied to applications that use huge amounts of memory for no good reason.
much of Androids poor memory management is Java related, who knows, maybe Google will get a clue and dump the Dalvik VM eventually for a native operating system.
Use aokp or cm 10
Sent from my GT-I9300 using Tapatalk 2
Diaze said:
Use aokp or cm 10
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
For many of us, camera is an important thing.
aakarani said:
Disable all the Bloatware or freeze it using link2sd.
(all share, talk back, s-voice)
Still sitting between 540mb and 630mb maximum
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Is it in the app store ?
Is there any way to freeze samsung permanently without root ?
does link2sd need root to work ?
is advance task killer enough to kill all samsung bloatware ?
Kojaes said:
Is it in the app store ?
Is there any way to freeze samsung permanently without root ?
does link2sd need root to work ?
Click to expand...
Click to collapse
1) Yes.
2) Yes. You can go to "manage apps", select the applications. There will be an option called "Disable". No need for any app.
3) See above
I would be very grateful if you G2 owners could reboot your phones and report how much RAM you have available after a fresh start.
The reason I'm asking is that I noticed in a video that the RAM was only around 500 MB with only 5 apps open, and then I saw this screenshot: just 320 MB of available with only 2 apps open!
Is the G2 really that low on RAM??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hduty said:
I would be very grateful if you G2 owners could reboot your phones and report how much RAM you have available after a fresh start.
The reason I'm asking is that I noticed in a video that the RAM was only around 500 MB with only 5 apps open, and then I saw this screenshot: just 320 MB of available with only 2 apps open!
Is the G2 really that low on RAM??
Click to expand...
Click to collapse
have you shut off services/apps you don't need? i noticed this on a verizon model they had at the store. Had 500mb left. i then tinkered and disabled many of the bloat apps and took the phone to 1.2GB of free ram. i don't know if this relates to your phone too. but the bloat slowly kills it at first.
pilot85 said:
have you shut off services/apps you don't need? i noticed this on a verizon model they had at the store. Had 500mb left. i then tinkered and disabled many of the bloat apps and took the phone to 1.2GB of free ram. i don't know if this relates to your phone too. but the bloat slowly kills it at first.
Click to expand...
Click to collapse
That's not a screenshot of my G2, it's from GSMArenas review. I don't own a G2 (yet), the low RAM figures I have seen makes me hesitant to buy one - hence my question.
But if I go ahead and get one it will be an unlocked/unbranded phone, so there will be no carrier apps on it.
Either way, what apps did you close down/disable on the model at the store?
Mines AT&T, but with most of the bloat disabled, I'm at 832. That's with stuff running and not a clean boot. Keep in mind, however, how Linux uses memory. Empty memory is wasted memory.
Sent from my LG-D800 using Tapatalk 4
RAM is meant to be used or it is useless. Android OS caches a ton of things in RAM since it doesnt cost anything or drain any significant extra battery so it looks like a lot of memory is used. If you need more RAM for your own open apps it will flush out unused cached data and apps to make room for whatever you are actually wanting to run. Having 300-400MB free RAM is pretty much perfect amount because it means a bunch of stuff is cached and ready to load fast but it also leaves enough space for a good number of your own things to be open and running before old stuff gets flushed out.
lastdeadmouse said:
...Empty memory is wasted memory.
Click to expand...
Click to collapse
EniGmA1987 said:
RAM is meant to be used or it is useless.... Having 300-400MB free RAM is pretty much perfect amount because it means a bunch of stuff is cached and ready to load fast but it also leaves enough space for a good number of your own things to be open and running before old stuff gets flushed out.
Click to expand...
Click to collapse
400 MB is what I have on my Xperia T after a reboot (no bloatware), as soon as you leave the browser and check 2-3 other apps and then return to the browser (20 seconds later) it has flushed the pages from memory and has to redownload the pages. In Pulse it kicks you out from the story (and even the category) you were reading when the app reloads, all as a result of the low RAM.
I also have the Asus Padfone 2 which has 1.5 GB of free RAM after boot, and it doesn't do any of that flushing, all your opened apps are in memory (because there is room for it), and the user experience compared to the Xperia T is like day and night due to that extra RAM.
So that's only partially true: used memory is good as long as it's made up of YOUR apps that are in memory, but 400 MB of free RAM for user-running apps is simply too little on Android, and I have my own experience, and couple of "Android-geek" friends who also complain the very same issue on their phones (Galaxy Nexus + S3), to back it up.
Since I only buy unbranded phones I'm curious what kind of bloatware you have disabled on your carrier-branded phones?
I'm having concerns with the ram. I usually have 750 on a fresh boot and 300 -400 average daily. My issues are when apps close randomly such as Sirius radio or tune in radio.
For example I'll be listening to one of those apps and get a call or pause it, when I go back to listen the app is closed. Or after a call on my previous phones it would resume. On the G2 it doesn't resume playing because the app is closed. That is not acceptable.
Another example is in the stock task switcher is I try to go back to an app I used say yesterday it will still be in the task switch but if I press it to go back to it will not respond to my touch. I have to actually go back and relaunch the app from the menu. Anyone else having these issues?
Sent from my LG G2
EniGmA1987 said:
RAM is meant to be used or it is useless. Android OS caches a ton of things in RAM since it doesnt cost anything or drain any significant extra battery so it looks like a lot of memory is used. If you need more RAM for your own open apps it will flush out unused cached data and apps to make room for whatever you are actually wanting to run. Having 300-400MB free RAM is pretty much perfect amount because it means a bunch of stuff is cached and ready to load fast but it also leaves enough space for a good number of your own things to be open and running before old stuff gets flushed out.
Click to expand...
Click to collapse
Yeah, I don't get people. They think free ram is magically going to make the phone faster. RAM is meant to be used. If your phone is not using ram, then it's not going as fast as it could. I usually have around 400-600MB free. I have frozen all apps that I think are bloat or I don't use.
Using cleanrom 1.0 I have over 600MB free. With open apps. No complaints.
Sent from my LG-D800 using xda app-developers app
To less off fee ram and android will start shut down backgroundapps to free up some. So little free ram is good on any linux. You surf the net on your browser and want to have any backgroundapps alive and kicking? You need ram So kill all bloatware and services you don't need, works in S4 and should work on the clone
Skickat från min HTC One via Tapatalk 2
verks said:
I'm having concerns with the ram. I usually have 750 on a fresh boot and 300 -400 average daily. My issues are when apps close randomly such as Sirius radio or tune in radio.
For example I'll be listening to one of those apps and get a call or pause it, when I go back to listen the app is closed. Or after a call on my previous phones it would resume. On the G2 it doesn't resume playing because the app is closed. That is not acceptable.
Another example is in the stock task switcher is I try to go back to an app I used say yesterday it will still be in the task switch but if I press it to go back to it will not respond to my touch. I have to actually go back and relaunch the app from the menu. Anyone else having these issues?
Click to expand...
Click to collapse
Your Sirius app closing when you switch to another app is a typical behavior when you are low on ram, so the system immediately closes down an app when it goes to the background in order to free up memory. It's very frustrating, and it was the only reason I stopped using my Xperia T. Never had that problem with my Padfone 2 though, precisely because of all that free ram available at any point.
The task switcher issue you're describing is a bug though, I have never heard of it before but the OS should not behave like that.
Gasaraki- said:
Yeah, I don't get people. They think free ram is magically going to make the phone faster. RAM is meant to be used. If your phone is not using ram, then it's not going as fast as it could. I usually have around 400-600MB free. I have frozen all apps that I think are bloat or I don't use.
Click to expand...
Click to collapse
And I don't get people who reply to threads they haven't read (or don't understand). It's not about speed.
dondavis007 said:
To less off fee ram and android will start shut down backgroundapps to free up some. So little free ram is good on any linux. You surf the net on your browser and want to have any backgroundapps alive and kicking? You need ram So kill all bloatware and services you don't need, works in S4 and should work on the clone
Click to expand...
Click to collapse
^This
All that "free memory is wasted memory"-talk is nonsense in this context, but people have read that phrase someplace and are now throwing it around whenever they hear the word "RAM", regardless of context.
hduty said:
I also have the Asus Padfone 2 which has 1.5 GB of free RAM after boot
Click to expand...
Click to collapse
Proof or GO of this thread. Nonsense and BS. Padfone 2 can haz 1.5 AVAILABLE memomy from boot, but it's not FREE memory. And that't ppl such as you that constantly spreading BS all around making other ppl believe that something's wrong with G2
hduty said:
^This
All that "free memory is wasted memory"-talk is nonsense in this context, but people have read that phrase someplace and are now throwing it around whenever they hear the word "RAM", regardless of context.
Click to expand...
Click to collapse
Exactly! I too own an HTC One X+ and the biggest and only real complain is the crappy ram management. My device does only have 1gb of ram though. Say i'm using Pandora, i receive a call, end call, phone goes back to Pandora but opens it from scratch, that to me is crappy app/ram whatever you want to call it management. I just figured it was due to my device only having 1gb of ram but does Pandora and stock Dialer app really use that much ram? No, not even close which again concludes me to think crappy Android OS 4.1 ram management.
Sad to see this G2 device "top of the line hardware" with 2gb or ram does the same exact thing. Only thing these two devices have in common, using Android OS. Mine is 4.1 and this device 4.2 but obviously no difference as users saying they get the same issue here.
I'm also using a custom rom with as many tweaks possible "to prevent this"
from happening.
I remember my old HTC Diamond doing this too and that device only came with i believe 256mb of ram, sad that to today there is still no resolution to this issue.
Worst part is if you're playing a graphics intense game like dead trigger, get a phone call, even if you ignore it and device goes back to dead trigger, the game now restarts from scratch and all progress never saved as if you weren't even playing the game. Total waste!
My att G2 has about 650 with alll loatwear installed,
after clean tool i get around 800.
When more dev. happens its going to be possible to have 1.2+ with optimization , LG has alot crap running.
People should actually go read how Android manages RAM before spewing nonsense. Stop caring about free ram. Android will manage the amount of RAM it uses. I had the GNex and when using slacker with maps and glympse I would get the low memory message sometimes but at no time did those apps close or crash. With the G2's 2GB of RAM, it's should be able to run all your apps just fine.
http://www.androidcentral.com/ram-what-it-how-its-used-and-why-you-shouldnt-care
http://developer.android.com/reference/android/app/Activity.html#ProcessLifecycle
"Process Lifecycle
The Android system attempts to keep application process around for as long as possible, but eventually will need to remove old processes when memory runs low. As described in Activity Lifecycle, the decision about which process to remove is intimately tied to the state of the user's interaction with it. In general, there are four states a process can be in based on the activities running in it, listed here in order of importance. The system will kill less important processes (the last ones) before it resorts to killing more important processes (the first ones).
The foreground activity (the activity at the top of the screen that the user is currently interacting with) is considered the most important. Its process will only be killed as a last resort, if it uses more memory than is available on the device. Generally at this point the device has reached a memory paging state, so this is required in order to keep the user interface responsive.
A visible activity (an activity that is visible to the user but not in the foreground, such as one sitting behind a foreground dialog) is considered extremely important and will not be killed unless that is required to keep the foreground activity running.
A background activity (an activity that is not visible to the user and has been paused) is no longer critical, so the system may safely kill its process to reclaim memory for other foreground or visible processes. If its process needs to be killed, when the user navigates back to the activity (making it visible on the screen again), its onCreate(Bundle) method will be called with the savedInstanceState it had previously supplied in onSaveInstanceState(Bundle) so that it can restart itself in the same state as the user last left it.
An empty process is one hosting no activities or other application components (such as Service or BroadcastReceiver classes). These are killed very quickly by the system as memory becomes low. For this reason, any background operation you do outside of an activity must be executed in the context of an activity BroadcastReceiver or Service to ensure that the system knows it needs to keep your process around.
Sometimes an Activity may need to do a long-running operation that exists independently of the activity lifecycle itself. An example may be a camera application that allows you to upload a picture to a web site. The upload may take a long time, and the application should allow the user to leave the application will it is executing. To accomplish this, your Activity should start a Service in which the upload takes place. This allows the system to properly prioritize your process (considering it to be more important than other non-visible applications) for the duration of the upload, independent of whether the original activity is paused, stopped, or finished."
BTW, this is what I get on fresh boot, and I haven't even frozen or uninstalled all of the bloatware apps in the ROM.
On another note, you should stop acting like a **** OP. If you ask a question on a forum expect answers from all sorts of people. If you dont like some of those answers dont ask in the first place.
Billy Madison said:
Proof or GO of this thread. Nonsense and BS. Padfone 2 can haz 1.5 AVAILABLE memomy from boot, but it's not FREE memory. And that't ppl such as you that constantly spreading BS all around making other ppl believe that something's wrong with G2
Click to expand...
Click to collapse
So who's spreading the BS?
Now GO of this thread.
Gasaraki- said:
People should actually go read how Android manages RAM before spewing nonsense. Stop caring about free ram. Android will manage the amount of RAM it uses. I had the GNex and when using slacker with maps and glympse I would get the low memory message sometimes but at no time did those apps close or crash. With the G2's 2GB of RAM, it's should be able to run all your apps just fine.
Click to expand...
Click to collapse
The only nonsense around here is the assertion that the amount of free ram on a phone is of no concern. Android's memory management can't perform miracles, nor circumvent basic computer science. If this was all about memory management we wouldn't be seeing phones with 2GB, and even 3GB of ram instead of 1GB, would we?
An app can only be loaded into and run from free memory, and if there is not enough of it the OS will try to make more available, i.e close down/cache/freeze/tombstone/swap some other running process that's currently alive (e.g. some other app that's currently running). If that closed process happens to be an app the user was running, and that the user expects to be alive when he returns to it, then you can encounter the scenarios described by some people in this thread - including myself, with apps being shut down unexpectedly in the background (I'm simplifying a little but for this discussion it's close enough...). More free ram means the OS is much less likely to close down apps opened by the user, simply because there is no reason to close them (and *here* is where the expression "unused memory is wasted memory" becomes relevant).
The exact implementation of *how* and *when* Android closes/freezes apps is what the memory management is all about, and what the text you posted explains. The talk about Android's memory management originally came from all the task managers people were using on their Android phones up until 2-3 years ago, which started to interfere with how the OS was supposed to work. But that is a completely separate discussion, irrelevant to what we are talking about here.
I honestly can't explain it any simpler than that. In other words, free (as in "unused") memory is fundamental in *any* OS for a good user experience, because your apps are going to run in that free memory, and the more of it you have the more apps you can run simultaneously without the OS closing them down in the background.
EDIT:
Just found this while I was searching for another story:
http://www.androidpolice.com/2013/08/30/htc-one-mini-review-the-awkward-ram-deprived-middle-child/
Note the title, and the "Not so good"-summary:
RAM. There isn't enough. 1GB does not cut it, HTC, and it was a tragic misstep to only give the One mini a single gig. Task switching and opening / closing apps becomes maddeningly slow the more you use the phone. It ruins the experience for me when this is happening many, many times a day.
Click to expand...
Click to collapse
So how come it's an issue on the Mini if the concern for free ram is "nonsense" and it's all about Android's memory management??
The issues described in the Mini-review is exactly what I faced with my Xperia T, and the reason why I asked the question here in the first place.
So I will repeat it for the last time: the amount of free ram you have on your phone is fundamental and - contrary to what some of you believe and have repeated here over again - anything but "nonsense", and has nothing to do with "unused memory is wasted memory" and all that talk about Android's memory management.
EniGmA1987 said:
BTW, this is what I get on fresh boot, and I haven't even frozen or uninstalled all of the bloatware apps in the ROM.
On another note, you should stop acting like a **** OP. If you ask a question on a forum expect answers from all sorts of people. If you dont like some of those answers dont ask in the first place.
Click to expand...
Click to collapse
No more **** than someone who replies with "yeah, I don't get people", acting like a smarta**, while in reality completely missing the point of the question.
Either way, thanks for posting your numbers.