|
2014-11-20
, 16:28
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#12
|
Cant we have some hack that when we minimize the app, that we do not let the app know it has been minimized.
Example use case:
How it looks like at the moment:
Official Android YouTube app > open a video/music > minimize > Video/Music stops
With some hack (to not let the app know you have minimized):
Official Android YouTube app > open a video/music > minimize > Video/Music does NOT stop
anyone?
The Following User Says Thank You to juiceme For This Useful Post: | ||
|
2014-11-20
, 16:35
|
|
Posts: 6,445 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#13
|
The Following 4 Users Say Thank You to pichlo For This Useful Post: | ||
|
2014-11-20
, 16:51
|
|
Moderator |
Posts: 3,715 |
Thanked: 7,419 times |
Joined on Dec 2009
@ Bize Her Yer Trabzon
|
#14
|
Very easy to do.
There are operating system hooks that tell the application what is the current focus. You are free to implement functionality to continue playing when you receive an out-of-focus message.
Many application developers just implement the functionality strictly as Android development guide tells you to do.
|
2014-11-20
, 16:56
|
Posts: 1,873 |
Thanked: 4,529 times |
Joined on Mar 2010
@ North Potomac MD
|
#15
|
Cant we have some hack that when we minimize the app, that we do not let the app know it has been minimized.
Example use case:
How it looks like at the moment:
Official Android YouTube app > open a video/music > minimize > Video/Music stops
With some hack (to not let the app know you have minimized):
Official Android YouTube app > open a video/music > minimize > Video/Music does NOT stop
anyone?
|
2014-11-20
, 17:32
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#16
|
If you are the developer, yes...
But what I mean is can we apply this to apps that already has such stupid 'stop when minimized' thing? (Maybe by editing some files from the dalvik?)
|
2014-11-20
, 18:55
|
Posts: 1,873 |
Thanked: 4,529 times |
Joined on Mar 2010
@ North Potomac MD
|
#17
|
|
2014-11-20
, 19:28
|
|
Posts: 423 |
Thanked: 478 times |
Joined on Sep 2014
@ Netherlands
|
#18
|
|
2014-11-20
, 19:47
|
|
Posts: 3,404 |
Thanked: 4,474 times |
Joined on Oct 2005
@ Germany
|
#19
|
The Following User Says Thank You to pycage For This Useful Post: | ||
Multitasking has just one single well-defined meaning in the context of computers, and all digital telephone devices, whether dubbed smartphones or dumbphones are computers.
Multitasking means that the device has the capability of holding more than one execution context in memory, and has a task switching mechanism that can allocate processor cycles to execution contexts.
It is up to the operating system and the application development libraries how they implement this in a useful context to the user.
Some systems are built so that they enforce developer to use a design pattern where only one foreground application is allowed to interact with its environment. This might annoy some people as it is possible for example that a poorly designed music player stops when pushed to background.
Other systems allow all interactive applications to continue when not in the foreground focus, which then again might annoy some people as it is possible to have two different sound sources play at the same time.
You are free to choose which method annoys you less
However, both kind of systems and all the range between can be built on top of the same core OS.
Hence, it is meaningless to talk about multitasking in this context.
Note: Some people seem to think that having background processes frozen leads to less power consumption but this is not actually true as given. The isolation from environment is done on level up from the core OS, and it makes really small difference powerwise whether most cycles are given to one application or to several applications...