yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] akira02rex:
I keep receiving hot reboots (not a full cold restart). I came from an odexed 4.2.1 STOCK OTA-based ROM from Bigxie. I did a full wipe before installing this. I also am receiving redraws of the home launcher every now and then when returning back to home from an application.

What I don't understand is, this ROM is based off 4.2.1 aosp, and the ota is the same thing right? What would be so much different to cause this big of an issue? I have the same, actually less, apps installed so I'm 99.999% sure that's not the issue here. Is it because I'm using tablet mode? The issue happens when the phone is literally just sitting idle or when I wake it up (for instance I tried touching the SMS app.. and boom it restarts).

And, please, don't tell me to reflash the ROM because it won't do anything. We all know a zip is a zip, and when it's extracted from CWM it will extract the same exact contents to the appropriate locations.. one flash won't do anything that another one could.
[Samsung Galaxy Nexus] zenitraM:
If I'm not wrong, your issue is due to the leak that happens after having locked and unlocked many times (exact same case as mine). system_process uses too much memory, Android starts killing processes (as the launcher) to save memory.. until finally system_process exhausts all the memory and crashes, leading to a hot restart.

This is probably due to the changes introduced to allow custom widget targets or something alike that.

Try what I said, lock and unlock lots of times in a row, it will end up getting sluggier faster. Disable lock screen completely and reboot (or force a hot reboot by killing system_process), everything is fine again.
[Samsung Galaxy Nexus] cocchiararo:
you missed my last post.

issue IS there.

it seems that since i have it setup to auto lock after 5 minutes, and i don't manually lock it while im home or @work, i didn't notice it before.

I did find it weird that today when i woke up i had only 4 programs in "cached memory".

It seems that the more memory is leaked with the issue you found, more stuff gets unloaded from memory.

Eventually, performance issues/lag will appear, its just that i did not see it because i don't lock/relock that often as you said.
[Samsung Galaxy Nexus] gautam_nexus:
all these bugs are from AOSP and not PA...hope moles or dark maybe able to fix it...
[Samsung Galaxy Nexus] Nephilim:
I'm sorry but you really should just stick to stock Roms because you obviously don't know much about flashing. It is an issue on your end not the ROM, nobody has posted anything similar to this so nobody else has encountered it but you. You understand what that means? Its something you did or installed. Did you dirty flash from a ROM below the 2.99 builds? Something is causing it because the only known issue on the latest beta is memory leaks, which cause low ram and lead to extreme lagging when the device is not rebooted frequently. The only help anyone is going to give you is to clean install the ROM after a factory wipe. If you don't like that, I'm sorry. I also apologize if I sound rude, I don't mean to be. You just seem to insistent that the issue is exclusively paranoidandroid when its 99.999999% not likely. Also, its a beta, if you want a perfect ROM download a stable one ;)

Sent from my AOSPA Galaxy Nexus
[Samsung Galaxy Nexus] zenitraM:
Oh, okay, then it seems everyone has it so far (if anyone doesn't suffer this, raise your hands!) and we can conclude it's a PA issue.

The fix might be simple, probably removing the commits for lockscreen targets will solve it for the time being.

They aren't from AOSP, if they were all AOSP roms would suffer from this and they don't.

The issue he has is the memory leak. All of what he explains is caused by it and can be explained by it, I know, because I've suffered it and had the same issues. If you have a lockscreen and lock and unlock too many times in a row, you'll also see it happens.
[Samsung Galaxy Nexus] Nephilim:
Quote, he is describing way more than the normal memory leak lag issues. Something was not installed properly.

Sent from my AOSPA Galaxy Nexus

---------- Post added at 09:37 AM ---------- Previous post was at 09:32 AM ----------

I just tested your theory and you're right about the memory degradation but not once has it gotten to the point of the phone rebooting from just opening an app..

Sent from my AOSPA Galaxy Nexus
[Samsung Galaxy Nexus] zenitraM:
Memory leaks -> too much memory being used (and less free memory).

Lack of memory -> Android kills background running/cached processes to free memory -> Android kills the launcher -> Launcher gets redrawn when it's brought back to foreground.

Too many memory leaks due to having locked and relocked too much -> system_server crashes.
[Samsung Galaxy Nexus] Nephilim:
I am not computer illiterate, I don't need a tutorial on how memory works ;)

I'm just pointing out that he has more than just the memery leak issue going in and I'm not changing my mind because I tested the lockscreen theory. It only created lag, not instant reboots. Also, not once has my launcher been killed either.

Sent from my AOSPA Galaxy Nexus
[Samsung Galaxy Nexus] tjackbjorn:
Is it possible to change the navbar icons in this rom? :)

Sent from my super fast Prime filled with beans.
[Samsung Galaxy Nexus] Nephilim:
I think the only current way is to go into the systemui.apk and manually switch them in the res folder.

Sent from my AOSPA Galaxy Nexus
[Samsung Galaxy Nexus] cocchiararo:
you just need to lock and unlock further to see more issues then :P
[Samsung Galaxy Nexus] thagringo:
ok, was bored and just tested this with beta7 on my gnex and i can reproduce it indeed : un+locking the thing many many times ( havent counted them but maybe 40+ times) makes the thing memory hungry.

I think i even got it to the point that oom kicked in and started to kill tasks, apex was killed while i was suing it for example ... at least i got a hot reboot after a while too.

Havent yet tried to get a logcat, still trying a few things.

cheers
[Samsung Galaxy Nexus] MrBlackbriar:
I just tested the lock-unlock leak myself, kept locking/unlocking, and got to a hot reboot.

root@android:/ # top -m 1 -s rss -n 1

User 1%, System 5%, IOW 0%, IRQ 0%
User 8 + Nice 0 + Sys 21 + Idle 384 + IOW 2 + IRQ 0 + SIRQ 0 = 415

PID PR CPU% S #THR VSS RSS PCY UID Name
392 0 0% S 84 633004K 140868K fg system system_server
root@android:/ # top -m 1 -s rss -n 1

User 2%, System 1%, IOW 0%, IRQ 0%
User 15 + Nice 0 + Sys 10 + Idle 572 + IOW 4 + IRQ 0 + SIRQ 0 = 601

PID PR CPU% S #THR VSS RSS PCY UID Name
392 1 0% S 83 614332K 245488K fg system system_server
root@android:/ # top -m 1 -s rss -n 1

User 55%, System 15%, IOW 18%, IRQ 0%
User 334 + Nice 6 + Sys 95 + Idle 60 + IOW 115 + IRQ 0 + SIRQ 0 = 610

PID PR CPU% S #THR VSS RSS PCY UID Name
392 1 3% S 84 617676K 338176K fg system system_server
root@android:/ # top -m 1 -s rss -n 1

User 18%, System 13%, IOW 26%, IRQ 0%
User 115 + Nice 0 + Sys 85 + Idle 251 + IOW 159 + IRQ 1 + SIRQ 0 = 611

PID PR CPU% S #THR VSS RSS PCY UID Name
8614 0 0% S 4 117792K 109960K fg graphics /system/bin/bootanimation

So yes, I'm quite sure his hot reboots are also caused by this issue.
[Samsung Galaxy Nexus] Nephilim:
I did it for almost 5 straight minutes and none of those things happened except extreme lag.

I think we all can agree though, something is terribly wrong with beta 7's memory. I have decided rather than to argue in circles I'll just chalk it up to different devices behave differently to the memory leak. ;)

Sent from my AOSPA Galaxy Nexus
[Samsung Galaxy Nexus] cocchiararo:
or you can read and accept the same thing from like 4 (or 5 if we count the user you sent back to stock rom...).

Unless you missed all the post between your last one and my post before this one.

What we know:

1) issue introduced on beta 7

2) locking/unlocking leaks memory

What was new on beta7:

1) lockscreen targets

2) any widget on lockscreen

I believe there is little doubt either one of those features, both of them, or "backstage stuff to make them work", are the culprits.

And the issue is present on builds made AFTER beta7 too.

----

And no, different devices behave "the same" if they have the exact same stuff installed. Its pretty imposible for that to happen tho, so they SEEM to behave differently.

Its easier for me to trigger the bigger issues, since i boot with just 200mb unused (i run a lot of stuff, no issues tho).

People who boot with 300+, are in a "safer position".

Its great that this was found tho, since every dev, and MOST users (me included) did not suffer from this on normal use.

----

EDIT: ok, this post didn't take into account overclocking. That, does have the chance of working differently on 2 completly identicaly configured devices
[Samsung Galaxy Nexus] alfiemenace:
Why is it that after I deselected that option, nav bar still isn't transparent :(

Stock ROM, custom user.
[Samsung Galaxy Nexus] Nephilim:
It's all good, what I meant in my last post was that I agree the issue is present and I do not want to argue what symptoms arise on different devices because I do not have those problems, just the extreme lag on apps after the phone drops below 80mb. It might be that I am using a different kernel, it might be my settings are different but after doing the lockscreen test I still do not get the hot reboots or launcher kills. Just sayin' ;)
[Samsung Galaxy Nexus] akira02rex:
I'll excuse your ignorange this once, but pardon me.. are you an idiot?

It looks like my question has been answered, thanks for posting about the memory leak issue guys - it all makes sense now.

And, how can one not install a rom correctly? You don't technically INSTALL anything.. you click a friggen button and Recovery installs it all for you. This isn't Active Directory or Exchange 2010 and having to manually install the system roles yourself bro. Geez Luis!

---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------

I use PGM Nexus (but I also did with stock ota and no issues) if that makes any difference. I text a LOT.. to the point I get the stupid warning message a LOT thus you can imagine how much I unlock/lock my device.
[Samsung Galaxy Nexus] Nephilim:
The only ignorant one is the person whom talks disrespectfully to everyone in order to get their point across, you proved this with your response to me and the initial comment you made about the rom having issues. There is a right way and a wrong way to address things and being as I went out of my way to tell you I was in no way being rude I think you are doing it the wrong way. Every device reacts differently to issues because of kernels, apps, settings etc. Until you posted your overwhelming issues nobody else said a thing about having any issues that drastic, this lead me to believe that you had improperly installed the rom. No need to bring up "Active Directory or Exchange 2010" as if I am a 14yr old kid that does not have computer knowledge, there IS a improper way to install the rom, some people do not read the OP and have flashed 2.99 over 2.54 which caused many issues due to one being CM based and the othe 4.2 AOSP based, that is an example of a WRONG way to install a rom so YES as you can see there IS a wrong way.

Now again, not trying to be rude but when you begin namecalling it's hard to not get a little frusturated. I guess the issue just arose due to lack of people coming forth with the extreme degree of issues that you have until after you posted yours. ;)
[Samsung Galaxy Nexus] akira02rex:
Bravo - I "Thanked" your post.

<sarcasm>On a side note, I performed some voodoo magic, as they call it, and installed each and every file manually on to my phone and it's beautifully working now. </sarcasm>
[Samsung Galaxy Nexus] zephyr1100:
per app navbar transparency and colorizing are PA features which stock ROMs don't have afaik. So your navbar remains as is. The NovaLauncher option I mentioned cannot make anything transparent. It only saves the wallpaper from being cropped at the navbar's centerline what made screen look ugly using PA transparency before.

Sent from my Paranoid Nexus
[Samsung Galaxy Nexus] Nephilim:
Thank you for labeling the sarcastic point of your post, I was having trouble with it. :p

Lol, anyways, I would thank your post as well but sadly I have used my 8 for the day. (lord knows why we are limited in giving thanks to people.)
[Samsung Galaxy Nexus] D4rKn3sSyS:
I need to confirm this, all the people who has lag since beta7, have you added custom widgets on lockscreen?

EDIT: Though is really weird, I use a few custom ones and no lag at all, perhaps there are a few bad widgets wich arent being destroyed?
[Samsung Galaxy Nexus] Lapiduss:
I confirm that the memory leaks with beta 7 are solved disabling the lock screen.

Andoid system usage (checked with Android system info) remain under 70Mb instead of 340Mb after a few hours. The cause of the problem apparently was not swiftwey flow..
[Samsung Galaxy Nexus] 87Cocaine87:
I have not added widgets. I gave up and went back to 6. It works great plus I installed trinity alpha 7
[Samsung Galaxy Nexus] Lapiduss:
I disabled all the widgets in the lock screen and the problem remained, just turn off and turn on the screen 20 times to have the memory problem..
[Samsung Galaxy Nexus] curious_yellow_eyes:
I've added ONE widget, and do not suffer lag.

HOWEVER what I have realised while reading the last few pages, is that I don't actually lock all that often. I've set to not lock on sleeping until a few seconds after the screen goes off, so while my phone is in use it doesn't actually lock at all, until I'm done with it. My launcher does redraw most times when I press the home key though, although that may be normal behaviour since I don't press it all that often and the launcher is several apps from the back, so to speak.

Edit: I should mention that I have no targets added.

Edit 2: the lock screen with the widget is switched to be the "main" one, don't know if that makes a difference. Also, I do have "calendar" on another lock screen but I never swipe to it.(that's why I forgot it ) and it's a "stock" widget
[Samsung Galaxy Nexus] bhavin23:
I get gps lock instantly but my position changes around original location(within 20-30 mtr) while i am idle.So tracking sw records quite inaccurate route. (Tried both endomondo and my tracks).
[Samsung Galaxy Nexus] D4rKn3sSyS:
I'm really bored of turning on and off screen multiple times, and scrolling, adding and removing lockscreen targets (even removed the cap for testing,and adding 25 icons, it still doesnt lags at all). I really have no idea whats causing the lags, and can't replicate the issue.
[Samsung Galaxy Nexus] MrBlackbriar:
I had the issue both with launch shortcuts enabled and custom widgets allowed (though none were actually used) and without launch shortcuts and the option disabled.
[Samsung Galaxy Nexus] D4rKn3sSyS:
This is what I mean, is really weird. It could be an issue with incomplete GCC or some bionic stuff (aaron has been messing around it), or something evil on older builds. I can't reproduce it on our actual environment, so hopefully whatever it was, is fixed for next version.
[Samsung Galaxy Nexus] aaronpoweruser:
New gcc 4.7 test build, this is the version that will be merged into beta 8 should be a lil faster than the last one. https://docs.google.com/open?id=0B_q...kVTLUdaUGlmaTA
[Samsung Galaxy Nexus] cocchiararo:
I have beautifull widgets added, and removed the stock clock one. (beautifull widgets has official lockscreen support)

i have NO LAG.

But its a FACT that the system process keeps getting bigger and bigger (thats what you must test, not search for lag).

I re tested beta 7 and december 7 dev build, both have it.

i did not go back to b6 to test it, but i did test the first fully working build that aron posted today, and the memory issue is there too.

newer than the last one you posted ? EDIT: error, not found (broken link?) EDIT2: the url link has the "..." instead of the full address xD
[Samsung Galaxy Nexus] DaD92:
It may be launcher related too. User users with lag use alternate launcher, no stcok (if I remember correctly)...
[Samsung Galaxy Nexus] 02ranger:
I have experienced the lag too. After flashing beta7 I thought everybody was nuts that reported lag issues, but after I started fiddling with third party widgets the lag started. I've used three different widgets, a digital disc clock, Zooper widget, and the stock messaging/SMS widget. Each at different times, but never more than one widget at a time. With the messaging widget I never saw any lag, but did with either of the other widgets. It has taken literally 7 seconds from when I hit lock to hear the lock sound (I counted) at times, but its fast when just rebooted. The screen always turns off nearly instantly, just doesn't lock. I haven't done anything with lock targets, just widgets. If you need any other info I'm happy to get it, logs or whatever. Hope this helps.

On another note, I'm thoroughly addicted to PA now. lol. I thought "what's the big deal here?" at first, but after playing with tabui and hybrid PAprefs some, I don't foresee any other ROMs in my future. Thanks for all your hard work, everybody involved!!
[Samsung Galaxy Nexus] Lapiduss:
Ho Mb is your Android system process after screen turned off and on several times?

(Thank you for your time!)
[Samsung Galaxy Nexus] D4rKn3sSyS:
Yes, I'm with eclipse tools debugging, so far it looks normal, and none of my widgets cause neither lag or system proccess getting bigger.

EDIT: Lapiduss where do I look that on phone?, on RAM meter in settings, I get 328mb free (that's even too much, I guess) after unlocking and relocking a thousand of times. Anyway, on eclipse, it doesnt shows that warnings on screenshot shown a few pages ago.
[Samsung Galaxy Nexus] cocchiararo:
hopefully you or someone fixed the issue without noticing :P
[Samsung Galaxy Nexus] zenitraM:
Then it might be fixed, I don't know. What I used to debug it was:

-used tools/monitor on android SDK to dump the heap profile for system_process

-converted the hprof file to Eclipse-compatible format using tools/hprof-conv

-opened the converted hprof with Eclipse Memory Analyzer Tool http://www.eclipse.org/mat/

-made it check for leaks

-got this:

the more I opened the lockscreen, the more instances were there.

No custom widgets were involved, just opening one and another time the lockscreen.
[Samsung Galaxy Nexus] cocchiararo:
there is an app called "memory usage" that you can use.

there was also a command line way of doing it (with top) that was posted pages back.

but memory usage should be fine
[Samsung Galaxy Nexus] D4rKn3sSyS:
Could you run the exact same test on a pure AOSP build?
[Samsung Galaxy Nexus] Lapiduss:
I use Android system info, tab task
[Samsung Galaxy Nexus] zenitraM:
I can't now :/

Anyway the usage is too obvious, after 20 times or so it went from 100mb up to 200mb. If you don't see an increase on memory usage, then it might be already fixed somehow.
[Samsung Galaxy Nexus] D4rKn3sSyS:
Certainly when on settings panel and locking/unlocking I got low ram and a hot reboot (though, took me about 50 unlocks). I reverted lockscreen targets / widgets but that's not it. I will reset to a very old head frameworks, so we can either discard it or find the culprit commit (I think the issue is not on framework, in wich case, we will have to start checking build tools).
[Samsung Galaxy Nexus] cocchiararo:
no one complained about this issue on b6, i can't test it now tho :(
[Samsung Galaxy Nexus] Nephilim:
+1, never had a single problem on any of the 2.99 Betas until 7, My memory on Beta 6 and below was predominantly above 200mb and never got below the 160's, more than not it was in the 270's even with 145+ apps, now it starts at the normal 300+ and drops after full boot to the 280's or so but consistently keeps dropping just as what has been discovered by you guys after the lockscreen test, once it hits 80mb it starts lagging and I can barely type without freezing on the keyboard and apps opening and closing with issue. This is when I reboot and start the process over.

Before you guys mentioned the lockscreen issue I figured it was just something that happened over a period of time but now it makes sense why sometimes it takes up to 7hrs for lag when I'm not really using my phone much but other times it gets bad after only an hour or so (which is usually because of heavy usage and locking/unlocking)
[Samsung Galaxy Nexus] drafgnjom:
Maybe they don't know/notice this issue until someone reported it at beta7.
[Samsung Galaxy Nexus] anthonyp326:
The lag occurs after time of use..like 8 hrs
[Samsung Galaxy Nexus] DaD92:
same here... It take several hours...
[Samsung Galaxy Nexus] Nephilim:
Nope, it's been proven in the last few pages that the lag occurs from repeated locking and unlocking of the lockscreen. Try it out yourself if you like. This is why sometimes it seems the lag takes along period of time but others it takes only a short amount. ;)
[Samsung Galaxy Nexus] cocchiararo:
This appeared way too fast on b7, hard to think it was there before, but only testing will tell.

nope, it happens after "x number of lock/unlock cicles" :P

Well, i admit that i had no lag tho, only noticed memory getting more and more used.
[Samsung Galaxy Nexus] molesarecoming:
anyone has a hint for a somewhat stable gapps package that has all of the important tidbits working? im preparing stuff for b8 and it would be nice to be up to date on that end too as we're coming closer to 3.0
[Samsung Galaxy Nexus] 02ranger:
It really seems to depend on how much you lock/unlock your phone. I rebooted mine before going to bed last night and all was good 8 hours later. After about an hour of use it lagged. I disabled the lock screen a little while ago and now it runs perfectly. But it looks like d4rk is on it now so I'm confident he and the PA team will find the culprit. I would advise disabling lock screen if you don't really need it, or revert to beta6 since everybody seems to not have problems on it.

Thanks again PA team!!

Edit: Looks like a couple people beat me to the punch on this post. lol
[Samsung Galaxy Nexus] drafgnjom:
Just days after the betasix was released and the betaseven came. Maybe that's why?
[Samsung Galaxy Nexus] cocchiararo:
The one from goo is fine (but lacks all the extras, that are present on the market anyway).

No pack has backup available.

If you still want to include all that stuff, take the last package you used, and add the libs for gtalk to it.
[Samsung Galaxy Nexus] EvilDobe:
The 11/30 gapps on goo.im have been working great for me. Worked fine when I flashed them with beta 7 as well.
[Samsung Galaxy Nexus] cocchiararo:
and in minutes/hours the issue appeared :P

"days" was plenty yime for it to be found before, i think xD
[Samsung Galaxy Nexus] Nephilim:
+1, this, I agree. Also, you could merge any updated apks that are in the goo.im gapps package into the OP gapps package.
[Samsung Galaxy Nexus] molesarecoming:
awesome then. i think im going to take a look at navbar size now, it was a much requested feature but i dont know if i can make it until deadline.