The Following 5 Users Say Thank You to imaginaryenemy For This Useful Post: | ||
![]() |
2016-06-28
, 00:53
|
|
Posts: 634 |
Thanked: 3,266 times |
Joined on May 2010
@ Colombia
|
#33
|
If the app isn't doing anything then it saves state and releases resources saving your battery. It restores state back to where you left it when you resume it.
Finally, it's quite apparent that some of us, myself included, want the same type of multitasking as on a desktop, even though there might be a battery/power penalty to pay.
The Following 9 Users Say Thank You to wicket For This Useful Post: | ||
![]() |
2016-06-28
, 06:26
|
Community Council |
Posts: 691 |
Thanked: 1,240 times |
Joined on Sep 2010
@ Mbabane
|
#34
|
This is not true. If a process is idling in memory, it will not consume any additional power unless it is swapped out. Saving and restoring state requires copying data from RAM to non-volatile storage and back again. This action is similar to swapping and does consume extra power. When Android restarts an app from scratch and restores its state, it's quite likely that it uses more power due to extra instruction cycles and copy operations than swapping normally would.
This is not entirely true either:
https://felipec.wordpress.com/2012/0...ic-vs-dynamic/
The Following User Says Thank You to sicelo For This Useful Post: | ||
![]() |
2016-06-28
, 06:49
|
Posts: 1,808 |
Thanked: 4,272 times |
Joined on Feb 2011
@ Germany
|
#35
|
but then ... it could be that more recent android builds have overcome some of the issues raised on that post? I notice that was 2012.
The Following 9 Users Say Thank You to reinob For This Useful Post: | ||
![]() |
2016-06-28
, 06:55
|
|
Posts: 6,453 |
Thanked: 20,983 times |
Joined on Sep 2012
@ UK
|
#36
|
The Following 8 Users Say Thank You to pichlo For This Useful Post: | ||
![]() |
2016-06-28
, 08:04
|
Posts: 702 |
Thanked: 2,059 times |
Joined on Feb 2011
@ UK
|
#37
|
This is not true. If a process is idling in memory, it will not consume any additional power unless it is swapped out. Saving and restoring state requires copying data from RAM to non-volatile storage and back again. This action is similar to swapping and does consume extra power. When Android restarts an app from scratch and restores its state, it's quite likely that it uses more power due to extra instruction cycles and copy operations than swapping normally would.
The Following 2 Users Say Thank You to aegis For This Useful Post: | ||
![]() |
2016-06-28
, 08:09
|
Posts: 702 |
Thanked: 2,059 times |
Joined on Feb 2011
@ UK
|
#38
|
The Following User Says Thank You to aegis For This Useful Post: | ||
![]() |
2016-06-28
, 09:54
|
|
Posts: 400 |
Thanked: 708 times |
Joined on Jun 2011
@ Geneva - CH
|
#39
|
The Following 5 Users Say Thank You to Jordi For This Useful Post: | ||
![]() |
2016-06-28
, 11:51
|
Posts: 1,873 |
Thanked: 4,529 times |
Joined on Mar 2010
@ North Potomac MD
|
#40
|
The Following 6 Users Say Thank You to mscion For This Useful Post: | ||
Playing VIDEOS in the background was only mentioned to demonstrate common misconceptions on multitasking on Android.
I agree, multitasking on mobile does not compare to multitasking on desktop. I just think the multitasking divide between Android and other more loved OSs is much smaller than many would like to think.
Sent from my XT1095 using Tapatalk
Last edited by imaginaryenemy; 2016-06-27 at 05:24.