Not happy with the touch screen responsiveness of the moto g

[soccerballtux]

They do but this is a developer's hacky method. I wrote about this before in that you still observe redraws. I'm not talking about launching intensive 3D games. Just exiting out of Chrome sometimes can you get you redraws. I believe Android 4.3 seemed to clean up some memory management where the issue was less prevalent (at least for me). I agree that there should be a class exception for launchers, and perhaps Android 4.3 was the magic pill.

Yeah, but 10% consumption by a game shouldn't result in a redraw. Freaking Mozilla Firefox is taking 25% of my RAM right now on my desktop.

Getting back to the topic though, input lag definitely could also be an issue and the results depend app to app. I was just playing with Google Maps side by side on my Nexus 5 and iPhone 5. Both are not 60 fps for sure. Its hard without an fps meter, but I *think* the Nexus 5 was a tad slower. But what was definitely noticeable was input lag. I think part of it is the inherent input lag for the device itself, but there might be something with Google Maps too in that its just a slow app in general.

maps since v7 has been uber laggy esp on input. 6 was much faster.

I worded that second point you bolded weird.

I was meaning to say that the bigger games need all the RAM they can get, and even 10% held for the launcher could cause issues.

I don't care to draw the side discussion out any further, so we'll just respectfully disagree on the severity of this problem. I do acknowledge that it exists; just don't want to be misunderstood there.

use OS monitor or another mem monitor. The game is not using all the RAM. When you get the redraw it's because it pushed the launcher out but a bunch of other apps are still there. It's poorly tweaked android, plain and simple pretty standard for google, get it 90% done (like maps 7 and 8) and ship it.

 

[sweenish]

I've already said I'll just disrespectfully disagree on the severity of the problem.

I'm not denying it's a problem. You're welcome to agree with DLeRium, just stop trying to debate the point with me.

 

[Suspicious-Teach8788]

Regarding the launcher: I think that's why the V6 supercharger attempts to lock the launcher in a different memory priority slot. Its also why apps like LightFlow have an option to run in foreground. Lux does this too. It ensures the app doesn't get killed off. If a background app gets killed off, I think often times the service won't automatically restart? Or if it does, its very unreliable. What I've noticed about LightFlow is that you have to relaunch the app itself and only from then on will notifications come in properly and blink properly. Every few days I'll see my phone blinking with a white light, meaning that LightFlow has stopped working. Its definitely a bit annoying. The problem isn't limited to launchers and I hope Google addresses this. AT the same time its a bit of a Catch 22. If you make it easy for apps to lock into RAM, can you see how apps could get abused? Junk apps could try to stay open for the sake of staying open. Like Facebook. Right now you can Greenify that stuff because it doesn't need to be open for you to receive push notifications.

Now regarding the Maps 6 vs 7 issue, yeah. 6 is definitely faster. Hope they clean up the Maps 7 performance a bit. The slideshow on my Nexus 10 is definitely not cool.

 

[CptObvious]

My Moto G's touchscreen screws up when it's charging (registers swipes as taps) but is fine when discharging.