Quote:
Originally Posted by davidfor
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.