下面是HTC官方的一个图片,展示了Android系统从发布最终到用户手中的一个完整的过程:

Awesome Infographic: HTC Shows Us “The Anatomy of an Android OS Update” From PDK to OTA

Ever wonder what the entire process of an Android update looks like? How and when do carriers get involved? Who are all of the players? How much quicker or fewer steps are there for developer or Google Play editions? When do manufacturers see the newest version of Android? All of that can be found in a lengthy infographic that HTC posted theirSoftware Updatespage, a spot that gives the status on current HTC phones and when they plan to push updates to them.

The image takes you on a journey of three different device types: carrier, unlocked/developer, and Google Play edition. You’ll see where an update can get caught up in the system, how much easier it is for HTC to get updates ready for non-carrier phones, and more.

You can find the entire infographic below, but I found a couple of points in particular interesting:

  • According to HTC’s count, Developer/unlocked and Google Play edition devices see 3 and 4 fewer steps through an update life cycle than carrier-tied devices do.
  • Chipset manufacturers have a lot more say in updates than I think any of us ever consider. Should one of them decide that their chipsets won’t work well with a new version of Android, there is a chance that that particular phone is done for good with no new drivers made available.
  • Even though most phone OEMs are making single devices that hit each carrier, there is still a lot of carrier customization done in terms of software that takes time during the process, especially should one not approve an initial build.
  • OEMs are receiving a Platform Developer Kit (PDK), however, they get new Android version source when the rest of us do, which is not until Google makes it available.

If you sneak over toHTC’s new status update page, you’ll see how the carrier-tied versions of HTC One are coming along through the process. At this point, HTC would put them in the “Integration” stage which means the update has a ways to go. The “Integration” stage is where HTC works with carriers to decide if any software modifications are needed before implementing them, doing internal testing, letting carriers test, and then hopefully getting final approval for a push.

Also, you may want to bookmark that page.

更多相关文章

  1. Android的init过程(二):初始化语言(init.rc)解析
  2. Android官方ORM数据库Room技术解决方案简介(一)
  3. Android跨进程通信之Proxy与Stub(三)
  4. android编译过程详解(一)
  5. Android(安卓)webkit image的加载过程解析(二)
  6. Android(安卓)核心分析 之八------Android(安卓)启动过程详解
  7. Android(安卓)核心分析 之八------Android(安卓)启动过程详解
  8. 自定义tabhost实现
  9. 基于Android官方DrawerLayout实现抽屉导航菜单

随机推荐

  1. Android底部菜单栏的实现
  2. Android中获取手机支持的硬件解码器类型
  3. android:Kotlin Java Kotlin android Kot
  4. API 23 widget.ImageView——属性分析
  5. Android 项目基础之XML
  6. 一篇讲的很细很好的帖子
  7. android 键盘状态,获取键盘显示和隐藏
  8. Unity—Android通讯
  9. CheckedTextView 显示问题
  10. android 常见问题解决