Nokia's “Normandy” phone uses a forked variant of Android, a la Kindle Fire
This is Nokia's Android phone — Codename Normandy is ‘full steam ahead’ — Nokia has been building its own Android phone according to multiple sources familiar with the company's plans.
Context & Ripple Effects
Nokia enters this story from a position of near-total control of one platform and an exit from hardware: AdDuplex put the company above 90% of Windows Phone market share in November 2013, with the budget Lumia 520 as its top-selling device worldwide, and the bulk of its handset business is already sold to Microsoft. A forked-Android device sits awkwardly across both facts.
The reported model is Amazon's Kindle Fire — Android's open-source core without Google's services layer — which would let Nokia ship app compatibility without joining Google's ecosystem. The breadth of pickup matters too: Ars Technica, Engadget, Gizmodo and five other outlets ran the same sourcing within a day, and the claim remains unconfirmed rumor rather than an announced product.
First-order effects
- A shipping Normandy would put Nokia in direct competition with the low-end Android handset market its own Lumia 520 currently wins on price — using Google-compatible apps without Google's blessing.
- Microsoft, mid-acquisition of Nokia's phone business, gains a partner whose flagship volume brand is hedging into the rival platform.
Second-order effects
- If the fork carries Nokia services instead of Google's, it pressures Google to make full GMS Android more attractive to second-tier OEMs, just as comScore data shows Android's US share has stopped eroding.
- Windows Phone's developer case rests on Nokia's volume; any Nokia-branded Android device siphons exactly the entry-level buyers the Lumia line was converting.
Third-order effects
- Kindle Fire plus a rumored Normandy points toward a two-tier Android: Google-certified devices versus open-source forks that swap Google services for the vendor's own — a structural split over who monetizes the platform.
- For Microsoft the pattern is uncomfortable: acquiring the dominant Windows Phone maker while that maker builds an escape hatch suggests hardware brands treat operating systems as replaceable layers, not commitments.
The trend: Major hardware makers are increasingly treating Android's open-source core as a neutral base they can fork and re-service on their own terms, following the Kindle Fire template.