View Single Post
Old 03-07-2014, 10:48 AM   #10
Sharkus
Evangelist
Sharkus ought to be getting tired of karma fortunes by now.Sharkus ought to be getting tired of karma fortunes by now.Sharkus ought to be getting tired of karma fortunes by now.Sharkus ought to be getting tired of karma fortunes by now.Sharkus ought to be getting tired of karma fortunes by now.Sharkus ought to be getting tired of karma fortunes by now.Sharkus ought to be getting tired of karma fortunes by now.Sharkus ought to be getting tired of karma fortunes by now.Sharkus ought to be getting tired of karma fortunes by now.Sharkus ought to be getting tired of karma fortunes by now.Sharkus ought to be getting tired of karma fortunes by now.
 
Sharkus's Avatar
 
Posts: 444
Karma: 2269648
Join Date: Jun 2010
Location: Toronto
Device: Kobo: Original, WiFi, Touch, Aura, Aura H20, MiniGloHD ;) iOS app
Quote:
Originally Posted by davidfor View Post
I think it was there for the Aura testing. The Aura has the codename "Phoenix" and the Glo is "Kraken". When I first saw that option, it was a a couple of months before the Aura was announced. I assumed that having "KrakenIsPhoenix=true" allowed Kobo to test changes for the Aura on the Glo but I don't remember seeing any differences.
There is some sense to that, and though there might not be an interface difference, there could be a behind the scenes difference, for example, a unique model identifier sent up to the server when you sync.
This option would therefore allow a Glo to masquerade as an Aura, and send up the Aura's unique model identifier, and thus it an be checked that the system is picking up the Aura correctly.
Sharkus is offline   Reply With Quote