M P Mathugama
M P Mathugama

Reputation: 1418

Build AOSP for Desire S

I downloaded AOSP from http://source.android.com & follow the steps of building the system as mentioned. Got system.img and other img files in the building process of the code. Then I fastboot system img to my android htc desire s device. it installed successfully. But when device reboots, it gets stuck in htc logo. I also tried installing imgs in many different ways. nothing worked.

As cyanogenmod & other custom rom designing companies have created custom roms for htc desire, etc, I would like to know how they have solved that issue. What can be the reason for this. Same code works fine in emulator. I saw that AOSP only works in Google nexus devices. For other devices, in order it to work properly need to have drivers (proprietary binaries). Is that true? If so how can I create my own custom rom by using AOSP? How can I get the proprietary binaries for Desire S or any other device except google's devices?

**Does this AOSP only natively works in Nexsus devices? If so what is the use of it as open source?

Really appreciate any positive reply on this.

Thanks.

Upvotes: 3

Views: 1607

Answers (1)

Yury
Yury

Reputation: 20936

Even for Google phones you need proprietary drivers. Proprietary drivers are needed to work with hardware on a low level. On a higher level you have Hardware Abstraction Layer. Linux kernel of Android works with this HAL and do not work with these proprietary drivers. All other layers of Android (and what you mean under AOSP) work with Linux kernel.

Thus, for every device you need proprietary drivers that are usually should be put into device or vendor directory of AOSP. Just try to find drivers for your phone and find instruction how to build AOSP for your phone.

Upvotes: 3

Related Questions