Amazon Kindle Fire cheat sheet for Android developers

My company recently published our Android app on the Amazon app store for Kindle Fire tablets. While getting ready to publish the app on the store, I realized that the list of Kindle Fire specifications that Amazon has here is neither developer nor customer support friendly.

Kindle Fire devices show system version in this format: 7.5.1_user_5170020. 


This does not convey the Android OS version at first glance. So, if a user or a customer support representative says that your app is not working on a Kindle and they only give you the system version, you as a developer are not sure which version of Kindle it's failing on.

If you are also debugging via USB on a Kindle device, Android Studio only shows you the Build Model and not the OS version.

To solve these issues, I made the cheat sheet below to help Android developers quickly determine which Android OS version a Kindle is on. Hope this helps!

Note: This table is as of March 28 2015.


Build Model Name Screen Size Status Android OS Fire OS Device -> Latest System Version Screen density
KFSAWA or KFSAWI HDX 8.9" 4th gen 8.9 New 4.4.2 4 22.4.5.3_user_453011120 xhdpi
KFASWI HD 7" 4th gen 7 New 4.4.2 4 20.4.5.3_user_453011120 hdpi
KFARWI HD 6" 4th gen 6 New 4.4.2 4 20.4.5.3_user_453011120 hdpi
KFTHWI or KFTHWA HDX 7" 3rd gen 7 New 4.4.2 4 updated from 3 13.4.5.3_user_453011120 updated from
13.3.2.5_user_325001120		 xhdpi
KFAPWA or KFAPWI HDX 8.9" 3rd gen 8.9 Legacy 4.2.2 4 updated from 3 14.4.5.3_user_453011120 updated from
14.3.2.5_user_325001120		 xhdpi
KFSOWI HD 7" 3rd gen 7 Legacy 4.2.2 4 updated from 3 11.4.5.3_user_453011120 updated from
11.3.2.5_user_325001620		 hdpi
KFJWA or KFJWI HD 8.9" 2nd gen 8.9 Legacy 4.0.3 N/A 8.5.1_user_5156520 hdpi
KFTT HD 7" 2 gen 7 Legacy 4.0.3 N/A 7.5.1_user_5170020 hdpi
KFOT 7" 2nd gen 7 Legacy 4.0.3 N/A 10.5.1_user_5170120 mdpi
Kindle Fire 1st gen 7 Legacy 2.3.3 N/A 6.3.3_user_4112920 mdpi

References:
Downloadable Kindle Fire System Updates
Kindle Fire Specifications

Popular posts from this blog

Recap of Android Summit 2017

I recently attended and spoke at Android Summit , an Android conference organized by the folks at Capital One. Special shoutout to Jared A Sheehan, Michael Jones and the entire organizing committee for running a fabulous event which raised $6000 for Women who Code. All speakers received a Phillips Hue Starter Kit as a speaker gift which I've used to toggle and dim my living room lights via Amazon Echo. So much fun! I had a prior commitment and could only attend Day 1 but here are my highlights. Process & Workflow A common theme on Day 1 was process and workflow talks which tied in beautifully with Kelly Shuster 's keynote. Kelly is an excellent story teller. In her keynote, she connected a story of communication from her theatre background to how developers, designers and testers need to work together to reduce boiler plate conversations when designing and developing apps. I gave a similar talk earlier this year at  Chicago Roboto  with my co-worker and designer  J
Read more

Team Charter and Norms: Working together

Image
In my previous blog post , I wrote about setting up a Team Charter and Team Norms on a team. In this post, I elaborate on some of the rules of engagement that teams I have worked on have generally used. Most software development teams that I have worked on have used some sort of Agile practices like the Scrum framework where cross-functional teams use iterative and incremental processes to improve their software delivery process. I have always used Agile in a way that works best for my team and the company’s culture at that time.  🧱 Team Structure I have had to occasionally run Scrum meetings as an Engineering leader since I have been on teams without dedicated Scrum Facilitators or Product Owners. Each Scrum team usually includes an Engineering Manager, Scrum Facilitator or Project Manager, Product Manager and Developers. In the absence of dedicated Project Managers or if there is leadership interest on the team, I make the Scrum lead role rotational so that every person on the team
Read more

Chicago Roboto 2018 Recap + First Keynote!

Chicago Roboto was back again this year as a single track conference and there were a lot of excellent talks.  Last year I gave a talk with my co-worker and product designer extraordinaire Jess Moon about design and development workflows and this year I was back again but as a Keynote speaker. Keynote Giving a keynote was a stretch goal I set for myself in 2018 and I managed to achieve it early thanks to the Chicago Roboto review committee. The topic I chose was being an Android Advocate who brings teams and communities together. I will be writing a follow up blog post about my keynote process soon but before that, a quick shout out to Corey Latislaw and my coworkers at Warner Bros. Digital Labs who took a look at my first and second drafts and listened to all my half-baked thoughts and ideas. Achievement unlocked 🎉🎉🎉 - Gave my first keynote @chicagoroboto #chicagoroboto Slides with resources available at https://t.co/OJVbZa3Akj — Yash Prabhu (@yashvprabhu)
Read more