Difference between revisions of "Backboardd"

From The iPhone Wiki
Jump to: navigation, search
m
(Explained what backboardd actually does, removed stub.)
Line 1: Line 1:
 
{{lowercase}}
 
{{lowercase}}
'''backboardd''' is a [[wikipedia:Daemon (computing)|daemon]] that appears to run alongside the [[SpringBoard]] daemon. It was discovered in an [[iOS]] 6 log file on an unmodified [[n94ap|iPhone 4S]]. Also [[Cydia.app|Cydia]] v1.1.8 now not only restarts [[/System/Library/CoreServices/SpringBoard.app|SpringBoard]], but also '''backboardd''' and [[sbreload]] after some installations.
+
'''backboardd''' is a [[wikipedia:Daemon (computing)|daemon]] that runs alongside the [[SpringBoard]] daemon. It has been introduced in iOS 6, aiming to offload some of Springboard's responsibilities, chiefly that of event handling. Prior to its introduction, SpringBoard was effectively the UI event sink for iOS, as is WindowServer in OS X. With backboardd, all touch events are first processed by this daemon, then translated and relayed to the iOS application in the foreground (i.e. to its UIApplication event loop).
   
[[Category:Daemons]]
 
   
  +
As a simple experiment, login over SSH to send a kill -STOP signal to the daemon, then touch your device. If you kill -CONT the daemon, you will see your touch events played out, as the events are consumed from I/O Kit by backboardd, and relayed to the foreground app.
{{stub|software}}
 
  +
  +
  +
[[Category:Daemons]]

Revision as of 03:48, 5 March 2013

backboardd is a daemon that runs alongside the SpringBoard daemon. It has been introduced in iOS 6, aiming to offload some of Springboard's responsibilities, chiefly that of event handling. Prior to its introduction, SpringBoard was effectively the UI event sink for iOS, as is WindowServer in OS X. With backboardd, all touch events are first processed by this daemon, then translated and relayed to the iOS application in the foreground (i.e. to its UIApplication event loop).


As a simple experiment, login over SSH to send a kill -STOP signal to the daemon, then touch your device. If you kill -CONT the daemon, you will see your touch events played out, as the events are consumed from I/O Kit by backboardd, and relayed to the foreground app.