Not enough RAM? - Xperia Z2 Q&A, Help & Troubleshooting
Hey guys,
Lately I've had problems with my apps always closing on me in the background when using multiple apps.
I.e I use Chrome with 8-12 Tabs, Moonreader+ also Walkman. And DsDownload and DsFile in the Background.
So whenever I switch back to chrome it has to rebuild the homepage
If I check RAM usage I see 1.5gb free 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"
}
But then I switch to apps in Cache and see 200mb Free.
So.... Am I really in a RAM shortage or does my phone just like to force apps in the background?
Anyone knows a better app for RAM management overview?
Greets
Haldi.
Ive never actually ran into this issue unless ive had 30 tabs open on chrome or playing a game
I use 3c toolbox to see whats eating my ram
i got a curious "problem" since a few days:
a long time of using stock ROM from @spuri78 the Task Manager in statusbar shows constantly 1,7 GB free of total 2,7 GB
But since a few days (nothing changed: no mods, no apk´s) it shows only 1,2 GB (and atm only 0,9 GB) free of total 2,7 GB
Cleaning cache with TWRP does not help.
What´s wrong?
Any ideas?
Ahhh yeah 3c toolbox.
Looks better than system tuner.
BTW, anyone knows which ones are the important values in the Meminfo in /proc/?
MemTotal: 2855172 kB
MemFree: 62272 kB
Buffers: 139868 kB
Cached: 926216 kB
SwapCached: 8488 kB
Active: 937888 kB
Inactive: 1148848 kB
Active(anon): 510396 kB
Inactive(anon): 553188 kB
Active(file): 427492 kB
Inactive(file): 595660 kB
Unevictable: 25424 kB
Mlocked: 0 kB
HighTotal: 2281472 kB
HighFree: 23416 kB
LowTotal: 573700 kB
LowFree: 38856 kB
SwapTotal: 524284 kB
SwapFree: 310548 kB
Dirty: 7976 kB
Writeback: 0 kB
AnonPages: 1045364 kB
Mapped: 388804 kB
Shmem: 17368 kB
Slab: 98972 kB
SReclaimable: 52900 kB
SUnreclaim: 46072 kB
KernelStack: 17464 kB
PageTables: 39648 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 1951868 kB
Committed_AS: 81743384 kB
VmallocTotal: 278528 kB
VmallocUsed: 42756 kB
VmallocChunk: 86028 kB
I think the Sony system app settings is somewhat off the mark....
MemTotal: 2855172 kB
MemFree: 178412 kB
Buffers: 27884 kB
Cached: 482564 kB
SwapCached: 8556 kB
Active: 1169996 kB
Inactive: 646788 kB
Active(anon): 945612 kB
Inactive(anon): 409452 kB
Active(file): 224384 kB
Inactive(file): 237336 kB
Unevictable: 25424 kB
Mlocked: 0 kB
HighTotal: 2281472 kB
HighFree: 65020 kB
LowTotal: 573700 kB
LowFree: 113392 kB
SwapTotal: 524284 kB
SwapFree: 309728 kB
Dirty: 1400 kB
Writeback: 0 kB
AnonPages: 1330984 kB
Mapped: 354572 kB
Shmem: 23164 kB
Slab: 100720 kB
SReclaimable: 51776 kB
SUnreclaim: 48944 kB
KernelStack: 19456 kB
PageTables: 43072 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 1951868 kB
Committed_AS: 81296116 kB
VmallocTotal: 278528 kB
VmallocUsed: 47400 kB
VmallocChunk: 86028 kB
I wonder which value they take for the free RAM....
BTW, it happened again. I was opening about 7 chrome tabs at once and then it stopped the bandcamp app and stopped playing the new circle of dust album ram showed about 700mb free and then instantly jumped to 950mb free.
P.s before you now think " oh chrome only uses 120mb Ram" lolnope, every tab has its own process with 25-35mb ~.~
I saw your post and had to reply since they weren't any proper answer for this.
First of all yes your RAM is running out obviously if you have that much open and especially when you have ~300MB of free RAM, android likes to keep 10-15% of RAM free to ensure that it doesn't start lagging sometimes even more.
Also in settings the first page shows services and the second one shows processes this one is obvious though.
I'd suggest you use greenify to close some apps that run in the background to free up some more RAM or just uninstall the stuff you dont need because ~70% of Android apps stay running in the background.
senoy2 said:
Also in settings the first page shows services and the second one shows processes this one is obvious though.
Click to expand...
Click to collapse
Ahhhh. Yeah that does make sense now ^^
Well yeah, tell me about to many apps ~.~ wiped dalvik and had to rebuild 344 apps, took way to long.
But yeah, some heavy multitasking just happens sometimes.
A lot of chrome tabs with guids and flight comparison pages, a travelguide in Moonreader, Tapatalk for forums browsing, discord for chatting. And then you think you should upload the newest Fotos to your NAS. Out of RAM faster than you expect
Here in a short video.
https://youtu.be/bPWiIxXVjs0
Haldi4803 said:
Ahhhh. Yeah that does make sense now ^^
Well yeah, tell me about to many apps ~.~ wiped dalvik and had to rebuild 344 apps, took way to long.
But yeah, some heavy multitasking just happens sometimes.
A lot of chrome tabs with guids and flight comparison pages, a travelguide in Moonreader, Tapatalk for forums browsing, discord for chatting. And then you think you should upload the newest Fotos to your NAS. Out of RAM faster than you expect
Click to expand...
Click to collapse
Yep i do some heavy multi-tasking too but I don't really run out of RAM that often since i have everything organized and am running a CM ROM which helps too.
maybe turn off stamina mode ?
check developer options in your settings there might be an option turned on to force close tasks in the background
or the option for queue background data in power management is on turn it OFF
if nothing else reset phone it helps
but before that try rebooting
actually you should reboot like once in 3 days
+as said greenify helps alot but it hibernates apps so check the ones you dont use (also works unroot)
---------- Post added at 07:15 PM ---------- Previous post was at 07:13 PM ----------
Zspitter said:
maybe turn off stamina mode ?
check developer options in your settings there might be an option turned on to force close tasks in the background
or the option for queue background data in power management is on turn it OFF
if nothing else reset phone it helps
but before that try rebooting
actually you should reboot like once in 3 days
Click to expand...
Click to collapse
btw im on 5.1.1 official firm unroot bootloader locked and NEVER had ram issues sometimes had like 20 apps in task manager on and going no lags smooth af
I think that one need to realise that these are smartphones. Not portable supercomputers.
Sounds like OP might want to use an ultra-portable laptop instead.
I'd love to, in 5.5“ maximum and with 3 days batterylife at least.
Sadly no one wants to sell such a thing
Background processes are set to standard.
I think that's more than 4?
Related
21MB RAM Hack "KANGMEM" updated 5/4! [Source] [zImage]
This time, my RAM hack expands memory by 21MB total from the stock kernel. And this time, no camera PMEM is taken away! This is all thanks to the incrediblec kernel source released by HTC giving me some insight. This is what I did, starting from the 8MB RAM hack: - Expanded EBI1_BANK0 by 8MB because the incrediblec source said I could - Moved 5MB GPU memory from EBI1_BANK0 to SMI - Created extra memory bank in EBI1_BANK0 totalling 13MB - Added 8MB camera PMEM back into SMI, and re-enabled camera PMEM Version 2: - Eliminated third memory bank in EBI1_BANK0 and added that memory into the first memory bank As far as I know it's not possible to create a memory bank in the SMI and live to tell the tale, so that's why we're squeezing the 8MB of camera PMEM in there. In total, this adds 21MB of RAM from stock cm-kernel with seemingly no compromises. The zImage is meant to be a proof of concept and only contains this tweak on top of normal cm-kernel. I don't suggest using this zImage for long, as it doesn't contain any "extras," and the regular custom kernels with all the extra features/optimizations will probably incorporate this soon. Enjoy! Version 2 Source: http://dl.dropbox.com/u/36553/board-mahimahi-kangmem2.tar.gz Test zImage: http://dl.dropbox.com/u/36553/zImage-kangmem2 Old version Source: http://dl.dropbox.com/u/36553/board-mahimahi.tar.gz Test zImage (requires 2.6.33.3 wifi modules for wifi to work!): http://dl.dropbox.com/u/36553/zImage-kangmem cat /proc/meminfo MemTotal: 416632 kB MemFree: 39932 kB Buffers: 7988 kB Cached: 111812 kB SwapCached: 0 kB Active: 253484 kB Inactive: 82412 kB Active(anon): 220128 kB Inactive(anon): 0 kB Active(file): 33356 kB Inactive(file): 82412 kB Unevictable: 0 kB Mlocked: 0 kB HighTotal: 293888 kB HighFree: 1200 kB LowTotal: 122744 kB LowFree: 38732 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 216104 kB Mapped: 81076 kB Shmem: 4032 kB Slab: 10188 kB SReclaimable: 4024 kB SUnreclaim: 6164 kB KernelStack: 3496 kB PageTables: 11220 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 208316 kB Committed_AS: 5665668 kB VmallocTotal: 778240 kB VmallocUsed: 144392 kB VmallocChunk: 592044 kB Click to expand... Click to collapse
Nice job coolbho. Why don't you recommend using it for long?
persiansown said: Nice job coolbho. Why don't you recommend using it for long? Click to expand... Click to collapse The zimage I built has no optimizations or any changes at all. The patch itself seems to be stable afaik.
coolbho3000 said: The zimage I built has no optimizations or any changes at all. The patch seems to be stable afaik. Click to expand... Click to collapse Nice indeed, thanks. How long have you been running this kernel for? Even without the optimizations it should say stable, shouldn't it? I wonder what the consequences will be by removing the 5mb from the GPU.
jlevy73 said: Nice indeed, thanks. How long have you been running this kernel for? Even without the optimizations it should say stable, shouldn't it? I wonder what the consequences will be by removing the 5mb from the GPU. Click to expand... Click to collapse I've tested it for a few hours, and it seems to be fine. The 5MB was moved, not removed. Instead of removing that 8MB of camera PMEM as the last tweak did, I moved it. There are no RAM banks that are unaccounted for in this patch.
coolbho3000 said: I've tested it for a few hours, and it seems to be fine. The 5MB was moved, not removed. Instead of removing that 8MB of camera PMEM as the last tweak did, I moved it. There are no RAM banks that are unaccounted for in this patch. Click to expand... Click to collapse Is this the .33.2 kernel or .33.3?
jlevy73 said: Is this the .33.2 kernel or .33.3? Click to expand... Click to collapse It's the 33.3 kernel, but the patch can probably be applied to any kernel from 32. But please bear in mind that the zimage I posted here is not really for general consumption. It works, but it doesn't have any of the extras.
good stuff dude. i will patch this in and commit to git later tonight and run some tests.
Interesting. I'll integrate this later when I get to the office.
In the name of XDA science, I installed and so far so good. It's pretty fast, seems a little faster than stock .33.3 but that could just be placebo. The 21mb is definitely real. I will continue to play with it. If I run into any issue I will post logs. Thanks again.
wifi broke
Testing now. but im not quite sure if i understand this correctly is this taking the use of the camera away?
chunga said: wifi broke Click to expand... Click to collapse I think you need the modules from a 33.3 kernel but I'm not sure how that works. jmotyka said: Testing now. but im not quite sure if i understand this correctly is this taking the use of the camera away? Click to expand... Click to collapse Camera works.
coolbho3000 said: I think you need the modules from a 33.3 kernel but I'm not sure how that works. Camera works. Click to expand... Click to collapse ok im loving this, i dont use wifi much so not worried about that atm. Also i dont know if this is me and ive had a long day at work but im not getting any lag on the swiping of the home screen is this real...Placebo? PS thanx for my one year anniversary gift to my registration as an xda member!
chunga said: wifi broke Click to expand... Click to collapse Use the wifi module from Pershoot's latest commit.
jmotyka said: ok im loving this, i dont use wifi much so not worried about that atm. Also i dont know if this is me and ive had a long day at work but im not getting any lag on the swiping of the home screen is this real...Placebo? Click to expand... Click to collapse .33.3 is pretty fast compared to .33.2
jlevy73 said: .33.3 is pretty fast compared to .33.2 Click to expand... Click to collapse Did you try out asphault to see if the 5mb GPU was hurt?
nevermind.
irishrally said: Did you try out asphault to see if the 5mb GPU was hurt? Click to expand... Click to collapse Remember to compare with a stock 33.3 CyanogenMod kernel instead of those with compiler optimizations, overclocking etc. which this particular zimage lacks. I tested Google Earth and Neocore myself and they both worked.
I included this in the kernel test.
Battery
Why gallery use dati? 8mb in 10 hours
Less cache is better?- Slim JB V1 by Pidio1 + PSN_nims_jb_2.2_memory_mod_swapall-v3.0
I have noticed something strange regarding the combo: ROM Slim JB V1 by Pidio1 + Kernel PSN_nims_jb_2.2_memory_mod_swapall-v3.0 My phone have a 16 GB class 10 microSD, formatted as 160 MB swap, 512 MB ext-4 no journaling, remaining space is Fat32. Clock: Max 844, min 242, smartass V2, deadline. Also with "Kernel Samepage Merging" & "Allow Purging of assets" the system was sluggish, lagging, slow. Switch from one app to another was too slow, even if the program was already in memory. I thought that this could be due too many cache miss readings in memory, so I tried to set a lower cache value and everything is improved: it looks like another phone, with much less lags, faster. Actually I use 128 KB instead the 3 MB default cache size, and all runs much better! Would someone wants to try and report what happens? Update: after many tries I have found the optimal file cache value for this rom+kernel combo: 512KB
How do i set that? Enviado desde mi GT-S5830 usando Tapatalk 2
[Q] Why the OS uses so much RAM (Not the cache)?
[Q] Why the OS uses so much RAM (Not the cache)? I know android is caching many apps in RAM for performance, but the actual size of the cache is quite small (less than 200 MB with some apps active). I also know that 200 MB are used for kernel and stuff like that ( for example, the user have 800 MB not 1 GB) but where is used the other RAM. In the first screen shot you can see a red highlight - gor what is that RAM used if not for apps or cache? Aren't the 200 MB unavailable RAM enough? (see the second screen shot). And why simple apps like opera browser use so much resources? Most android apps use as much resources as desktop counterparts but have very crippled functionality (firefox for android use as much RAM but it doesn't have as many features). On dumb phone ( nokia s40) opera mini would run fine with just 2 MB RAM - not 200 (seriously) and render pages as fast as the sgs3 (but with a cpu with less than 400 MHz and outdated architecture) and surpringly similar features and UI (not crippled even more). Symbian (for example) apps didn't used so much resources but had mostly the same features. And sorry for the long post!
Mali 400 and memory on cheap tablets
So I'm using an A13 tablet with mali 400 GPU and 512MB of ram. 800x480 Some EGL apps are having texture problems where the screen will go black. Benchmarks that run get low FPS too like 5-15. Apps are clearly running with black screen too and in some benchmarks it goes in/out. I see error messages like: <4>[ 4516.010000] Mali: Memory allocate failed, could not allocate size 256 kB. <4>[ 4516.020000] Mali: Out of memory. Mali memory allocated: 65408 kB Configure 65535 kb and on igo primo in GL mode E/navngo ( 809): 17:54:13 MapViewpenGL_PrepareBuffers: should not be called E/navngo ( 809): 17:54:13 iGOpenGL surface_gles.cpp: Framework_OpenGL_PrepareBuffers not ready W/navngo ( 809): 17:54:13 iGOpenGL videomemorymanager.cpp: OpenGL: Cannot create 1024*1024 texture -- smaller too like 64x64 Is there any tweak or work around for this? GPU broken/sucks? The driver should be using system memory after running out of "vram" and I have 200MB free. I have gles libraries on the device and the OS is set to run gpu accelerated with only 0 1 mali in egl cfg plus build.prop set to GPU rendering.