Well, the moon doesn't keep my phone's $ per minute network
connections alive when I'm not looking at it, nor does it burn extra
CPU cycles. I think the real issue is that users want control over
possible network charges and battery life. It's great that Android is
managing memory for us (but most OSes do that already via page and
disk caches) but I need to know that when I'm done with an app *all*
its resources are released.
Or, conversely... The Maps app is currently doing a great job of
enabling the GPS receiver only when a map is displayed - I can see the
satellite icon appear and disappear. But then it takes a while to
update my location when I switch to a browser and back... so maybe
Maps should just keep the GPS alive until I kill it? Then *I* get to
decide how much battery life to use while traveling.
On Sep 25, 3:33 am, Peli <[EMAIL PROTECTED]> wrote:
> It is similar to the question: Is the moon there when you don't look
> at it? [1] From the user perspective, the moon should always be there.
> You know where the moon is, you know where to look ("sky") to find it.
> From the Android perspective, the moon does not have to be there if
> the user does not look there, so Android may kill it and compress it
> to a few bytes (moon position, moon phase). When the user looks at the
> sky again, Android pops up the moon at the correct position with the
> correct moon phase, and as a user you never know if the moon existed
> while you were not looking at it.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Android Discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
