Appletell has closely followed the development of the jailbreak to bring Siri to older iOS devices. Many hackers were able to port Siri to the iPhone 4 and the iPod Touch 4th generation, but they failed to make Siri speak fluently like it's capable in the iPhone 4S. The main problem was getting the hacked Siri to talk to Apple's servers, as Siri works by sending your requests to Apple's servers (the servers act as the brain-power for Siri). Now, thanks to hackers such as Steven Troughton-Smith and chpwn, those problems have been overcome.
These developers have managed to get the hacked version of Siri communicating successfully with Apple's servers. But don't expect to see this Siri hack anytime soon for a public release, as this is a proof-of-concept only.
The two hackers provided a video (below) of their successful port of Siri to these older iOS devices.
In an interview with 9to5Mac, the developers revealed that in order to get Siri to work, users first have jailbreak their Apple devices, and it requires extracting code components from Siri files of a jail-broken iPhone 4S. The Siri transplant to these older Apple devices was about a 20-step process of renaming and recoding files to complete. Steve Troughton-Smith told 9to5Mac he doesn't want to be involved in distributing the Siri port at the moment, but he promised that more details of the hack will be revealed soon.
Siri port to the iPhone 4 video:
Siri working on an iPod Touch 4th Generation:
Meanwhile, a second video demonstrates Siri running on the iPod touch, though in this case there are some hardware limitations. According to them, UI on the iPod touch felt "slightly slower," though the actual Siri usage was "pretty much identical to the iPhone 4S." Now, that is typical because the iPod touch carries less RAM and has a slower single-core processor A4 chip. Also, there has been some difficulty with the iPod's microphone, which in terms is less sensitive than that of the iPhone 4/4S: Siri demands a clear voice to be able to pick up your voice commands.
Via [9to5Mac]
No comments:
Post a Comment