I recently became aware of a project named Android-x86 that lets Android run on an x86 platform like a laptop or a desktop running an x86 processor.Some may wonder why someone would want to do this to a perfectly good tablet OS, but to a developer, the reasons are more obvious you can test software more easily and quickly than with a small Android device, you can set up dual-boot configurations to make Android accessible on machines with lots of resources, you can test different display and peripheral configurations more easily than on a small Android device.So I decided to download the source, configure the kernel and compile locally for my requirements.
![]() Because of the much wider adoption of Linux since I started using it, and because of a more complete set of runtime modules, most things I added by hand in the old days are now included by default in stock kernels. ![]() So moving Android to a laptop or desktop environment represents a philosophical as well as practical departure. My primary reason for this project was to make the kernel more accommodating of different system requirements. Wifi On Android X86 Code This GuideAfter struggling to decode this guide, I decided to start over and craft my own methods and my own description. Notwithstanding that the point of this project is to modify just the kernel, its necessary to have the entire Android source present for the compilation. The following list of steps assumes a UbuntuKubuntu Linux working environment, but it should be reasonably portable across Linux distributions. This plan also tries for the least amount of effort and complexity it modifies and compiles a new Android kernel, then drops this replacement into the directory tree of a stock Android-x86 installation. The command below should provide most of them, or tell you that you already have them. Visit the source page to see the options, and as time passes, this specification is likely to change. Therefore I recommend making a backup copy, because any number of errors in what follows could corrupt the directory tree in a way that might require it to be replaced. Open a shell in the android-x86 directory and execute the instructions below (or create a shell script to execute them). In my case, to make desktop operation possible, I needed to add SATA drive support, and the drivers needed to be statically linked. This action will place the changes in the file we created above with the advantage that it is located outside the source tree, so if we must replace or refresh the source, our configuration changes will be preserved. Before we actually perform a compilation run, I want to strongly recommend the use of distcc, a utility that distributes compilation tasks across multiple machines to improve speed. ZEROCONFtrue very important: means no distcc host file needs to be maintained. Move into the android-x86 source directory and issue these commands (or write a shell script to run them). I should warn you that people in the Android-x86 discussion forum report compilations that take days, because they have just one computer, and one thats not meant for development work. This is why I recommend distcc on every machine you can get your hands on and network up. In most cases skipping this step will produce a much quicker result. It also shows why its important to locate the custom configuration outside the source tree.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |