Using Lollipop on my device with 1 GB of RAM, I've found that I have trouble using Maps Navigation and Play Music together. Frequently, if I start Nav and then Music, Nav will be closed. Conversely, if I start Music and then Nav, Music will be closed.
Further, I've discovered that if I open the app switcher and clear all old applications, that Nav and Music will work together without problem.
It appears that Android is trying to reclaim memory while under pressure from Nav & Music, but it's starting with other fresh, currently-running applications instead of clearing out old apps from memory first. I would expect stale applications, like Chrome, Mint, or whatever that hasn't been touched in hours to be killed first over a new app--especially ones that are running in the background actively (Music, Nav).
Why is Android killing processes like that? Shouldn't it kill old apps first over newer, active ones?
Further, I've discovered that if I open the app switcher and clear all old applications, that Nav and Music will work together without problem.
It appears that Android is trying to reclaim memory while under pressure from Nav & Music, but it's starting with other fresh, currently-running applications instead of clearing out old apps from memory first. I would expect stale applications, like Chrome, Mint, or whatever that hasn't been touched in hours to be killed first over a new app--especially ones that are running in the background actively (Music, Nav).
Why is Android killing processes like that? Shouldn't it kill old apps first over newer, active ones?
Aucun commentaire:
Enregistrer un commentaire