Did anyone notice frequent launcher redraw?
I see launcher redraw almost everytime when I exit playing games. It's just that now it redraws faster so you don't feel as bad as before.
However, I don't recall I have launcher redraw issue at all since L... until now.
Is there anyway to stop this?
Unfortunately no. Crappy memory management and 2GB of ram are the culprit. Marshmallow is not very lean
Haven't seen any launcher redrawing myself, but I don't play games and tend to restart my phone every few days to keep things fresh.
Related
My phone is actually quite laggy now. Sometimes flicking between the menus lags so I have to restart my phone.
Also, high end processes such as the game asphalt lag A LOT.
Whats up? I thought this was "the most powerful phone in the world"?
+1 finding mine to lag a lot as well........
Mine also becomes increasingly laggy, the only thing that sort of works is using advanced task killer to stop the all the background running programs, some were running on mine i dont even remember opening!
Not finding this at all. I think it's certain apps that cause it as my phone is practically full of apps barely any space left but still not laggy.
EDIT: No task manager on mine either.
i have around 40 apps including asphault and sygic navigation and i nevered faced lag in my desire....!!!! the only time i restart the phone is when i have all of them running and cause i don't want to kill them with task managers i restart in order for it to close them itself.
Sorry but I must say, I'm a bit disappointed. The Phone is Luggy.
And I don't even dare to compare it to Iphone (And Yes I know it boosts more then twice the resolution of the Iphone), but still When I play Asphalt It looks like a Pentium 3 running - Crysis.
So... "Fastest Phone ever made"??? Maybe only on paper...
Asphalt for some reason does not run well on the Desire, the game is butter smooth on my Milestone. Let's hope they optimize it for the Desire as well, the game is quite good.
The phone does get very laggy unless you use a task manager. For a snapdragon powered phone it doesn't seem to be very "Snappy". It's seriously bad in the "All Programs" menu especially.
As for gaming, the milestone will unfortunately always be better than the Desire. It has an OMAP/PowerVR CPU/GPU combo (The same as the Nokia N900) which outclasses the Snapdragon in 3D gaming but is slightly slower in CPU intensive apps.
I've been attacked with huge consistent lag since 2 days now (unknown before) but it was the miscall app and app organizer running in the background causing it (as well as voraciously depleting the battery life) so not a problem here.
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Hi All,
I like(d) my ARC, especially for gaming. The problem is, however, that many games (amazing spiderman, the dark knight rises, death trigger..) randomly crash during gameplay. Firstly I thought it is a RAM problem, but now I think it is something else because when the game crashes, often the launcher is still in memory and services like Facebook or Maps or Dropbox have been running for very long time. In other words, if it is a RAM problem, shouldn't these services and processes be killed before the memory reaches critical state and the app crashes? I have about 150MB free ram when starting the game, I doubt the whole game is going to eat it all up (unless android is for some stupid reason trying to keep 100 MB or so constantly free..)
So if it is not a RAM problem, what else might be causing these issues? Lack of VRAM? Are you guys facing the same crashes? If not, what ROM are you using? (I wanna keep ICS, so pls. don't tell me "go back to GB" )
Thanks for your opinions!
V6 Supercharger.
The only problem - supercharging makes the phone slower and everything lags more. Heavier applications (like Chrome or maps) cause the whole phone to freeze even for 5 seconds.
Use CM10 or MooDeD 90.7
GNex on 4.2.2 slow and memory-starved...is a "keep in memory" tool the answer?
Lately on 4.2.2 completely stock I've been very disappointed with the performance of my phone. The launcher always redraws after using Chrome and Chrome and the new Hangouts app pretty much never stay in memory and can take up to 5 seconds to relaunch when I come back to them. It's ridiculous for a late 2011 phone.
I've always been anti-task killer tools, but I don't have these sorts of problems on my Nexus 10 and the reason why is obviously that it has more RAM. The Nexus 10 reports 700+ MB free RAM, the GNex often reports <50 MB. So it is clear that after using a couple apps, apps like Hangouts, Chrome, and the launcher just can't stay in memory and take forever to reload.
So I wonder, is a "keep in memory" app the right solution? Can I use a tool to tell Hangouts, Chrome, and the launcher to stay in memory to improve my basic usage of the phone? What would be the best tool? I don't want an auto-kill app, I just want an app that says "if you're going to kill things, don't kill these." Is this the best option, or are there other things I can use that don't require root?
Thanks.
Does anyone that has they're Note 4 experiencing any home screen or app switching lag of any kind? I heard that is the only problem so far, the whole TW user interface is hogging just about 2GB of ram.
Chuckleb0ne said:
Does anyone that has they're Note 4 experiencing any home screen or app switching lag of any kind? I heard that is the only problem so far, the whole TW user interface is hogging just about 2GB of ram.
Click to expand...
Click to collapse
I heard the opposite...NO LAGS!! I also played with it in Bestbuy store for about 1 hrs 1/2 and found no lags
Everything is smooth as silk, unless you leave 20 bazillion apps running in the background. I also opened the developer options and reduced the animation time delay for faster response as well.
only has like 300MB of free ram when idling.
If freeing up ram is something that you want, then purchase Greenify from the Playstore. This app is also effective when the phone us not rooted.
Has anyone else noticed some slowdowns on their pixel 2 XL? I had noticed slow animations on Android Oreo, I thought that maybe they would be fixed in the Pie update, but i am still noticing slow downs every so often.
For me, Pie has actually been the smoothest compared to DP2 though DP5. There's a similar thread already here:
https://forum.xda-developers.com/pixel-2-xl/how-to/phone-sluggish-time-t3826729
harryfornasier said:
Has anyone else noticed some slowdowns on their pixel 2 XL? I had noticed slow animations on Android Oreo, I thought that maybe they would be fixed in the Pie update, but i am still noticing slow downs every so often.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
I've been getting stutters too. Occasionally it will just catch up and lag.
Haven't noticed any stuttering, just seems smooth for my usage...
harryfornasier said:
Has anyone else noticed some slowdowns on their pixel 2 XL? I had noticed slow animations on Android Oreo, I thought that maybe they would be fixed in the Pie update, but i am still noticing slow downs every so often.
Click to expand...
Click to collapse
There's micro stutters here and there but they're insignificant, I wouldn't call them slowdowns. Google really needs to up their ram for the next phone, the 4gb is starting to show it's limitations. Compared to the iPhone , the pixel doesn't seem very smooth with it's animations.
Actually my test shows after couple hours usage, the free RAM of Android P will drop around 600MB.
At this stage, you will start getting stutter or even no response from apps due to system try to release free RAM.
Right after boot up, Andrpod P will have around 1300MB free RAM, however after couple hours use (depends on how heavy you use your phone), the free RAM will go down to around 500MB and you will notice stutter if you launch some App which requires RAM.
You can verify this by launch Google Map, Google Photo and Street View together... or you could launch Camera App then take some panorama after a day's use. When fresh out of reboot, Pixel 2 XL has no trouble running those App together or handling multiple Panoramas but will run into stutter or even kill your Launcher for free RAM after couple hours useage...
I checked the OOM setting on "empty app" and it's defaulted at 318MB. I suggest raise it to 512MB to get better, longer stutter free operation (YMMV). With default OOM setting when I launch camera app, sometimes Nova Launcher will be killed for free RAM. However after modifing the empty app OOM limit to 512MB I seldom got any kill rampage when launching camera app.
For me, Android P is smooth when free RAM is over 900MB and you will definitely get into stutter when free RAM under 600MB. And it's unavoidable to went to this low ram stage after some use...
If you don't have above issue then lucky you, or you just didn't use your phone heavy enough as Google think you should... I don't want to argue how good Android can manage RAM since for me, kill my Launcher to make RAM for Camera is not a solution... Which happened to me quite often. I use Greenify to block most background app and do check what runs behind the scene quite regularly and kill those unwanted... Still, Android P will go to 600MB free RAM unless I modify OOM... (It's now aound 800MB when Nova Launcher is foreground App)
You can use this app for monitoring your free RAM.
https://play.google.com/store/apps/details?id=info.kfsoft.android.MemoryIndicatorPro
lssong99 said:
Actually my test shows after couple hours usage, the free RAM of Android P will drop around 600MB.
At this stage, you will start getting stutter or even no response from apps due to system try to release free RAM.
Right after boot up, Andrpod P will have around 1300MB free RAM, however after couple hours use (depends on how heavy you use your phone), the free RAM will go down to around 500MB and you will notice stutter if you launch some App which requires RAM.
You can verify this by launch Google Map, Google Photo and Street View together... or you could launch Camera App then take some panorama after a day's use. When fresh out of reboot, Pixel 2 XL has no trouble running those App together or handling multiple Panoramas but will run into stutter or even kill your Launcher for free RAM after couple hours useage...
I checked the OOM setting on "empty app" and it's defaulted at 318MB. I suggest raise it to 512MB to get better, longer stutter free operation (YMMV). With default OOM setting when I launch camera app, sometimes Nova Launcher will be killed for free RAM. However after modifing the empty app OOM limit to 512MB I seldom got any kill rampage when launching camera app.
For me, Android P is smooth when free RAM is over 900MB and you will definitely get into stutter when free RAM under 600MB. And it's unavoidable to went to this low ram stage after some use...
If you don't have above issue then lucky you, or you just didn't use your phone heavy enough as Google think you should... I don't want to argue how good Android can manage RAM since for me, kill my Launcher to make RAM for Camera is not a solution... Which happened to me quite often. I use Greenify to block most background app and do check what runs behind the scene quite regularly and kill those unwanted... Still, Android P will go to 600MB free RAM unless I modify OOM... (It's now aound 800MB when Nova Launcher is foreground App)
You can use this app for monitoring your free RAM.
https://play.google.com/store/apps/details?id=info.kfsoft.android.MemoryIndicatorPro
Click to expand...
Click to collapse
This is only valid for people who buy the phones direct from Google and are able to root. For those from Verizon, you are out of luck, as there's no way to mess with memory settings.
This post is one reason in won't buy from Verizon.
Sent from my [device_name] using XDA-Developers Legacy app