S3C6410板载Android体验与Netbook便携开发

需积分: 0 22 下载量 21 浏览量 更新于2024-08-02 收藏 3.11MB PDF 举报
本文档探讨了将Android作为嵌入式平台的实践经验,分为两个主要话题:在基于S3C6410的目标板上体验Android以及在便携式Netbook上实现Android。作者GeunSik Lim来自三星电子,通过深入剖析移动平台历史、Android内核特性、交叉编译构建内核以及针对S3C6410芯片的定制化过程,为我们揭示了如何在特定硬件平台上实现Android。 首先,作者回顾了Linux基础的移动平台发展史,概述了Android平台的整体架构,包括其源代码管理和维护的网站。这些网站包括Android Git存储库(git://Android.git.kernel.org),这是一个基于Git的源代码控制系统,提供代码贡献、邮件列表、文档、路线图等功能,同时还有官方Android开发者网站(source.android.com)和Android Market(code.google.com/Android/和www.android.com/market/),后者提供了SDK(Software Development Kit)以及开发人员指南和教程,帮助开发者创建新的应用程序。 话题一专注于S3C6410为基础的硬件平台,详细介绍了如何针对此设备进行Android内核的开发和移植。S3C6410KernelSummary部分可能涵盖了该处理器的特性和优化,以及在该硬件上运行Android时所面临的技术挑战。开发者需要了解如何进行跨平台编译,以便让操作系统适应不同的硬件环境。 话题二则探讨了将Android移植到Netbook这样的便携式设备上,这涉及到适配不同屏幕尺寸、输入设备和性能需求的过程。可能涉及的挑战包括系统优化、UI调整和资源管理,以确保在移动和桌面环境下提供一致的用户体验。 通过本文,读者可以了解到如何在嵌入式设备和传统便携设备上成功实施和优化Android平台,这对于硬件制造商、系统集成商和Android开发者来说都是极具价值的信息资源。
2019-02-18 上传
Android’s growth is phenomenal. In a very short time span, it has succeeded in becoming one of the top mobile platforms in the market. Clearly, the unique combination of open source licensing, aggressive go-to-market, and trendy interface is bearing fruit for Google’s Android team. Needless to say, the massive user uptake generated by Android has not gone unnoticed by handset manufacturers, mobile network operators, silicon manufacturers, and app developers. Products, apps, and devices “for,” “compatible with,” or “based on” Android seem to be coming out ever so fast. Beyond its mobile success, however, Android is also attracting the attention of yet another, unintended crowd: embedded systems developers. While a large number of embedded devices have little to no human interface, a substantial number of devices that would traditionally be considered “embedded” do have user interfaces. For a goodly number of modern machines, in addition to pure technical functionality, developers creating user-facing devices must also contend with human-computer interaction (HCI) factors. Therefore, designers must either present users with an experience they are already familiar with or risk alienating users by requiring them to learn a lesserknown or entirely new user experience. Before Android, the user interface choices available to the developers of such devices were fairly limited and limiting. Clearly, embedded developers prefer to offer users an interface they are already familiar with. Although that interface might have been window-based in the past—and hence a lot of embedded devices were based on classic window-centric, desktop-like, or desktopbased interfaces—Apple’s iOS and Google’s Android have forever democratized the use of touch-based, iPhone-like graphical interfaces. This shift in user paradigms and expectations, combined with Android’s open source licensing, have created a groundswell of interest about Android within the embedded world.