View Single Post
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#4
Originally Posted by paulkoan View Post
What would this mean in terms of a voice call? I am assuming that freemantle doesn't have quite the same gung-ho approach with rti, and will leave a few cycles ready so I can hit "answer" on the incoming call.
I suspect pm_qos is part of the answer. On the scheduler front, the SDK kernel is configured like this:

CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_RT_GROUP_SCHED is not set
CONFIG_USER_SCHED=y
# CONFIG_CGROUP_SCHED is not set
so maybe (just guessing) telephony will run as a different uid to get its fair share of CPU cycles?

The other side of this is memory management. If the telephony app isn't already in RAM (eg it hasn't been started or it gets swapped out by another memory-hungry process) when a call comes in it could take a while before it can start playing the ringtone and display an answer button, and you might even miss the call. This is what happens currently with SIP or Jingle calls on the N8?0s.

Conversely, if you don't want to use the device as a phone that's a waste of perfectly good RAM. This could be a significant factor in choosing a "phone" vs "tablet" Fremantle device for some people.
 

The Following 2 Users Say Thank You to lma For This Useful Post: