Develop Bugs

[Q] Is ICS on HOX killing apps for no reason?

I have found that my One X often kills apps I have running when I press the power button and put it away for more than a few minutes. I know Android will try to reclaim resources starting with background apps but this is killing the app I am currently looking at.
I have almost nothing else running and my system normally has 200-300 mb of available memory so it is a very unexpected behaviour. A typical example is I have something like firefox displaying a page. I read a bit then press off. I come back 10 minutes later and it needs to restart and reload the page. With previous phones the app would still be in the foreground the next time I turn it on and unless I navigate away it would stay that way.
I have a nexus s running ICS and that does not happen.
I have a desire running GB and is doesn't hapen.
I have a desire running Froyo and it does not happen.
Is there any way to force a less aggressive memory management on HOX?

There is an option for this, in settings > developer options, furthest down under apps section, first one; "Don't keep activities" check if it is enabled.
Sent from my HTC One X using xda premium

.. also beneath it, there is a restriction "Background process limit", it may also cause immediate kills if "no background process" is set
Sent from my HTC One X using xda premium

Thanks for the suggestions but those were set normally.
Tried using the built in browser instead of firefox and the problem was significantly reduced. It seems the system has a bias against non google apps. Even so - this HOX is behaving different in this respect to my other phones. It is my expectation as a user that if I am doing one thing, that thing should still be there the next time I look at my phone.
Something on the device may be leaking and the result is this need to stop stuff. My money is on sense ( mainly because of the observed ripple/flicker on the home screen ).

I've noticed same with my new one x it seems over eager killing all apps even sense launcher.
settings are correct but using chrome I don't dear open anything else for fear of it closing chrome and having to log back into everything, sometimes its as bad as just answering call or replying to a text message and its been killed
just as annoying it even kills launcher if I press home after using an app for more than a few minutes I get the please wait spinner while it has to load launcher
had ICS on desire HD and on zoom tab... this is not how it should work can't believe a phone with more memory and designed to run ICS is having to kill everything when DHD runs perfect
annoying little thing that is so far ruining what is otherwise an amazing phone

Seeing the same issue on my One S.

This happens with Dark Meadow. If the screen times out, or you hit the lock button, the game kind of "crashes". Not sure if this is the One X killing it or whether it's how the app is coded.
It's irritating anyway ><

Applications with a notification icon have not this behavior. Is there a possibility to set a higher priority to applications without root?

I'm having the same problem.
With cm9 @ Desire Z, I could, say, restore my 3000 sms within GoSMS (which takes a while) and meanwhile do whatever I wanted with the phone, eg. browsing, texting and so on.
With the H1X, after a certain time, the apps gets killed/suspended and therefore anything that happened within the app - which is pretty annoying. Any solution in sight?
H1X @ ARHD

I get this too. Annoying.

ViaraiX said:
I've noticed same with my new one x it seems over eager killing all apps even sense launcher.
settings are correct but using chrome I don't dear open anything else for fear of it closing chrome and having to log back into everything, sometimes its as bad as just answering call or replying to a text message and its been killed
just as annoying it even kills launcher if I press home after using an app for more than a few minutes I get the please wait spinner while it has to load launcher
had ICS on desire HD and on zoom tab... this is not how it should work can't believe a phone with more memory and designed to run ICS is having to kill everything when DHD runs perfect
annoying little thing that is so far ruining what is otherwise an amazing phone
Click to expand...
Click to collapse
Sense launcher closing is not cos of the over-aggressive app killing. It's cos the system needs more RAM, so closes Sense since it's not directly in use right now. I do notice that some apps are getting closed after a period of inactivity, probably a default ICS setting that we can tweak when kernels and ROMs get more mature releases

I'm suffering from this defect as well. It's frankly astonishing that this phone behaves in this way. Really makes you wonder if anyone actually uses the phones before releasing such junk. What use is such fantastic hardware if it performs so badly in real use conditions. Every time I press home, loading. Try to run some javascript Web pages then go send a text, then back to browser and all tabs have to refresh. Mine is going back if it doesn't get fixed pretty quickly as it's practically unusable in this state. Battery is unsatisfactory as well. 2 hours on battery, screen on for an hour, 57% left?! What are they thinking seriously

harryshepard said:
I'm suffering from this defect as well. It's frankly astonishing that this phone behaves in this way. Really makes you wonder if anyone actually uses the phones before releasing such junk. What use is such fantastic hardware if it performs so badly in real use conditions. Every time I press home, loading. Try to run some javascript Web pages then go send a text, then back to browser and all tabs have to refresh. Mine is going back if it doesn't get fixed pretty quickly as it's practically unusable in this state. Battery is unsatisfactory as well. 2 hours on battery, screen on for an hour, 57% left?! What are they thinking seriously
Click to expand...
Click to collapse
If your battery is that bad you have a bad app running rampant or your battery is faulty.
For everyone else, even in settings if "Don't keep activities" is unchecked, try checking it and unchecking it. I read that sometimes it is still set to "Don't keep activities" even if it is unchecked and checking and unchecking it could solve the problem if this is the case. Doesn't hurt to try.

Hopefully one of the devs will make a Rom/kernel with better oom adjustments... I'm hoping.

the multitask implementation on this phone is terrible. I was using runkeeper, stopped to check something in my settings during the ride, phone closed the runkeeper application deleting my ride. It is getting annoying ...

Screen wake lag - Let's solve this thing

EDIT: According to garyd9, this is an Exynos issue and cannot be fixed. I believe him that this is an Exynos issue because it supports what I've seen, and he's a smart guy. I'm still holding out hope that there is some possible resolution in the future. Why else are we here if not to find ways to make our phones better, right? However, because of the nature of this issue, it's not going to be resolved by app settings, disabling apps, etc. If you don't see the lag yourself, it's because your phone isn't in deep sleep when you try to wake it.
Original Post:
Alright guys, some of you have probably noticed that this phone suffers from the wake lag that others (all Samsung?) have also suffered from.
Symptom: When you press the power or home button it takes 1-2 seconds before the screen turns on.
This DOES NOT happen when the phone is plugged in, likely because the problem is a delay getting the phone out of deep sleep. Deep sleep does not occur while the phone is plugged in.
Culprit: Anybody know? My wife's AT&T GS2 has this same problem and has with every ROM/Kernel combo I've tried (AOSP, AOKP). My Skyrocket has the issue on some of the more recent versions of Sky Jelly Bean, which I believe Sean said was a Kernel problem.
Fixes that don't work: This morning I tried the most popular suggestions:
Turn off Lock Screen Popup note
Lock Screen Ripple Effect
S-Voice home key
S-Voice Auto-start speaker
S-Voice wake up command
NONE OF THESE WORK!
So, let's band together and solve this thing. Do some tests and find something that works. Preferably, a solution that takes as little modding as possible.
Is this something that can only be solved by a customer kernel? If so, let's see if a dev is up to the task!
EDIT TO ADD: This seems to be an issue on all variations of this device. I'm searching their forums for an answer, but don't see one yet. I decided to post this here to get more eyeballs on the problem
More info from Entropy512:
Entropy512 said:
To be more detailed: It seems to be specific to how Samsung wires up the modem interfaces of Exynos devices. On Exynos4 devices, they're always hung off of HSIC (a variant of USB) buses. Since HSIC is based on USB, it has the same slow suspend/resume of USB. Almost all Exynos3 devices hung the modem off of a serial port if I recall correctly, and these devices could suspend/resume much faster. If you look at a resume sequence, there are huge time gaps, and after the first 200-300 msec, almost all resume activity is modem stuff.
The only solution, unless someone figures out a way to make the HSIC resume faster (I'm not messing with it, I have enough trouble getting it not to drop the bus randomly!!!!!!!), is to inhibit deep sleep with a wakelock - but this will be bad for battery life.
Click to expand...
Click to collapse

Jrockttu said:
Alright guys, some of you have probably noticed that this phone suffers from the wake lag that others (all Samsung?) have also suffered from.
Symptom: When you press the power or home button it takes 1-2 seconds before the screen turns on.
This DOES NOT happen when the phone is plugged in, likely because the problem is a delay getting the phone out of deep sleep. Deep sleep does not occur while the phone is plugged in.
Culprit: Anybody know? My wife's AT&T GS2 has this same problem and has with every ROM/Kernel combo I've tried (AOSP, AOKP). My Skyrocket has the issue on some of the more recent versions of Sky Jelly Bean, which I believe Sean said was a Kernel problem.
Fixes that don't work: This morning I tried the most popular suggestions:
Turn off Lock Screen Popup note
Lock Screen Ripple Effect
S-Voice home key
S-Voice Auto-start speaker
S-Voice wake up command
NONE OF THESE WORK!
So, let's band together and solve this thing. Do some tests and find something that works. Preferably, a solution that takes as little modding as possible.
Is this something that can only be solved by a customer kernel? If so, let's see if a dev is up to the task!
Click to expand...
Click to collapse
I'm not feeling major sleep lag on att , Sprints on the other hand was pretty bad with 2-3 sec delay

Simple soft locker from market... doesnt seem to effect battery. Try it out works great
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

u921333 said:
Simple soft locker from market... doesnt seem to effect battery. Try it out works great
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
The app creates a partial wakelock, so it will affect battery. A wakelock will keep the phone from going into deep sleep, which is what extends Android phone battery life. With such a large battery, it won't be as noticeable on this phone, but it still has substantial negative effects.

sling said:
I'm not feeling major sleep lag on att , Sprints on the other hand was pretty bad with 2-3 sec delay
Click to expand...
Click to collapse
I'm getting about 2 second lag on both mine and my wife's AT&T N2s. Mine is rooted, hers is not.

Jrockttu said:
Alright guys, some of you have probably noticed that this phone suffers from the wake lag that others (all Samsung?) have also suffered from.
Symptom: When you press the power or home button it takes 1-2 seconds before the screen turns on.
This DOES NOT happen when the phone is plugged in, likely because the problem is a delay getting the phone out of deep sleep. Deep sleep does not occur while the phone is plugged in.
Culprit: Anybody know? My wife's AT&T GS2 has this same problem and has with every ROM/Kernel combo I've tried (AOSP, AOKP). My Skyrocket has the issue on some of the more recent versions of Sky Jelly Bean, which I believe Sean said was a Kernel problem.
Fixes that don't work: This morning I tried the most popular suggestions:
Turn off Lock Screen Popup note
Lock Screen Ripple Effect
S-Voice home key
S-Voice Auto-start speaker
S-Voice wake up command
NONE OF THESE WORK!
So, let's band together and solve this thing. Do some tests and find something that works. Preferably, a solution that takes as little modding as possible.
Is this something that can only be solved by a customer kernel? If so, let's see if a dev is up to the task!
EDIT TO ADD: This seems to be an issue on all variations of this device. I'm searching their forums for an answer, but don't see one yet. I decided to post this here to get more eyeballs on the problem.
Click to expand...
Click to collapse
I have everything that you have listed except Turn off screen popup mode & I have no lag at all.

It's a side effect of the exynos SOC. You can't "fix" it. It just takes about 800ms to wake from deep sleep.

garyd9 said:
It's a side effect of the exynos SOC. You can't "fix" it. It just takes about 800ms to wake from deep sleep.
Click to expand...
Click to collapse
800ms???? No way can I wait that long lol jk
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

garyd9 said:
It's a side effect of the exynos SOC. You can't "fix" it. It just takes about 800ms to wake from deep sleep.
Click to expand...
Click to collapse
Bummer.

Jrockttu said:
The app creates a partial wakelock, so it will affect battery. A wakelock will keep the phone from going into deep sleep, which is what extends Android phone battery life. With such a large battery, it won't be as noticeable on this phone, but it still has substantial negative effects.
Click to expand...
Click to collapse
I have used it on my galaxy s2 and my international galaxy s3 without seeing any negative battery issues. Now granted it has to have some effect but even with the not so great life on s2 wasnt noticeable. Try it out and see if it works for you. I was skeptical at first.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

It is in fact S-Voice.. completely remove it from the Note and you will remove the lag.. this has been an issue with virtually every device with S-Voice... I bet there will be a bebloated ROM come along in the next day or 2 and itll fix it.
Sent from my SAMSUNG-SGH-I317 using xda premium

I dont but I do know my galaxy s3 had it even when I was on aokp.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

daddymatt said:
It is in fact S-Voice.. completely remove it from the Note and you will remove the lag.. this has been an issue with virtually every device with S-Voice... I bet there will be a bebloated ROM come along in the next day or 2 and itll fix it.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Like the poster above this says, my wife's Galaxy S2 has the lag on AOKP and AOSP based roms that do not have S-Voice. As much as I don't want to believe it, Gary is likely right that it's an exynos issue. I was just hoping that it could be solved through a kernel.
Tested it for ****s and giggles, definitely not S-Voice. I disabled it and restarted phone. Let it settle about a minute from start up, opened BetterBatteryStats to CPU state screen and looked at the "deep sleep" state. Turned screen off for a few seconds, lagged, checked deep sleep state to make sure it had increased (ensuring it was recovering from deep sleep). This is the simple method to test any of these supposed fixes that people say will solve the laggy wake.
Anybody that says their phone doesn't lag when they wake up the screen is likely because they're looking at it while they're charging it, they're playing music, they have an active notification, or they're turning it off and back on really quick. All of these prevent the phone from deep sleeping. Deep sleep is what causes the issue.

I had lag on my Note I whenever it would deep sleep on any Rom. This only happened when I had Wi-Fi off when sleeping. When I turned Wi-Fi on all the time lag was gone. Not a clean battery friendly fix but the lag was driving me crazier than charging the battery a little sooner.
Sent from my GT-N7000 using Tapatalk 2

I have the att version and I was just wondering...the same thing...I am willing..to try anything...I mean it sucks just waiting a little bit. I was just waiting for a new rom

daddymatt said:
It is in fact S-Voice.. completely remove it from the Note and you will remove the lag.. this has been an issue with virtually every device with S-Voice... I bet there will be a bebloated ROM come along in the next day or 2 and itll fix it.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I would have to say this is true. I've seen people do this in videos and it seems to work. They say its the wake looking and checking to see if you held the button or double clicked it that will solves this problem. Are there any other settings that control the home button settings like how you show recent apps or s-voice?

http://www.youtube.com/watch?v=UHMIxBUclh0&feature=plcp

truth77 said:
I would have to say this is true. I've seen people do this in videos and it seems to work. They say its the wake looking and checking to see if you held the button or double clicked it that will solves this problem. Are there any other settings that control the home button settings like how you show recent apps or s-voice?
Click to expand...
Click to collapse
The only thing disabling S-Voice does is make your Home key work faster once the phone is already on because it's not waiting to see if you're double tapping it. S-Voice has no impact on the wake issue.

Mj23foreva said:
http://www.youtube.com/watch?v=UHMIxBUclh0&feature=plcp
Click to expand...
Click to collapse
That's the first thing I watched this morning when investigating this issue. If you notice, his "fix" doesn't seem to work that well for him. Try it yourself, it won't work. That's why I put it in the OP that these don't work.

No lag here and the phone's been in use/running for 24 hours now.

[Q] Why is my HTC One M8 stuttering?

I have an htc one m8 with android 5.0.1 (lollipop). I am experiencing some stuttering issues. For example, in the app drawer when I scroll up and down for a certain period of time slowly (like for a 1 minute or so), there will be a glitch/stutter where the scroll quickly and automatically goes to next page (it is almost like the app drawer just blinked and refreshed but it shouldn't be doing that right?). After that stutter/glitch then no more glitches/stutters occur.
It usually happens when my cell signal is weak
OR
If i turn ON the cell radio or WIFI after being exiting airplane mode, the phone starts connecting to the wifi or cell signal and a stutter in the app drawer occurs.
But the scrolling everywhere else is fine (ex.scrolling in homescreen pages). There are no glitches,stutters etc. anywhere except for in the app drawer.
So is it doing that since the phone is trying to connect to the wifi/cell radio and causes the stutter?
I suspect that many users will not have experienced this issue even if it exists because not everybody would be focusing so much time scrolling in the app drawer like I do for no apparent reason anyway lol :laugh: . I just wanted to know if it is normal on every htc one m8 or not.
Let me know if I am not being clear enough, thanks!

hc p304 said:
I have an htc one m8 with android 5.0.1 (lollipop). I am experiencing some stuttering issues. For example, in the app drawer when I scroll up and down for a certain period of time slowly (like for a 1 minute or so), there will be a glitch/stutter where the scroll quickly and automatically goes to next page (it is almost like the app drawer just blinked and refreshed but it shouldn't be doing that right?). After that stutter/glitch then no more glitches/stutters occur.
It usually happens when my cell signal is weak
OR
If i turn ON the cell radio or WIFI after being exiting airplane mode, the phone starts connecting to the wifi or cell signal and a stutter in the app drawer occurs.
But the scrolling everywhere else is fine (ex.scrolling in homescreen pages). There are no glitches,stutters etc. anywhere except for in the app drawer.
So is it doing that since the phone is trying to connect to the wifi/cell radio and causes the stutter?
I suspect that many users will not have experienced this issue even if it exists because not everybody would be focusing so much time scrolling in the app drawer like I do for no apparent reason anyway lol :laugh: . I just wanted to know if it is normal on every htc one m8 or not.
Let me know if I am not being clear enough, thanks!
Click to expand...
Click to collapse
I know it sounds basic and simple, but in most cases, a factory reset will fix those kind if issues.

UniversalKID said:
I know it sounds basic and simple, but in most cases, a factory reset will fix those kind if issues.
Click to expand...
Click to collapse
hey thanks for getting back to me! i appreciate it.
i already tried a factory reset as well as wipe cache too a few days ago
but it still occurs. so i am guessing this is not happening on your m8?

hc p304 said:
hey thanks for getting back to me! i appreciate it.
i tried a factory reset as well as wipe cache too
Click to expand...
Click to collapse
So still the same? Some heavy usage must be happening from an app maybe. Check under Power : Battery Usage.
Some app may be slowing down the CPU performance.
Try High Performance mode under Developer options.

UniversalKID said:
So still the same? Some heavy usage must be happening from an app maybe. Check under Power : Battery Usage.
Some app may slow down the CPU performance.
Try High Performance mode under Developer options.
Click to expand...
Click to collapse
all seems ok under the battery usage. but doesn't the high performance mode cause huge battery drain and is not recommended?
also, this isn't something that happens all the time, just when i keep scrolling a lot in the app drawer after i turn on wifi, the stutter occurs.
are you sure this isn't normal?

hc p304 said:
all seems ok under the battery usage. but doesn't the high performance mode cause huge battery drain and is not recommended?
also, this isn't something that happens all the time, just when i keep scrolling a lot in the app drawer after i turn on wifi, the stutter occurs.
are you sure this isn't normal?
Click to expand...
Click to collapse
Just try High performance mode, just to compare. See if it does the same.
Mine doesn't do that.

UniversalKID said:
Just try High performance mode, just to compare. See if it does the same.
Mine doesn't do that.
Click to expand...
Click to collapse
the stutter still happens in high performance mode after i turn off and then turn on wifi again
maybe you could try this:
first turn off wifi and data, and then turn only wifi on and then open the app drawer and scroll slowly back and forth for a few a pages about for like 30 to 60 seconds. wifi again

hc p304 said:
the stutter still happens in high performance mode after i turn off and then turn on wifi again
maybe you could try this:
first turn off wifi and data, and then turn only wifi on and then open the app drawer and scroll slowly back and forth for a few a pages about for like 30 to 60 seconds. wifi again
Click to expand...
Click to collapse
Tried it. No sttuter. But don't worry about it, maybe you have auto connect with saved WI-FI networks and stutter just when the device locks into a network.
I have auto connect and no sttuter. Just ignore it, it's a minor ''issue''

Phone freezing twice or thrice a day ! Tried all reset options !

Hi All,
Anybody here with the same issue ?
Looks like a software issue/touch unresponsive issue because usually I find it coming back to normal once I press power button and unlock it again.
Sounds like RAM allocation issue, isn't ?
Thinking to sell it. Please suggest if you guys know a better way to deal with it !
Even if I go to SC, I cannot reproduce the issue at that particular time. They will just reset it and give me back, and that where I don't want to waste my time.
Does this looks fruitful to flash stock firmware again by the unbrick way ? I feel like that will be me last try.

You seem new here, so welcome on xda
One thing you should keep in mind is to be as precise as possible when presenting an issue, your description right now is not very clear, by the title it sounded like your phone actually froze, which could have been a ram or even a power management issue, but after reading your post it seems more likely that your display was wet, or that you were charging your phone, capacitive touchscreens are sensible to that.
Usually a frozen phone does not respond to the power button like yours did, and a ram issue seems very unlikely tbh

CriGiu said:
You seem new here, so welcome on xda
One thing you should keep in mind is to be as precise as possible when presenting an issue, your description right now is not very clear, by the title it sounded like your phone actually froze, which could have been a ram or even a power management issue, but after reading your post it seems more likely that your display was wet, or that you were charging your phone, capacitive touchscreens are sensible to that.
Usually a frozen phone does not respond to the power button like yours did, and a ram issue seems very unlikely tbh
Click to expand...
Click to collapse
My style of using I believe is the same and I had no such issues in my Cool 1 ever in an year. Was a lot better in every way. Picked it up because I loved the looks, but have lost my trust on Huawei. They really need a lot of improvement.

i am having the same issues as the OP (Although i don't know what he means by "going to the SC")
the phone just goes through moments of extreme lag for about 10-30 seconds, sometimes longer, and it makes the phone COMPLETELY unusable during those times. it happens at least once every other day or so, sometimes several times a day, and sometimes it only lasts about 10 seconds, although on a few occasions, it has lasted several minutes, the phone will "attempt" to respond to inputs, but it gets nowhere quick, opening apps i did not click on, closing apps that weren't open, black-screening, half-screening (app on half the screen), etc.. sometimes i have to just power cycle..
i have the exact same feeling as the OP in that i want to sell the phone. (although i type much better, i'll assume english is a second language for him/her)
i like EMUI a lot.. although i think i want a galaxy s8/s9 now.
BND-L24 HONOR 7X B140 no root

Tirken said:
i am having the same issues as the OP (Although i don't know what he means by "going to the SC")
the phone just goes through moments of extreme lag for about 10-30 seconds, sometimes longer, and it makes the phone COMPLETELY unusable during those times. it happens at least once every other day or so, sometimes several times a day, and sometimes it only lasts about 10 seconds, although on a few occasions, it has lasted several minutes, the phone will "attempt" to respond to inputs, but it gets nowhere quick, opening apps i did not click on, closing apps that weren't open, black-screening, half-screening (app on half the screen), etc.. sometimes i have to just power cycle..
i have the exact same feeling as the OP in that i want to sell the phone. (although i type much better, i'll assume english is a second language for him/her)
i like EMUI a lot.. although i think i want a galaxy s8/s9 now.
BND-L24 HONOR 7X B140 no root
Click to expand...
Click to collapse
Since yours is the us variant, I'm assuming you've got 3 gb of ram instead of 4 gb, in which case a ram issue seems much more likely.
Not much of an issue actually, just that you probably had lots of apps open at the same time, leading to almost full ram (so the system starts closing background and even foreground apps if needed, leading to the strange behaviour you noticed).
Just remember to close apps you don't use and you'll be fine

CriGiu said:
Just remember to close apps you don't use and you'll be fine
Click to expand...
Click to collapse
It's 2018 and I think the OP and I know how smartphones work. I am coming from a phone with 2GB RAM and it has no such issues, no matter how many apps and/or games are open. Google explicitly states that closing background apps is unnecessary, and I should think EMUI offers an improvement over stock Android, not a detrimental experience. However, if you are correct and it is the RAM, it is not acceptable and needs to be fixed or I'm buying a new phone from a different company. In today's world, phones will open links to Chrome and from Chrome open reddit, xda app, pinterest, link to Facebook, share to Twitter, etc etc.. every time I click on a button I should not be having to back track to make sure I only have a certain amount of apps open. Nougat limits max open apps to 20 BTW, marshmallow it was 30.. But RAM management CPU management should be better. If it's of any interest, my reported "free" ram always stays at or above 1-1.5GB so I don't think its ram.. CPU or software problem, possibly.. But my Temps are good as well. Yes it's the 3GB version

Just a quick thought of something you could check (I also have the US 3GB version and was experiencing the same issue). Open up Settings > Battery, and other the "Other" section click "Consumption". See if there's any apps there that are keeping the phone awake and preventing it from sleeping. I would get constant lag after only a few hours of use, and it was intermittent just like you're experiencing. I was about to send the phone back, but checked this setting first. Turns out, the CNN app was running the CPU at nearly 100% for hours on end and preventing the phone from deep sleeping. Once I uninstalled that app, I haven't had issues since then. Could be something similar, just a thought. YMMV.
And by the way, it's NOT the ram. 3GB is plenty. You can see how much is being used on the app select screen, and I've never used more than 1.5 with a ton of apps in the background.

Let me help you there guys....i got the US variant too and has these freezing and lags all over the place, what i discover and did was:
1- Not all the apps works well with the phone hardware(they told me that somewhere) so try to test the apps you put on the phone.
2-Delete all the unnecessary apps from emui, that will give you less lag.
3-Check the battery consuming apps like the guy said and if you want turn on the close apps on screen lock.
Now after all of these my phone have been moving better but the problem isnt the ram, is the software so wait a little more so they can fix this cause is really a good value phone

It has to be the RAM management. Huawei must have optimized the software for 4GB, and then released a US 3GB version without changing anything, so it's screwed up even though phone is showing lots of free RAM.

Wao man thats the best explanation for this problem thanks man

It isn't and never was a RAM thing. Android's memory management essentially force closes apps (but shows them in recents) if it needs more memory. Note there is no work involved in that and you'd never know it until you switch apps and it has to reload, shows logo, etc. Amazing how non-solutions we're brought up multiple times and even thanked. Insert that's-not-how-any-of-this-works meme.

deV14nt said:
It isn't and never was a RAM thing. Android's memory management essentially force closes apps (but shows them in recents) if it needs more memory. Note there is no work involved in that and you'd never know it until you switch apps and it has to reload, shows logo, etc. Amazing how non-solutions we're brought up multiple times and even thanked. Insert that's-not-how-any-of-this-works meme.
Click to expand...
Click to collapse
Well, yeah, ram issues nowadays should not be present, but I do speak on a basis, I have experienced bad performance and foreground apps getting killed on a nexus 5, which has 2 gb of ram and stock android. I have no idea what's emui's ram management policy, but on a scale, this would be the least likely cause for sure

Pixel 3XL Ram Management problem

Okay so the phone is great let me start there and virtually no lag or studder when using most apps again all. But I did notice today while using Google Maps, Pokemon Go, and Facebook messenger that switching between the apps there was a major system hang and a slow down. Also after having a bunch of apps open it ****s Pokemon go down completely from running in the background and even though it shows it's still open in the recents, when I go back to it, it starts up again like I just opened the app and reloaded it. Has anyone else noticed this issue? And if so is this something that could be fixed with an update or is this just bad ram management for 4gb of ram on this phone?

Pokemon Go is a terribly optimized heavy resource game, it reloads after using almost anything else on my Pixel 2

One thing I've noticed for some apps, if you have it battery optimized, it will do that. YouTube Music for me would. I would be in the car, stop and go in a gas station or whatever, come back out and it would startup like it just opened for the first time. Turned off optimization and hasn't done it since. But yeah, watch out for some games. Some are resource hogs.

mdonnelly1127 said:
Okay so the phone is great let me start there and virtually no lag or studder when using most apps again all. But I did notice today while using Google Maps, Pokemon Go, and Facebook messenger that switching between the apps there was a major system hang and a slow down. Also after having a bunch of apps open it ****s Pokemon go down completely from running in the background and even though it shows it's still open in the recents, when I go back to it, it starts up again like I just opened the app and reloaded it. Has anyone else noticed this issue? And if so is this something that could be fixed with an update or is this just bad ram management for 4gb of ram on this phone?
Click to expand...
Click to collapse
This was happening to me on my Pixel 2 XL, and I thought it was a RAM management issue. Turns out it was battery optimization. I turned off battery optimization and PoGo stopped closing in the background. I did this for a couple of other programs I didn't want aggressively closed. It seems to have done the trick.

wtharp2 said:
This was happening to me on my Pixel 2 XL, and I thought it was a RAM management issue. Turns out it was battery optimization. I turned off battery optimization and PoGo stopped closing in the background. I did this for a couple of other programs I didn't want aggressively closed. It seems to have done the trick.
Click to expand...
Click to collapse
So turning off adaptive battery helps you're saying?

mdonnelly1127 said:
So turning off adaptive battery helps you're saying?
Click to expand...
Click to collapse
Not exactly. Select the apps and make sure they are not optimized. Everything else on your phone should stay optimized.

wtharp2 said:
Not exactly. Select the apps and make sure they are not optimized. Everything else on your phone should stay optimized.
Click to expand...
Click to collapse
Awesome, gonna give it a try, thank you

wtharp2 said:
Not exactly. Select the apps and make sure they are not optimized. Everything else on your phone should stay optimized.
Click to expand...
Click to collapse
Just tried it, unfortunately did not work... IDK what's up with this

wtharp2 said:
Not exactly. Select the apps and make sure they are not optimized. Everything else on your phone should stay optimized.
Click to expand...
Click to collapse
Actually I restarted my phone after I did the changes and now it seems to be working? I'll test it through out the day but if that's all it was you're a life saver my friend. Thank you

wtharp2 said:
Not exactly. Select the apps and make sure they are not optimized. Everything else on your phone should stay optimized.
Click to expand...
Click to collapse
It didn't work, see like when it gets 4 or 5 apps down the list it restarts itself when u try and reopen it .. thank you though

I think there's a RAM leak. I think there was one on the 2 XL too.

I saw someone in the comments of an article say there is way to fix this with root. Is there a magisk mod that helps with this?

probably the SWAP being used

You MOMOS. IT SAVES BATTERY. DO YOU GET IT?

More and more reports are coming up regarding this issue - playing music in the background and then using the camera, etc.
I have experienced it when using Smart AudioBook Player playing in the background and have google maps navigation running. All of a sudden, the audio bookstops playing. I have to switch to the audiobook and restart playback. It then happens again and when I restart the audiobook a second time, google maps' navigation gets closed out. I think google needs to issue a software update for their RAM management.

jrac86 said:
More and more reports are coming up regarding this issue - playing music in the background and then using the camera, etc.
I have experienced it when using Smart AudioBook Player playing in the background and have google maps navigation running. All of a sudden, the audio bookstops playing. I have to switch to the audiobook and restart playback. It then happens again and when I restart the audiobook a second time, google maps' navigation gets closed out. I think google needs to issue a software update for their RAM management.
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-3-xl/how-to/apps-closing-t3857299/post77946888
In addition to that @topjohnwu has stated:
Just checked the code, it seems that the configurations are read only once when it started. If kernel devs wants to tune LMK, they would either have to: a. Modify /system/bin/lmkd to allow runtime changes b. Use resetprop to modify those read-only props, and restart lmkd https://twitter.com/MishaalRahman/status/1054409086626861056
Sent from my crosshatch using XDA Labs

Ram isn't a problem for me but I will be implementing simple lmk in FrankenKernel ,for those with issues it's probably just aggressive .. Should not be a huge deal going forward..
Sultan- https://github.com/sultanxda/androi...mmit/cd8c0ff4eba3310ffa016e1bd29b4b0bcd7baff5

Furthermore I think people are taking this a tad too far I have had the device since Friday and can't speak anything but great things and look forward to developing on it in the coming days

There is defiantly some ram issues, i have been using a few music apps that keep getting killed when im doing other things. im sitting at over 3gb of usage almost 700mb more usage then my pixel 2 xl with the same apps i use. Im sure it will be fixed just not sure it will be done with in my return window and since i got it from vzw i wont have the luxury of flashing better optimized kernels . sucks having issues like this but i think all my pixel nexus phones had some odd issues for the first few weeks/months

I noticed the RAM problem while using Amazon Music and Zombie's Run! The music would stop during the first song while the Run app still runs. It really sucks to have to stop my workout to make the music start. My 2XL never had this issue.
I'm on the fence. For this amount of money, I should be happy with it, not annoyed.