Actions
DeprecatedPortingGuideMSMQSD » History » Revision 2
« Previous |
Revision 2/72
(diff)
| Next »
Denis 'GNUtoo' Carikli, 12/24/2010 11:37 PM
Introduction
Many people bought many different phones, and some of them whish to help replicant and/or to port replicant to their phones or devices.
This guide will show what was done for the htc dream, so theses people could understand the process better. Source
lunch cyanogen_dream_sapphire-eng
}}}
you would need to identify the right command that correspond to your device, so in order to do that:
when you run the following command look at the output. {{{
$ source build/envsetup.sh
including device/geeksphone/one/vendorsetup.sh
including device/htc/ace/vendorsetup.sh
including device/htc/bravoc/vendorsetup.sh
including device/htc/bravo/vendorsetup.sh
including device/htc/buzz/vendorsetup.sh
including device/htc/glacier/vendorsetup.sh
including device/htc/heroc/vendorsetup.sh
including device/htc/inc/vendorsetup.sh
including device/htc/legend/vendorsetup.sh
including device/htc/liberty/vendorsetup.sh
including device/htc/supersonic/vendorsetup.sh
including device/htc/vision/vendorsetup.sh
including device/motorola/sholes/vendorsetup.sh
including device/nvidia/harmony/vendorsetup.sh
including vendor/cyanogen/vendorsetup.sh
}}}
The output include the list of supported(by cyanogenmod) devices.
For instance if you have the bravo phone do: {{{
$ cat device/htc/buzz/vendorsetup.sh #
Many people bought many different phones, and some of them whish to help replicant and/or to port replicant to their phones or devices.
This guide will show what was done for the htc dream, so theses people could understand the process better. Source
The first thing to do is to download the replicant sources:
[wiki:BuildDream] can be used as a reference: download and build the sources for your device.
Let's say the user has an htc wildfire.
lunch cyanogen_dream_sapphire-eng
}}}
you would need to identify the right command that correspond to your device, so in order to do that:
when you run the following command look at the output. {{{
$ source build/envsetup.sh
including device/geeksphone/one/vendorsetup.sh
including device/htc/ace/vendorsetup.sh
including device/htc/bravoc/vendorsetup.sh
including device/htc/bravo/vendorsetup.sh
including device/htc/buzz/vendorsetup.sh
including device/htc/glacier/vendorsetup.sh
including device/htc/heroc/vendorsetup.sh
including device/htc/inc/vendorsetup.sh
including device/htc/legend/vendorsetup.sh
including device/htc/liberty/vendorsetup.sh
including device/htc/supersonic/vendorsetup.sh
including device/htc/vision/vendorsetup.sh
including device/motorola/sholes/vendorsetup.sh
including device/nvidia/harmony/vendorsetup.sh
including vendor/cyanogen/vendorsetup.sh
}}}
The output include the list of supported(by cyanogenmod) devices.
For instance if you have the bravo phone do: {{{
$ cat device/htc/buzz/vendorsetup.sh #
- Copyright (C) 2008 The Android Open Source Project #
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at #
- http://www.apache.org/licenses/LICENSE-2.0 #
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License. #
- This file is executed by build/envsetup.sh, and can use anything
- defined in envsetup.sh. #
- In particular, you can add lunch options with the add_lunch_combo
- function: add_lunch_combo generic-eng
add_lunch_combo generic_buzz-eng
}}}
Then build the source, backup what's on your device, including the operating system, and flash the new replicant image.
Updated by Denis 'GNUtoo' Carikli over 14 years ago · 2 revisions