I am using stock ROM & JB 4.1.1 in my S3 GT I9300. But it sucks & working slow. Its taking 5 to 7 sec to open contacts & messages. When i use any app like i play game than after exit from app menu icons are also taking some seconds to come. Menu opening is also taking time.. all this sucks alot.Give any solution.
1) Factory reset
2) Root it and try custom rom
3) Sell it and get something else.
Sent from my GT-I9300 using xda app-developers app
ravitomar said:
I am using stock ROM & JB 4.1.1 in my S3 GT I9300. But it sucks & working slow. Its taking 5 to 7 sec to open contacts & messages. When i use any app like i play game than after exit from app menu icons are also taking some seconds to come. Menu opening is also taking time.. all this sucks alot.Give any solution.
Click to expand...
Click to collapse
I'd suggest doing a factory reset also.
for contacts and texting, replace the stock apps (that indeed are a bit slow) by something else. I might suggest GO SMS pro for texting and exDialer for dialling and contacts. They are way faster (and on some points do sport more functionalities than the stock ones).
Now, for the redrawing of the desktop. The reason icons need to re-appear after you leave a game is that the phone did make more room for this game in memory by closing all the other apps, including the launcher. Therefore it needs to restart it totally when you quit the game. It take time.
Again, you may decide to go with an alternative launcher (I use Apex, but many others are available) in which you can control the staying in memory of the desktop or you might be able to force the TW launcher to stay in memory even if other apps are running. In anycase, doing that will be at the detriment of the game (or other memory hungry apps) performances (they will have less memory). Your decision!
Check free RAM
Go to Settings->Application Manager. Swipe left/right to get to the Running tab. Check if the amount of free RAM (at the bottom) is too low. If so find which apps are using most RAM and try killing them.
Related
Am I being paranoid or is my phone getting slower and slower :S I get tired of closing apps in the 'Running Services' tab. Is there a way to completely close an app? I got in the habit of hitting back until I return back to the homescreen but that doesn't work on all apps such as Facebook.
No thats the propper way..
If an app doesnt stop after hitting the back button it wont do this anyway
you have to kill it on task manager
apps like facebook wont close doen because they own notifications and live messaging
jiffer1991 said:
No thats the propper way..
If an app doesnt stop after hitting the back button it wont do this anyway
you have to kill it on task manager
apps like facebook wont close doen because they own notifications and live messaging
Click to expand...
Click to collapse
Task Manager? Where is that? I have an Xperia Play
There is a way ... If you use CM go to settings --> applications --> development and stop app via long press
Sent from my WT19i using XDA
Hi
Android are supposed to keep apps 'cached' in the background - having them ready should you need them once again.
One way to 'kill' apps, to free memory is to install a 'task manager' og 'task killer' (search one of these phrases in play).
They are designed to kill a list of apps with a single touch...however Google doesn't recommend this way, as they claims it might leave the system in an unstable state.
As i can't post links, you can 'google' this: 'task-killers-answer-google-developers'
You might have a rogue app or memory leaks, or your VM values are bad for your device. Are you running out of RAM? Is your CPU usage maxing out? Are you using swap or compcache? What are your VM/sysctrl values? All these things and much more can destroy a ROM.
I find that many custom ROM's have a habit of using stupid VM values. Try getting RAM Manager from Play Store and using the "Balance" preset, it works great. I also highly suggest "SystemPanel App" from Play Store (costs $3), it has an awesome Monitoring function to record a history of how all your apps, services and processes are using the CPU. That is, if the CPU is maxing out... get a CPU Usage Monitor to find that out.
EDIT: If you are using an sd-ext partition, it can also kill performance. Especially if you move dalvik-cache to sd.
GetPatriotized said:
Task Manager? Where is that? I have an Xperia Play
Click to expand...
Click to collapse
ehm i got a samsung so if i long press the home button it appears if u dont have a taskmanager built in ur rom hjust download task killer from the playstore
Hi.
First: I haven't found a thread which is only meant for my problem.
So: As written above, I'm on XXDLIB, but this behaviour is there in earlier JB releases, too (all WanamLite).
When I minimize an app (means: press home button in an app) it won't stay there long. It will be closed after a (volatile) period of time.
Example: I'm navigating and want to read something in (stock) browser. I read and minimize this app too.
I'll go back to navigation.
Afterwards I want to read my opened page (which should be in browser) and waht happens: the browser reloads the page and hasn't been listed in task manager (hold home button, left side).
So it has been closed.
First i thought that this is a out of memory issue. So I removed many apps that I don't need from /system/app and observed the memory usage then.
Same scenario as mentioned above: Navigation (Navigon) is opened, I open the browser, finish my navigation... and .. the browser is closed again.
This is vice versa: when I minimize my navigon app and use the browser for.... let's say 3 to 4 minutes the app will be closed.
Then I got deeper into it. I opened FM radio, browser, WhatsApp and evernote and minimized them, before I slept. No app with that great memory usage I would say.
But at morning ALL apps are closed.
For short: I HATE it. When I want to have my browser opened, it should be opened until I want to close it.
Sometimes I minimize my navigon app and I only need audio orders... unusable now, because the app closes very fast...
Same for browser: It eats my monthly provided data, because it reloads the last viewed page (its not reloaded from cache; with flight mode enabled there is only an error page).
It's no memory issue I would say. After opening all these mentioned apps I have more than 230 MB of free ram.
I know that wanam adds a modified services.jar with some kind of 'memory optimization script/code' from XDA devs.
But as far as I understand it, it should not lead to any closed apps.
As far as I can see, this problem is 'new' since JB (AOS 4.1.1).
In 4.0.4 it hasn't been there.
Anyone with the same problem?
Stock or mod?
Any suggestions?
I'm missing my S2... never had this kind of problems there...
Greetings,
Mario
EDIT: I'm using the newest apex launcher (free). I don't know if this could be important.
The issues you describing are present big time in ICS also. That's what I hate this phone.
I don't even think this is a Galaxy S III issue. It seems to be more of an issue with Android itself. I've noticed things like this with the pure stock android Galaxy Nexus and even on the US Galaxy S III which has a total of 1.6gb of ram available.
Mine keeps it in memory and when I return to it is still there as I left not re-started. In fact I just opened xda app after not using all day today but using many other apps it was still on the last thread I was reading. I'm running stock but rooted.
It's all about the RAM. More precisely about the amount of available RAM.
Get the free app 'Advanced Tools', go to 'options' and tick 'Root functions'.
Then go to 'System'->'System Manager'->LMKiller and configure the values.
They are thresholds, meaning that if this amount of total available RAM (disk cache deduced) has been reached, it will start killing apps off to free at least enough Ram to go above the threshold again. Lowering the values means it will only do it much later.
Make sure that you don't lower them too far, since a device running low on RAM uses the OOM-Killer to kill apps regardless of their status.
It should help to set the Dalik heap size to 128MB too, but some side effects with large games/apps have been reported.
I have also realised this problem as someone who comes from Samsung Galaxy S 2. Now I am on Omega Rom v27 and use hard swap, I should not be having this problem but no, I see that many apps are closed by system although I have huge ram available after some time. There must be a way to deal with it; I play with auto memory kill settings but have not seen a difference so far.
Regards
GT-I9300 cihazımdan Tapatalk 2 ile gönderildi
This is an Android issue even with GB, if the phone runs out of memory for the foreground process, it closes other processes in order to free up memory. However, what you're talking about (web browsing) if you're using Chrome I believe this is a chrome thing (does the page get greyed out?) Happens to me even if I leave the page on. For example:
Browsing, put phone aside, the phone automatically locks, as I unlock it does that. Doesn't bother me much though, as long as the page loads again normally. I haven't had any issue with the S3 concerning closing other applications for the foreground one.
d4fseeker said:
It's all about the RAM. More precisely about the amount of available RAM.
Get the free app 'Advanced Tools', go to 'options' and tick 'Root functions'.
Then go to 'System'->'System Manager'->LMKiller and configure the values.
They are thresholds, meaning that if this amount of total available RAM (disk cache deduced) has been reached, it will start killing apps off to free at least enough Ram to go above the threshold again. Lowering the values means it will only do it much later.
Make sure that you don't lower them too far, since a device running low on RAM uses the OOM-Killer to kill apps regardless of their status.
It should help to set the Dalik heap size to 128MB too, but some side effects with large games/apps have been reported.
Click to expand...
Click to collapse
Thanks. I will have a look - but I would say, its now memory issue, because of the free ram that is left.
Heapsize is at 128 MB, heapgrowlimit too. I played around with these values. Nothing helped.
I'll give a report tomorrow.
EDIT: On stock the heapsize is 256m. Why should someone *lower* this value, like wanam?
Any idea? I'm no programmer...
Removing the bloat helped here a lot and that change in the build.prop from 256 to 128m.
Delete kiesexe from system/bin if you don't use kies. Freeze all the Samsung applications and services. Finally don't use Supercharger.
Swyped on I9300 - XXDLIB - Siyah kernel - JKay & Thunderbolt tweaks.
To me, it happens randomly. Sometimes the browser just show the same page without reload even after a few days! But sometimes it just reload after receiving a call!!!
Is not big problem on a daily usage but is very very big problem when I'm downloading something and have to worry about incoming call.
Sent from my GT-I9300 using xda app-developers app
hey guys, it makes me miss my little "Eclair" or "Froyo" phone...
a phone with this huge capabilities can't have this type of issue...
im getting this issue when im playing and need to change a track in song player...
then it always restart the game and it sucksssssssssssssss!!!!! ;/
So, thank you all.
I increased heapsize to 276. Now the apps are hold longer in memory.
I observed something strange: When I use flight mode, apps are closed too... but thats ok.
im playing Football Manager Handheld
and it closes everytime too...
cant handle this!!!!
i want a phone that does the things correctly.....so sad!!
Ya this is really sad!!
We keep on saying how Android does true multitasking and all, but at the end of the day it's not getting done what we want to.
I was downloading Shadowgun the other night, and after about 50%, I got a msg so I pressed home button to go to the Msg app and then:
1) Home Redraw ..grrrrrrrrrrrr.
2) I replied back to text and opened the Shadogun from Recent Apps and the downloading had stopped.
Had to start it again.
WTF??
Why does android not kill the other useless cached things which is taking upto 300-400 mb ram.
Why does it have to kill Launcher and the latest foreground operation??? The worst kind of management ever!!
Why doesn't it kill Maps instead of Launcher. I've not touched maps in two days and it takes about same ram as my Launcher does??
It has got the sorting all wrong...I hate it...
I don't know how it is in iOS, but it couldn't be worse
d4fseeker said:
It's all about the RAM. More precisely about the amount of available RAM.
Get the free app 'Advanced Tools', go to 'options' and tick 'Root functions'.
Then go to 'System'->'System Manager'->LMKiller and configure the values.
They are thresholds, meaning that if this amount of total available RAM (disk cache deduced) has been reached, it will start killing apps off to free at least enough Ram to go above the threshold again. Lowering the values means it will only do it much later.
Make sure that you don't lower them too far, since a device running low on RAM uses the OOM-Killer to kill apps regardless of their status.
It should help to set the Dalik heap size to 128MB too, but some side effects with large games/apps have been reported.
Click to expand...
Click to collapse
Best reply in this thread. I have these settings :
LMkiller: 32/40/48/56/64/72
dalvik.vm.heapsize=256m
To fix launcher redraws, change it's OOM value. Supercharger V6 can help with that. Also debloated ROMs help a lot
j0ep0 said:
Best reply in this thread. I have these settings :
LMkiller: 32/40/48/56/64/72
dalvik.vm.heapsize=256m
To fix launcher redraws, change it's OOM value. Supercharger V6 can help with that. Also debloated ROMs help a lot
Click to expand...
Click to collapse
This is where Apple wins and Samsung fails.
So much just to make your phone smoothly, something Samsung should have done and not the user.
j0ep0 said:
Best reply in this thread. I have these settings :
LMkiller: 32/40/48/56/64/72
dalvik.vm.heapsize=256m
this settings will solve the problem????
if so, how to set up?????
Click to expand...
Click to collapse
Hello,
ـــــــــــــــــــــــــــــــــــــــــــ
My mobile information.
ـــــــــــــــــــــــــــــــــــــــــــ
i have Samsung Galaxy Y Duos GT-S6102
Android 2.3.6.
I am using the Stock ROM, My mobile is rooted.
I am also using GO Launcher EX and Go Locker.
ـــــــــــــــــــــــــــــــــــــــــــ
My Problem.
ـــــــــــــــــــــــــــــــــــــــــــ
When i am using my phone for a while it is fast, for example switching the AppDrawer screens, Open Messenger close it again, Go to home screen instantly after pressing ( Home ).
but when i leave my mobile for a while ( 10min + ) it become slow ( when i unlock the screen the Home screen appear after a while, the app drawer take long time to load and is laggy while switching screens, opening an application take a while too.
Notes :
1- I Don't have any Auto-Task killer applications ( i had before but uninstalled it )
2- I noticed that my phone lose Internet Wifi connection too, because when i open FB messenger it show me the "Connecting" message.. i also doesn't receive notifications after leaving my phone idle for a while.
3- When i unlock the phone and start using it the notifications are revived ( delayed notification )
Well, your device has very low RAM. Apps like Facebook, Messenger and Go Launcher, use a lot of RAM. And if you have to much apps running at once, your phone will slow down. You can try Greenify app to hibernate some of these apps (Facebook for sure). A used to have a Galaxy Ace, and Greenify helped a lot.
About Wifi and delayed notifications, see in Wi-Fi settings if the option to keep it on during sleep is set to "always". If not, change it. That should solve the problem.
Sent from my Nexus 4 using Tapatalk
meatboy371 said:
Well, your device has very low RAM. Apps like Facebook, Messenger and Go Launcher, use a lot of RAM. And if you have to much apps running at once, your phone will slow down. You can try Greenify app to hibernate some of these apps (Facebook for sure). A used to have a Galaxy Ace, and Greenify helped a lot.
About Wifi and delayed notifications, see in Wi-Fi settings if the option to keep it on during sleep is set to "always". If not, change it. That should solve the problem.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks for your answer, but..
I Uninstalled facebook 2 months ago, And the problem is not that the mobile is generally running slow, the fact is while i am using it for more than 30 sec it start to be fast and keep to be fast until i lock it again.
but when i lock it and keep it for more than 10 minute and then re-use it, it run slow for about 30 second then start to be fast again ( which is not good when i want to do a fast call or something with such a delay )
i am suspecting that after the mobile be IDLE for a while the service and applications closes it self .. The launcher close itself ( thats why the mobile always delay ), the applications background service too ( thats why i get no notifications ).
so if my theory is right, what is the reason that cause this ?
Now I understood...
Well, I'm no android expert, but I know the system needs RAM to work. Some applicatins are cached in memory to open faster, without the need to be load all over again, but when the system runs low on memory, it tends to kill background applications/services to keep foreground apps in use.
Maybe your apps are not being cached, and/or being restarted for some reason right after the phone wakes, that could explain why your phone slow down a bit then get back to normal.
I hope some dev can explain it better.
Sent from my Nexus 4 using Tapatalk
Definitely low RAM can be a culprit, but I wouldn't be surprised if at least half the reason is the combo of Go Locker and Go Launcher. They are cool apps with all kinds of customizations, but have used them on multiple devices, even the most powerful ones at the time and have never been pleased with the performance vs other comparable apps. Especially if the Go lockscreen is fighting with the system one to see which one will turn on will you hit the power button and the RAM switching over to it in time when the phone wakes.
Another possible thing would be that the screen off profile is too aggressive and takes a bit to ramp up to normal speeds and get everything running again.
But try using a different combo for the lockscreen and launcher and see if it doesn't make a difference (make sure to kill the Go apps otherwise they will run in the background along side the new apps and make it worse). My $ is on that it will.
hi everyone
i've been using the d620r version for half a year now and there is a problem i see with the ram managment. the phone just can't keep a few tasks running at once. when i listen to music, or chat with chatheads (fb messenger) and open another app, for example maps, browser, or any game, the system simply closes the music and messenger apps running in the background. and i don't even want to mention the homescreen which reloads everytime i open the simplest app...
i am rooted, and this is what i've tried to do to solve my problems:
deleted lg the bloatware (like lg sync etc)
deleted google bloatware (google search, play games, play music, etc)
played around with auto memory manager (setting really low values so apps would not get killed)
tried to force ongoing notifications using the xposed module app settings
tweaked around with gl tools, to decrease graphics so apps would be lighter
decreased screen resolution using resolution changer pro (this helped but it made the phone and message apps to forceclose)
i even flashed another rom, the crystal PA 8 available here on xda.. this actually helped, there was much less closing, BUT the rom is too unstable and buggy for everyday use...
is there anything else i could do?
thanks a lot
I don't know about any other users but root takes something from performance, at least here (D618). What I suggest is: flash back stock, full wipe (KDZ), root but don't heavily use apps that require root, don't use a lot of xposed modules and etc. Hope it helps.
bombaglad said:
hi everyone
i've been using the d620r version for half a year now and there is a problem i see with the ram managment. the phone just can't keep a few tasks running at once. when i listen to music, or chat with chatheads (fb messenger) and open another app, for example maps, browser, or any game, the system simply closes the music and messenger apps running in the background. and i don't even want to mention the homescreen which reloads everytime i open the simplest app...
i am rooted, and this is what i've tried to do to solve my problems:
deleted lg the bloatware (like lg sync etc)
deleted google bloatware (google search, play games, play music, etc)
played around with auto memory manager (setting really low values so apps would not get killed)
tried to force ongoing notifications using the xposed module app settings
tweaked around with gl tools, to decrease graphics so apps would be lighter
decreased screen resolution using resolution changer pro (this helped but it made the phone and message apps to forceclose)
i even flashed another rom, the crystal PA 8 available here on xda.. this actually helped, there was much less closing, BUT the rom is too unstable and buggy for everyday use...
is there anything else i could do?
thanks a lot
Click to expand...
Click to collapse
make swap in cache partition because its so dumb to have that much free memory
and thats why apps are being killed
thanks for your opinion. actually, this problem occured even before i rooted the phone. right now, i'm back to stock. i hoped that maybe i could expand my ram using rohesoft swap expander but our kernel is not supported and i couldn't find any custom ones...
sebatox said:
make swap in cache partition because its so dumb to have that much free memory
and thats why apps are being killed
Click to expand...
Click to collapse
kernel doesn't support swap
oooh i was sooo wrong... the cache swap file works perfectly, the phone is much much smoother now
if anyone is experiencing the same issue, just download ram expander, choose the swap file location to cache and enjoy
I use almost 290 apps in my android phone. i might use upto 15 to 20 apps in the back ground. This means i open them and close them and use another app, and if i go to recent apps list, they all were in recent apps.
I'm using currently Asus Zenfone 2 Laser 5.5 in 2gb ram. Though if i try to open the apps (either other or the same app is running in the background or not) the app sometimes takes more than 4 to 5 secs to load and 2 secs to load anytime.
To manage the ram i use greenify, hibernating all the apps which i dont use, not the once which im reporting. apps which do take long gaps while opening are facebook, page manager, quora, twitter.. and i think even almost all apps..taking time.
I don't want that lag between the tap and seeing the app opened. So what to do for this? do i need high end processor or ram? or both? or is it that the apps on android are such a like, taking huge resources in background?
I dont want game power or camera or graphics, just want the apps to be opened as i tap on them.