DeprecatedPortingGuideMSMQSD » History » Version 5
Denis 'GNUtoo' Carikli, 12/24/2010 11:42 PM
| 1 | 1 | Denis 'GNUtoo' Carikli | == Introduction == |
|---|---|---|---|
| 2 | Many people bought many different phones, and some of them whish to help replicant and/or to port replicant to their phones or devices. |
||
| 3 | This guide will show what was done for the htc dream, so theses people could understand the process better. |
||
| 4 | |||
| 5 | == Source == |
||
| 6 | 2 | Denis 'GNUtoo' Carikli | |
| 7 | The first thing to do is to download the replicant sources: |
||
| 8 | [wiki:BuildDream] can be used as a reference: download and build the sources for your device. |
||
| 9 | Let's say the user has an htc wildfire. |
||
| 10 | |||
| 11 | The main difference will be that instead of doing that: |
||
| 12 | {{{ |
||
| 13 | lunch cyanogen_dream_sapphire-eng |
||
| 14 | }}} |
||
| 15 | you would need to identify the right command that correspond to your device, so in order to do that: |
||
| 16 | when you run the following command look at the output. |
||
| 17 | {{{ |
||
| 18 | $ source build/envsetup.sh |
||
| 19 | including device/geeksphone/one/vendorsetup.sh |
||
| 20 | including device/htc/ace/vendorsetup.sh |
||
| 21 | including device/htc/bravoc/vendorsetup.sh |
||
| 22 | including device/htc/bravo/vendorsetup.sh |
||
| 23 | including device/htc/buzz/vendorsetup.sh |
||
| 24 | including device/htc/glacier/vendorsetup.sh |
||
| 25 | including device/htc/heroc/vendorsetup.sh |
||
| 26 | including device/htc/inc/vendorsetup.sh |
||
| 27 | including device/htc/legend/vendorsetup.sh |
||
| 28 | including device/htc/liberty/vendorsetup.sh |
||
| 29 | including device/htc/supersonic/vendorsetup.sh |
||
| 30 | including device/htc/vision/vendorsetup.sh |
||
| 31 | including device/motorola/sholes/vendorsetup.sh |
||
| 32 | including device/nvidia/harmony/vendorsetup.sh |
||
| 33 | including vendor/cyanogen/vendorsetup.sh |
||
| 34 | }}} |
||
| 35 | The output include the list of supported(by cyanogenmod) devices. |
||
| 36 | For instance if you have the bravo phone do: |
||
| 37 | {{{ |
||
| 38 | $ cat device/htc/buzz/vendorsetup.sh |
||
| 39 | # |
||
| 40 | # Copyright (C) 2008 The Android Open Source Project |
||
| 41 | # |
||
| 42 | # Licensed under the Apache License, Version 2.0 (the "License"); |
||
| 43 | # you may not use this file except in compliance with the License. |
||
| 44 | # You may obtain a copy of the License at |
||
| 45 | # |
||
| 46 | # http://www.apache.org/licenses/LICENSE-2.0 |
||
| 47 | # |
||
| 48 | # Unless required by applicable law or agreed to in writing, software |
||
| 49 | # distributed under the License is distributed on an "AS IS" BASIS, |
||
| 50 | # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
||
| 51 | # See the License for the specific language governing permissions and |
||
| 52 | # limitations under the License. |
||
| 53 | # |
||
| 54 | |||
| 55 | # This file is executed by build/envsetup.sh, and can use anything |
||
| 56 | # defined in envsetup.sh. |
||
| 57 | # |
||
| 58 | # In particular, you can add lunch options with the add_lunch_combo |
||
| 59 | # function: add_lunch_combo generic-eng |
||
| 60 | |||
| 61 | add_lunch_combo generic_buzz-eng |
||
| 62 | }}} |
||
| 63 | 3 | Denis 'GNUtoo' Carikli | Note that the developper is supposed to know the code of his device, that is to say that the htc wildfire correspond to the "buzz" codename. |
| 64 | 4 | Denis 'GNUtoo' Carikli | then instead of typing that: |
| 65 | {{{ |
||
| 66 | lunch cyanogen_dream_sapphire-eng |
||
| 67 | }}} |
||
| 68 | type what correspond to your device: |
||
| 69 | 3 | Denis 'GNUtoo' Carikli | {{{ |
| 70 | lunch generic_buzz-eng |
||
| 71 | }}} |
||
| 72 | 2 | Denis 'GNUtoo' Carikli | Then build the source, backup what's on your device, including the operating system, and flash the new replicant image. |
| 73 | 5 | Denis 'GNUtoo' Carikli | |
| 74 | Then test what works and what doesn't. |