Talk:Fire OS/Archive 1

Archive 1

Fire OS

Shouldn't this page be called the above? 213.112.134.102 (talk) 19:14, 25 September 2013 (UTC)

Fire OS 3.0 will not be made available for older devices

http://www.pocket-lint.com/news/123918-amazon-kindle-fire-os-3-0-mojito-what-is-it-and-is-it-coming-to-my-tablet 87.113.232.166 (talk) 14:58, 12 October 2013 (UTC)

Thanks 156.34.85.34 (talk) 08:24, 26 March 2023 (UTC)

When was Android forked into Fire OS? And where do you draw the line between Android (AOSP) and the rest of the software?

My edit has confused another editor and this is the right place to explain. I know [1] is a WP:PRIMARY source but I think that should tell us when Android was forked. I'm trying to tread lightly to avoid WP:OR but I can explain here. Some people might say the original Kindle included an Android fork as the user facing interface is different. This is not a simple issue as people disagree in general how an operating system is defined. In a very strict sense the Linux kernel is the operating system but a as a whole to run Android applications you have Android AOSP and that is the true OS. Note: This doesn't include Google Play or Google Applications. The homescreen is however also included in AOSP but is not part of "the underlying OS". Even Google has forked that into proprietary.

Amazon says "Based on Android 2.3.3, API level 10" and "Based on Android 2.3.3, API level 10" (note however thereunder "android:largeHeap is ignored" that I just noticed). I assumed since they say "based on Android" (but "compatible with Android" for the new Fire OS) that Android as an operating system was not forked (changed OS source code). I would need a source for that. "Compatible" however implies "forked". In both cases I guess the "non-OS" homescreen app was forked (and Amazon App store, not Google Play included). comp.arch (talk) 14:06, 13 December 2013 (UTC)

Amazon forks the AOSP code each time they create their versions of Fire OS seeWhat is a fork?. The fork part (where Amazon change's the OS source code) is that Amazon has to create its own set of APIs to interface with Android, since they cannot use Google's set of APIs since they are not following Google's standards. Frmorrison (talk) 21:55, 13 December 2013 (UTC)

Fire OS provides all the Android (AOSP) APIs (what they mean by "compatible"). What is excluded are Google's proprieatry APIs, that are not part of Android. From the good link you provided: "Making devices without Google's apps has nothing to do with forking Android." comp.arch (talk) 13:41, 16 December 2013 (UTC)

Rewrote and sourced section on Android incompatibility.

The previous reading sounded like it was impossible to sideload applications from Google Play store and others or root and install Google Play store and Google Services Framework. That's ridiculous and there are over 30 sources with information on how to do these things in my first page of searching DuckDuckGo from the last 3 years. If you don't like the sources then there are plenty more to pick through but you certainly can sideload or root/install Google Play, Google Mail, Google Maps, YouTube, etc. Sideloading Google Mail won't work as it requires password services to Google Framework but Google Maps and YouTube work sideloaded. 97.85.173.38 (talk) 01:10, 21 November 2014 (UTC)

The article *still* implies that Kindle Fires can't run non Amazon software. While it's not trivially easy, it's pretty straightforward to sideload Google Play. It's also fairly easy to replace the dreadful Fire app launcher with something better (I'm typing this on a KF7 using Microsoft Edge and the Google launcher). --Ef80 (talk) 21:51, 23 November 2018 (UTC)

Foxconn manufactures Fire Phones

In the main article, the last paragraph in the Features section states that "Members of the Open Handset Alliance (which include the majority of Android OEMs) are contractually forbidden to produce Android devices based on forks of the OS, therefore Kindle Fire tablets are manufactured by Quanta Computer who is not an OHA member." However, Foxconn is the manufacturer of the Fire Phone and Fire HDX devices, and it is still a member of the OHA. This is because ODMs and Contract Manufacturers that are members of the OHA are not bound by platform exclusivity, only certain OEMs are. Even then, OEMs like ZTE (for example) manufactures and sells phones with its own flavour of Android without any Google apps – the ZTE Blade S6 –, as well as with the full Google experience. So no, Amazon has not had to resort to a non-OHA manufacturer to produce the Fire devices, since Foxconn is making them and it is an OHA member. 2620:0:1050:9:A14F:2F1A:ED0E:B6CE (talk) 10:12, 15 July 2015 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified one external link on Fire OS. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive https://web.archive.org/web/20140209072904/https://android.googlesource.com/platform/system/core/+/master/toolbox/ to https://android.googlesource.com/platform/system/core/+/master/toolbox/

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 23:28, 31 December 2016 (UTC)