yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Colemak:
Have you compared this to the default tool under 'Settings > Apps > Running'? I've never used that tool before and am not sure where it's getting it's numbers from. But I do know that a high amount of RAM being used is not necessarily a bad thing, since it might just be cached. I would recommend using Elixer 2 for all the stats you'll never need for your phone. When I checked the "android system" process was taking about 100mb
[Samsung Galaxy Nexus] BinkXDA:
Maybe you should try the stock ROM? I didn’t install the app you noted here, but I also don’t have this crazy 5, 10, 20 second issues that you have after a week of uptime.
[Samsung Galaxy Nexus] T4rd:
Yeah, I've looked at the stock app manager and it showed about the same amount of remaining RAM when it was down to ~100MBs. But right now it's showing about 90MBs less RAM available on SystemPanel as compared to the stock app manager.

Thanks for the Elixer link. I've never heard of that and it seems pretty nice. On Elixer, the RAM usage amount it's displaying matches up exactly with the "Resident" Memory Usage displayed on System Panel (2nd and 4th pics in OP). I'm not sure what the difference between "Resident", "Effective" and "Shared" memory is, but it seems "Effective" is what's actually utilizing the physical RAM on the phone since that's what's being displayed on the main processes/services page in SystemPanel.

Yeah, I'm considering that because I ran my Nexus stock for a few weeks just to make sure my hardware was good (my first stock/unrooted Nexus randomly rebooted periodically in its first week so I exchanged it for my current one) before I started rooting/ROMing the phone and I don't remember ever experiencing anything like this on stock 4.0.2. I definitely didn't have many launcher redraws, if at all. It just sucks going back to stock after being used to all the extra functionality of these other ROMs. I really like having all the status bar customization/widgets, fast charge/LTE toggles and most of all the search and menu buttons on the Navbar.

It's annoying to have to compromise the speed of the device for more functionality. It seems no one else has these same issues, but I do and that's why I'm here trying to figure it out so I don't have to make these compromises if possible.

Thanks for the responses :). Any more are very welcomed.
[Samsung Galaxy Nexus] RogerPodacter:
Wow this looks like a problem. I haven't noticed this issue but I'll start paying attention. I use system panel all the time. I can confirm however that my total ram amount never ever gets below 200mb, so I prob don't have this issue.
[Samsung Galaxy Nexus] T4rd:
Bump for help.
[Samsung Galaxy Nexus] Zepius:
first thing i would do is try stock. it's not hard to go back to your rom if you make a backup.

see if the problem resides in the rom itself.
[Samsung Galaxy Nexus] hasnol143:
I have the same EXACT problem on 4.0.3 AOKP... its really starting to get annoying i just used the app and found my system is at 300mb!
[Samsung Galaxy Nexus] adrynalyne:
Use stock. It has been mentioned several times. If it doesn't have issues, then its crappy roms with memory leaks.
[Samsung Galaxy Nexus] RogerPodacter:
If it helps I'm on aokp 29 4.0.4 and haven't seen this bug yet. I keep checking periodically.
[Samsung Galaxy Nexus] hasnol143:
Dont you have signal issues on 4.0.4? For gsm anyways
[Samsung Galaxy Nexus] RogerPodacter:
So far I don't have signal issues.
[Samsung Galaxy Nexus] T4rd:
I think I may have somewhat figured this out now.

I went into my "Superuser" app to see what apps had root permissions and "system" was among them. So I toggled it to "deny" and rebooted the phone. Upon reboot I got a prompt that "System" was requesting root permissions. I denied that too and left the box unchecked so it will prompt me again if it tries to access root again (to see what actions trigger it later). So far "System" has stayed in the 50-60 MB range for usage, but it's only been a few hours since that reboot. I'll have to monitor it for the next day or so to see if that keeps it down.

I've noticed something since monitoring this "system" usage for the past week too. Once it reaches around the 300 MB spot in RAM usage, it causes my phone to reboot. I've seen it consistently do this 3 times in the past week or two. So there's definitely like a memory leak or something because it slowly but surely increases. Every time I went back to check it after a few mins of usage, it would have raised by at least 1-2 MBs. I don't think I've ever seen it lower in usage. It seems like the more I use my phone, the higher the RAM usage gets for "system".

So could anyone that's reading this thread (that's rooted) check their Superuser app and see if this "system" app is listed and what permissions it has? I'm hoping that I've found out that it's not supposed to have root access. But then that begs the question; what is "system" and why is it requesting root access? If it's a legit service; should it still have root access?

I'm hoping to see that no one else here has it listed in their Superuser app so that I can leave it as it. I just hope it's not something that requires root access and will interfere with the OS at some point if it don't have the permissions it requires.

Thanks for all the help so far!
[Samsung Galaxy Nexus] adrynalyne:
System requiring root access?

I'd call that a malicious app.
[Samsung Galaxy Nexus] T4rd:
Yeah, I was thinking that too, but could you please check your running services and Superuser app to see if you see it in there too? That's what I'm trying to see.

Thanks!
[Samsung Galaxy Nexus] adrynalyne:
Only in system panel.
[Samsung Galaxy Nexus] adrynalyne:
My apologies. I do under system panel. It looks like the screenshot in the original post. However, it definitely does not have root access.
[Samsung Galaxy Nexus] T4rd:
Thanks :). I wonder why a lot of other people see it running on their phone too then? I doubt we're all infected.. :confused:.

Edit: See your second post. Thanks for clarifying.
[Samsung Galaxy Nexus] ChongoDroid:
Doesn't the system require root access for ROM control on aokp?

Sent from my francoPhone
[Samsung Galaxy Nexus] T4rd:
Good question. I'm on LiquidSmooth 1.25 at the moment though.
[Samsung Galaxy Nexus] adrynalyne:
If done properly, system should never need root access.

Keyword being 'if'.
[Samsung Galaxy Nexus] RogerPodacter:
Wow interesting, I just checked my super user, and sure enough system shows up. Then went to system panel and my system process is now using 105mb of ram. Remember earlier in this thread I had no issue. I'm now running aokp so I bet settings needs this access since I'm running status bar tweaks. Damn.

---------- Post added at 04:43 PM ---------- Previous post was at 04:42 PM ----------

My up time is 167 hours.
[Samsung Galaxy Nexus] adrynalyne:
I am using status bar tweaks (from a toolkit) without the need for system having root.

I don't use aokp though.
[Samsung Galaxy Nexus] RogerPodacter:
Yeah I used a modded systemUI on 4.0.1 to tweak my status bar, so technically I don't think thattype of method needed continual root access. But I'm not clear on how aokp is doing the status bar options from their rom control src etc so perhaps its possible continuous root is needed upon each boot to set the status bar tweaks I've selected. I really don't know.

I could always just change the systemUI code and compile my own transparent bar or something, but that's not as flexible and that couldn't capture everything like dBm. Poop and stuff. Maybe something else is causing this.
[Samsung Galaxy Nexus] T4rd:
Bumping for visibility.

After a day since denying root to "system", it seems to still be gradually growing in RAM usage. Sitting at about 106 MBs right now. I'm hoping it will plateau around there since that's about the amount other people are reporting it taking.

Please check your phones for the process and if it has root access in your Superuser app.

Thanks again :).
[Samsung Galaxy Nexus] RogerPodacter:
Mine is at 60mb right now. Rebooted yesterday and showed 48mb, then went down to 42mb after a few min. Now today its showing 60mb.
[Samsung Galaxy Nexus] adrynalyne:
Mine has been at 48.9mb for two days now.
[Samsung Galaxy Nexus] T4rd:
I just figured something else out that is causing "system" RAM usage to increase.

EVERY time I unlock/wake up my phone, it increases by ~1-1.5 MB. I just did it like 15 times in a row and it went from ~120 MBs to ~135 MBs in usage. I would leave System Panel open, turn off my screen, immediately turn it back on, unlock the phone and observe "System" RAM usage increase by around 1 MB. I left System Panel open so when I unlocked my phone, I would see it first thing when it unlocks and every time it raises "System" RAM usage by around 1 MB. I think I'm just going to sit here unlocking it now until my phone crashes and reboots, lol.

WTF.. someone please point me to a dev or help me out with this. I would just flash it back to stock or try a new ROM, but I would like to actually see what's causing this first if possible so I can avoid it from happening in the future.

Thanks again!

Edit: Alright, I just crashed my phone by constantly locking/unlocking it. It crashed right around when "System" got to 286 MBs of usage, then did a soft reboot (back to the boot animation as opposed to the Google screen with the lock at the bottom), then upon unlocking it went through the "Activation" setup where it just tells you to wait for a few seconds, then I hit the finish button to return to my launcher. After the crash it starts out at 48.9 MBs usage. Even right after a fresh reboot, System is exhibiting the exact same behavior of increasing in RAM usage after every unlock. Good stuff, eh?
[Samsung Galaxy Nexus] adrynalyne:
I tried that. It went up a few megabytes but ended up dropping.faster than I could get it to rise.
[Samsung Galaxy Nexus] T4rd:
Yeah, same thing on my Wife's Rezound, though it's stock and I wouldn't expect it to behave the same. I was just wondering where it should actually be and stay at, which seems to be around 50 MBs.

If you have any input on where I can post this issue so that active developers might have some good insight on how to trace this down, that would be awesome. I know this wouldn't be appropriate anywhere else in the G-Nex sub-forums, but I thought about registering on Rootz-Wiki or something and making a post there since most people here in the Q&A section aren't devs and probably wouldn't be able to track this down very well.

Thanks again.
[Samsung Galaxy Nexus] @rbiter:
What permissions are in your system folder?

zippity doo da.
[Samsung Galaxy Nexus] T4rd:
Please elaborate. You want me to list permissions for every folder/file in the system folder?

Thanks.
[Samsung Galaxy Nexus] RogerPodacter:
Well my system doesn't increase by locking unlocking the screen. Its staying at 64.5mb and won't budge, even hitting that refresh button just for good measure...
[Samsung Galaxy Nexus] @rbiter:
no. just the system folder. are all the permissions ticked and not supposed to be?
[Samsung Galaxy Nexus] adrynalyne:
Post in the thread of the rom developer. I am not stock, by the way ;)
[Samsung Galaxy Nexus] T4rd:
Not sure what they should be, but mine reads: rwxr-xr-x. Is that right?
[Samsung Galaxy Nexus] adrynalyne:
That is correct.
[Samsung Galaxy Nexus] RogerPodacter:
My system reduced its process foot print by itself, back down to 58mb from 67mb. Not too worried right now.
[Samsung Galaxy Nexus] sublimaze:
I posted this in the Liquid thread too. I have never encountered that problem, and I've tried just about every rom on this board. The fact that it happens on multiple roms suggests that it specific to your setup (including 3rd party apps or scripts), or your particular hardware. Since you ran stock for awhile without issues, it is less likely a hardware defect, and more likely due to something installed after flashing the rom.

Here's what I would do. Wipe everything (factory wipe, /system, /dalvik). Reflash rom. Log into google account and sync contacts, calendar, etc, but don't install anything else or alter the rom in any way (no scripts, themes, or modded youtube or other gapps) for a few days and see if the system still hogs memory.

Btw, system is not on my superuser list of apps asking for root access, and I don't ever recall seeing it there.
[Samsung Galaxy Nexus] cheapbeerbaron:
I have/had this problem too, from my very unscientific testing I think it was from a kernel not flashing correctly. I have used glados/franco's/lean and the problem persisted, then after flashing the same glados twice manually(same file) my system process seemed to behave itself for several days until I changed ROM and then flashed a new kernel again. I haven't been able to repeat this yet(not trying too hard to get rid of it yet) and from what I can tell it increases in size from apps being moved in and out of memory
[Samsung Galaxy Nexus] adrynalyne:
Kernels either flash or they do not. There is no in-between.
[Samsung Galaxy Nexus] T4rd:
Yeah, I was wanting to do that, but I also wanted to see if I could diagnose this before wiping so that I would be able to avoid it happening in the future or at least identify it easily. But I think that's what I'm going to end up doing.

I haven't installed anything outside of the ROM and kernel though. No scripts, mods, themes or anything else that modifies the OS/GUI outside of the options that Liquid gives you in the Liquid Control settings. I just flashed my ROM and Kernel (I stay on the latest LeanKernel releases), then restore everything with Titanium Backup (no System Apps of course).

So I was just planning on doing a full wipe in Recovery, then first thing when I get back into my phone is to load Titanium and System Panel. Then I'll see if the "System" process requests root and if it increases in memory usage after every unlock (as it's doing now). If it doesn't (which I would hope not since I'm still basically on a fresh ROM install), then I guess I'll have to individually install my apps and check for when this behavior returns by locking/unlocking my phone and monitoring the System service.

So it sounds like a PITA :(. Thanks for the response and input though.

Indeed. Plus I've flashed multiple kernels while this has happened. There's a new version of LeanKernel released at least every week and I always flash the new ones. I've tried one of the Franco Kernels too. So I don't think this is kernel related.
[Samsung Galaxy Nexus] @rbiter:
Do what? :banghead: :D

bow chicka wow wow.
[Samsung Galaxy Nexus] adrynalyne:
I think you are dealing with memory leaks from Liquid's code. You should tell him. BAMF Paradigm does not have this issue, using those same tests. So I would conclude that it is not an Android bug, but a bug from what was added in.
[Samsung Galaxy Nexus] T4rd:
Yeah, I'm guessing either that or a Kernel issue with LeanKernel at the moment. You would think that you would see lots of people complaining about this in their respective threads though and I haven't seen any of that even after posting about this issue and linking to this thread. I'm actually getting replies back saying they've tried locking/unlocking their phone and they're not seeing that issue. So I think it may be kernel related even though I've updated LeanKernel every week or so. I guess it's possible since it's the same dev, he left the same memory leak in the last few versions. I haven't posted in any of the LK threads to see if users are seeing this issue, but I have read the recent pages on them and don't see any reports of this. :confused:
[Samsung Galaxy Nexus] T4rd:
Bump.

I updated OP with a video I made to demonstrate how to replicate this.
[Samsung Galaxy Nexus] reyes.jr:
Hey I'm trying to see if I have the same problem so I downloaded system panel but I don't see a "system" application in "system panel" to monitor the memory usage? The only 2 things that have root access on my phone are Kernal and ROM manager.
[Samsung Galaxy Nexus] T4rd:
To see System process in System Panel, open System Panel, hit Menu > Settings > check the "System Process" box.

Thanks.
[Samsung Galaxy Nexus] reyes.jr:
K I did the lock/unlock thing on a quad lock screen and it went from 39.3 to 41 then back down to 39.5, back up to 40, then down to 39.4 again. So I do not have the same problem as you bro. I'm on Glados Kernel with Eclipse rom.
[Samsung Galaxy Nexus] T4rd:
Thanks for the info. I'm pretty sure it's ROM specific, I'm just amazed I haven't seen any other Liquid users report the same problem. But I guess most of them don't use that octo-lock screen like I showed in the video. I'm not sure if anything else triggers that memory leak though.
[Samsung Galaxy Nexus] reyes.jr:
No idea man..I loved liquids 1.1 rom but I kept having issues with his 1.25 rom so I switched to eclipse rom.
[Samsung Galaxy Nexus] T4rd:
Ok, I take it back. It seems pretty much all the devs reuse this same lock screen mod in all of their ROMs. I just replicated the bug on AOKP after a fresh wipe and install.

Watch my video here to see the bug in action and crashing the phone!
[Samsung Galaxy Nexus] petsasj:
Is this happening only on the Octo lockscreen or the Quad one as well?
[Samsung Galaxy Nexus] adrynalyne:
Try BAMF Paradigm.
[Samsung Galaxy Nexus] T4rd:
I just tested it on Liquids new 1.3 ROM and it didn't seen like the quad one triggered this bug. Before I switched to Octo, I tried quad just because I was curious about that too. But after having it on quad and configuring all 4 unlock points, it didn't seen to change system memory usage at all after several unlocks. So I then switched it to the Octo launcher and I immediately started seeing it increase by .5 MBs or so after every unlock. I took it up to about 70 something MBs, then switched back to the Quad lock screen and it still continued to increase after every unlock. So then I thought maybe it's because I still have all eight of the unlock points configured (because it saves those settings even if you switch back to stock, quad or anything else). So I changed all the points back to "blank" and even switched it back to the stock unlock screen. It still increased after every unlock even after switching back to the stock lock screen, even after a reboot too.

So I just did a full wipe in recovery to test the quad launcher again and I'll report back. I'm hoping it doesn't affect it because I would like at least 4 unlock points/apps. I'm really hoping that this octo-lock screen feature is the only thing causing this memory bug too because it's annoying to diagnose and work around these things.

Edit: Ok, I just did another full wipe in recovery and after booting back up it seems that the Quad unlock screen does still cause System memory usage to climb after every unlock, it just doesn't seem to climb quite as fast as it does when I have the Octo lock screen enabled. It was only increasing about .1-.3MBs after every unlock as opposed to the Octo unlock screen causing it to increase by about .5 MBs per unlock. So maybe I was thinking of the stock unlock screen before.

Now I'm going to wipe it again and not touch the lock screen features, do a full restore of all my apps/data and see if the phone will have any memory issues afterwords.
[Samsung Galaxy Nexus] RogerPodacter:
That just sucks that the lock screen can't be used now. Perhaps the devs can figure out a fix. But you'd have to convince someone to look into it.
[Samsung Galaxy Nexus] dandrown:
I have a fix for this and I've submitted it to AOKP. If other ROM developers need it, you can see the patch at AOKP's gerrit for frameworks_base, change I93779d41 or my github for CNA's android_frameworks_base, commit 5aaf393c4f8b68cfdbf83da893b1cff641143454 (I can't post the links due to insufficient post count).
[Nexus S General] Rengak05:
hi Folks.

ICS is now available for nexus s I9023 in india my friend received it yesterday its about 128 MB in size..

Cheers,

Renga
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] will89:
I flashed the clockworkmod for the first time. After that went back to menu by holding power + vol - but I can only see the usb icon and downloading icon. No recovery option. if I go into usb mode it just stucks there and on top bootloader: uknown. Anyone know what's up? I'm using the google IO tablet btw.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] richard2311:
Have you flashed the recovery or just booted it.....anyways

If you have got a rom with extended power menu you can reboot in recovery that way...

If not, get your recover.img and put it in a folder on pc.

go into fastboot mode (vol. down. / Power then select USB) and type :

Fastboot boot recovery <path>recovery.img

you could also try ROM manager...
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] alastyr:
No USB-boot

I got the exact opposite/same issue on my 10.1v,

I can only see the recovery and Downloading... icons and not fastboot.

See attachment for a screenpicture of what I get when pressing VolDown + Power.

Recovery, adb, and rooted ROM all work great - but fastboot aint an option...

Can't test isimobile's ICS-rom without fastboot :(

edit:

attachment buggered up.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] will89:
Thanks for the tips on using ROM manager. That solved my problem, finally able to try the CM9 Kangs rom
[General Questions and Answers] bigbaggie:
I must be missing something: in the past few days I've been looking around at how to unlock my xperia play r800a @ 2.3.4 and this is what I don't get..

The device is rooted and I can access all of the folders so can I flash a rom to my system with a script or program? I think it may be impossible since your flashing to the thing you're actually using at the time but I'm very new to this thing, technically...

Also, I understand that there are those who can create a custom kernel for my phone so it'll be unlocked, where could I find these people? I have my unlock code, imei, but the phone refuses to connect when powered off and the Search (or any other) button is held :mad:
[Galaxy Ace S5830 Themes and Apps] princeof:
Can any one port the so famous roise launcher to our cute ace,please...

i know,there are brilliant ones up here.... if we have a ported sense 2.1 itself here, why can't we do this.... i will be very thankful for your kind reply...Thank you
[Galaxy Ace S5830 Themes and Apps] wunghau:
It might NOT as easy as you think, as the launcher might require modification in framework.

I also hope that it could be ported and use in either stock/Cm7 rom:D
[Galaxy Ace S5830 Themes and Apps] princeof:
Thanks for your reply, Can't we modify our framework to suit this ....
[Galaxy Ace S5830 Themes and Apps] :
The sense launcher needs the sense framework, you would need a full sense port (there is one in the development thread). In any other rom you could only have themed launchers.
[Galaxy Ace S5830 Themes and Apps] SpaceCaker:
beats with smooth sense has 3.0 launcher mod :)

and i also shared sense4 launcher mod

and mre

unwritten sentance
[Galaxy Ace S5830 Themes and Apps] princeof:
Yup Beats with smooth sense is awesome.....

Space.... you are awesome toooo...
[Android Q&A, Help & Troubleshooting] Terramoto:
hey, i have a tablet for a while but i only gave it attention now and i wanted to root it but i cant seem to find drivers for it, this is the device

CPU	VC882 Embedded 1G ARM Cortex A8 3D, Aceleração 3D de OpenGL ES 2.0

memory	DDR3 512M

memory Flash	8GB

WiFi	Yes

UMTS/3G	UMTS/3G

GPS	No

Bluetooth	No

Câmara	Câmara 0.3MP

Gravity sensor	supports
[Nexus S Q&A, Help & Troubleshooting] AeroEchelon:
I recently purchased a dock for my Nexus as it provides easy access to incoming notifications, USB storage and doubles as a desk clock.

However, I've been reading mixed opinions on whether AMOLED screens or specifically the Nexus S screen can have burn-in or not. I would like to use my phone as a desk clock but not have any consequences to the screen after a year or so ...

Anyone use their Nexus S as a Desk Clock (for hours a day) and have you received burn in? Thanks!