Project

General

Profile

DeprecatedPortingGuideMSMQSD » History » Version 63

Paul Kocialkowski, 08/22/2011 05:20 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 33 Michael Haas -
This guide will show what was done for the htc dream, so these people can understand the process better.
4 34 Michael Haas -
When talking about porting, this page talks about re-using existing product definitions. You will not learn how to
5
build Android for a device not currently supported by Android. Instead, you will learn how to build a version of
6
[Cyanogenmod http://www.cyanogenmod.com/] without proprietary parts.
7 35 Michael Haas -
To gain more insight in the Android build system, refer to [http://source.android.com/porting/build_system.html Android Build System documentation] which is part of
8 34 Michael Haas -
[http://source.android.com/porting/ Android Platform Developer's Guide]. You should find an answer there if you have any questions about the Makefiles referenced in this document.
9 32 Michael Haas -
10 62 Igor Almeida -
Note: The Android Build System documentation above has been removed. You can find a mirror of the (outdated) documentation [http://www.kandroid.org/online-pdk/guide/index.html here] and [http://www.netmite.com/android/mydroid/development/pdk/docs/ here].
11
12 1 Denis 'GNUtoo' Carikli
== Terminology ==
13 33 Michael Haas -
The RIL is the radio interface library, that is to say, a library that talks to the modem, usually (but not always) trough AT commands.
14 32 Michael Haas -
Basically the modem runs on a separate CPU,and there is some sort of communication needed between the main CPU and the modem CPU to make telephony work. For instance, the modem must tell you when you've got a call, and you must tell the modem that you want to call someone.
15 1 Denis 'GNUtoo' Carikli
TODO: point to 0707 standard or newer
16
17 31 Denis 'GNUtoo' Carikli
== Help with source code ==
18 32 Michael Haas -
Keep in mind that on most devices, the full source code of the kernel is released.
19
However, some userspace libraries, or dlopened libraries (libraries loaded at runtime after the application started) are proprietary software,
20 31 Denis 'GNUtoo' Carikli
so if you're porting to a new CPU/SOC keep in mind that you have the source code to the kernel interfaces.
21
That can help a lot, and sometimes there is even some sort of documentation in the headers.
22 1 Denis 'GNUtoo' Carikli
23
== Build the source ==
24
25
The first thing to do is to download the replicant sources:
26
[wiki:BuildDream] can be used as a reference: download and build the sources for your device.
27 32 Michael Haas -
Let's say the user has a HTC Wildfire. It is useful to know the codename of the device in question, which is "Buzz" in case
28
of the Wildfire.
29 1 Denis 'GNUtoo' Carikli
30 32 Michael Haas -
You need to configure the build tree for our device. By default, a generic image
31
for the Android emulator will be built. 
32
In [wiki:BuildDream], you would use the following command to set up the build:
33 2 Denis 'GNUtoo' Carikli
{{{
34
lunch cyanogen_dream_sapphire-eng 
35
}}}
36 32 Michael Haas -
Now, since you are not building for the HTC dream, you need to identify the right command that corresponds to your device.
37
In order to do that, run the following command and look at its output.
38 2 Denis 'GNUtoo' Carikli
{{{
39
$ source build/envsetup.sh
40
including device/geeksphone/one/vendorsetup.sh
41
including device/htc/ace/vendorsetup.sh
42
including device/htc/bravoc/vendorsetup.sh
43
including device/htc/bravo/vendorsetup.sh
44
including device/htc/buzz/vendorsetup.sh
45
including device/htc/glacier/vendorsetup.sh
46 1 Denis 'GNUtoo' Carikli
including device/htc/heroc/vendorsetup.sh
47
including device/htc/inc/vendorsetup.sh
48 2 Denis 'GNUtoo' Carikli
including device/htc/legend/vendorsetup.sh
49
including device/htc/liberty/vendorsetup.sh
50
including device/htc/supersonic/vendorsetup.sh
51
including device/htc/vision/vendorsetup.sh
52
including device/motorola/sholes/vendorsetup.sh
53
including device/nvidia/harmony/vendorsetup.sh
54
including vendor/cyanogen/vendorsetup.sh
55
}}}
56 37 Denis 'GNUtoo' Carikli
The last line is important:
57 1 Denis 'GNUtoo' Carikli
{{{
58 37 Denis 'GNUtoo' Carikli
$ cat vendor/cyanogen/vendorsetup.sh
59
add_lunch_combo cyanogen_ace-eng
60
add_lunch_combo cyanogen_bravo-eng
61
add_lunch_combo cyanogen_bravoc-eng
62
add_lunch_combo cyanogen_buzz-eng
63
add_lunch_combo cyanogen_dream_sapphire-eng
64
add_lunch_combo cyanogen_espresso-eng
65
add_lunch_combo cyanogen_glacier-eng
66
add_lunch_combo cyanogen_harmony-eng
67
add_lunch_combo cyanogen_hero-eng
68
add_lunch_combo cyanogen_heroc-eng
69
add_lunch_combo cyanogen_inc-eng
70
add_lunch_combo cyanogen_legend-eng
71
add_lunch_combo cyanogen_liberty-eng
72
add_lunch_combo cyanogen_one-eng
73
add_lunch_combo cyanogen_passion-eng
74
add_lunch_combo cyanogen_sholes-eng
75
add_lunch_combo cyanogen_supersonic-eng
76
add_lunch_combo cyanogen_vibrant-eng
77
add_lunch_combo cyanogen_vision-eng
78
add_lunch_combo cyanogen_z71-eng
79 4 Denis 'GNUtoo' Carikli
80 37 Denis 'GNUtoo' Carikli
PATH=$PATH:$PWD/vendor/cyanogen/tools ; export PATH
81 4 Denis 'GNUtoo' Carikli
}}}
82 37 Denis 'GNUtoo' Carikli
The output include the list of supported (by cyanogenmod) devices.
83
For instance if you have the Wildfire (codename 'buzz') phone do:
84 36 Michael Haas -
{{{
85 1 Denis 'GNUtoo' Carikli
lunch cyanogen_buzz-eng
86 36 Michael Haas -
}}}
87
88 1 Denis 'GNUtoo' Carikli
Then build the source, backup what's on your device, including the operating system, and flash the new replicant image.
89 9 Denis 'GNUtoo' Carikli
90
Then test what works and what doesn't.
91 1 Denis 'GNUtoo' Carikli
92
The images are located in 
93
{{{
94
out/target/product/dream_sapphire
95 32 Michael Haas -
}}}
96 8 Denis 'GNUtoo' Carikli
in the case of the HTC Dream. You need to look in the path that corresponds to your device.
97 1 Denis 'GNUtoo' Carikli
98
== Trying free replacements ==
99 32 Michael Haas -
100
The source code you just built contains some free replacements for the proprietary
101
libraries shipped by your phone vendor with the default firmware.
102
103 1 Denis 'GNUtoo' Carikli
A list of proprietary libraries is available in
104 10 Denis 'GNUtoo' Carikli
{{{
105
device/htc/dream_sapphire/extract-files.sh
106 32 Michael Haas -
}}}
107
Note: don't run this file, just look at it. If you run it, the proprietary files will be copied from your phone into the build tree. A build containing proprietary files would put you and
108 1 Denis 'GNUtoo' Carikli
your users at risk. Additionally, it is illegal to redistribute such build, because the libraries are not redistributable(the copyright owner didn't allow you to redistribute them).
109 32 Michael Haas -
110
111
=== RIL test ===
112
I will take the example of how to use the free RIL (Radio Interface Library) to see if it works fine without modifications:
113 11 Denis 'GNUtoo' Carikli
The proprietary RIL library (which you don't have in the phone) location is found looking at the extract-files.sh
114
here's a part of extract-files.sh:
115
{{{
116
adb pull /system/lib/libhtc_ril.so ../../../vendor/htc/$DEVICE/proprietary/libhtc_ril.so
117 32 Michael Haas -
}}}
118
Note: don't run this command, just look at it. If you run it, the proprietary files will be copied from your phone into the build tree. A build containing proprietary files would put you and
119
your users at risk. Additionally, it is illegal to redistribute such build, because the libraries are not redistributable(the copyright owner didn't allow you to redistribute them).
120
121 12 Denis 'GNUtoo' Carikli
So looking at the above line the proprietary RIL is located here on the phone:
122
{{{
123
/system/lib/libhtc_ril.so
124 32 Michael Haas -
}}}
125 13 Denis 'GNUtoo' Carikli
while the free ril is located here (known fact):
126 14 Denis 'GNUtoo' Carikli
{{{
127 1 Denis 'GNUtoo' Carikli
/system/lib/libreference-ril.so
128 32 Michael Haas -
}}}
129 13 Denis 'GNUtoo' Carikli
In order to test the free RIL you could be tempted to do that:
130 14 Denis 'GNUtoo' Carikli
{{{
131 15 Denis 'GNUtoo' Carikli
# ./adb remount
132 14 Denis 'GNUtoo' Carikli
# ./adb shell
133 1 Denis 'GNUtoo' Carikli
mv /system/lib/libreference-ril.so /system/lib/libhtc_ril.so
134
}}}
135
But that wouldn't work as it wouldn't be using the right serial port, the correct way to try that is to use getprop/setprop:
136 14 Denis 'GNUtoo' Carikli
{{{
137 1 Denis 'GNUtoo' Carikli
# ./adb shell
138
# setprop
139
usage: setprop <key> <value>
140 32 Michael Haas -
}}}
141 39 Konstantinos Karantias -
What you can do to set the libre RIL is - possibly - this:
142
{{{
143
./adb shell
144
setprop rild.libpath /system/lib/libreference-ril.so
145
setprop rild.libargs -d/dev/smd0
146
}}}
147 13 Denis 'GNUtoo' Carikli
Here's how it looks on a working replicant on the HTC Dream:
148
{{{
149
# ./adb shell
150
# getprop | grep ril
151
[ro.ril.hsxpa]: [2]
152
[ro.ril.gprsclass]: [10]
153 1 Denis 'GNUtoo' Carikli
[rild.libpath]: [/system/lib/libreference-ril.so]
154
[rild.libargs]: [-d/dev/smd0]
155 15 Denis 'GNUtoo' Carikli
[init.svc.ril-daemon]: [running]
156
[ro.ril.def.agps.mode]: [2]
157 32 Michael Haas -
[gsm.version.ril-impl]: [android reference-ril 1.0]
158 14 Denis 'GNUtoo' Carikli
}}}
159 12 Denis 'GNUtoo' Carikli
 * /dev/smd0 is the (emulated) serial port
160
 * /system/lib/libreference-ril.so is where to look for the RIL hardware specific library 
161 1 Denis 'GNUtoo' Carikli
162 39 Konstantinos Karantias -
Then, you can kill the ril daemon:
163 1 Denis 'GNUtoo' Carikli
{{{
164 39 Konstantinos Karantias -
./adb shell killall rild
165 1 Denis 'GNUtoo' Carikli
}}}
166 39 Konstantinos Karantias -
Then try the reference RIL. You can see debugging things and such by doing:
167
{{{
168
./adb logcat -b radio
169
}}}
170
171
That's also tested and worked on the gtklocker's HTC Hero, so I suppose it will work for the most HTC devices out there. If your device isn't listed anywhere, don't dare to try it.
172 32 Michael Haas -
173 16 Denis 'GNUtoo' Carikli
== Replacing proprietary libraries for real ==
174 32 Michael Haas -
175
On the HTC Dream the following proprietary libraries were replaced:
176 16 Denis 'GNUtoo' Carikli
(Refer to [wiki:ProprietaryHtcDreamLibsReplacement] for more up to date details(or fix it if it's less recent))
177
178
The first thing you will have to do is to modify the build system.
179 1 Denis 'GNUtoo' Carikli
The key thing to do is to change 
180 32 Michael Haas -
181
=== RIL ===
182
If the RIL you previously tried works fine, why not switching to it...directly in the build system.
183 16 Denis 'GNUtoo' Carikli
Here's the diff between A working RIL and a non-working RIL for the htcdream:
184
{{{
185
android_device_htc_dream_sapphire$ git diff 5593d2899203ec378c306701788f1c43af9a6935 -- full_dream_sapphire.mk
186
diff --git a/full_dream_sapphire.mk b/full_dream_sapphire.mk
187
index 9ec7feb..eb1b956 100644
188
--- a/full_dream_sapphire.mk
189
+++ b/full_dream_sapphire.mk
190
@@ -40,7 +40,8 @@ PRODUCT_PROPERTY_OVERRIDES := \
191
     ro.media.dec.jpeg.memcap=10000000
192
 
193
 PRODUCT_PROPERTY_OVERRIDES += \
194
-    rild.libpath=/system/lib/libhtc_ril.so \
195
+    rild.libpath=/system/lib/libreference-ril.so \
196
+    rild.libargs=-d/dev/smd0 \
197
     wifi.interface=tiwlan0
198 17 Denis 'GNUtoo' Carikli
 
199
 # Time between scans in seconds. Keep it high to minimize battery drain.
200
201
}}}
202
Note that full_dream_sapphire.mk is located here:
203
{{{
204 18 Denis 'GNUtoo' Carikli
device/htc/dream_sapphire/full_dream_sapphire.mk
205
}}}
206
The diff is self-explanatory and how to do the change is left as an exercise to the reader.
207 32 Michael Haas -
208 18 Denis 'GNUtoo' Carikli
In case the RIL need to be modified the sources are in :
209 19 Denis 'GNUtoo' Carikli
{{{
210
hardware/ril/reference-ril
211
}}}
212 21 Denis 'GNUtoo' Carikli
They are written in C.
213 19 Denis 'GNUtoo' Carikli
214 32 Michael Haas -
=== Audio libraries ===
215
On the HTC dream the audio libraries were modified.
216 40 Denis 'GNUtoo' Carikli
If your device is an msm7k "CPU" (in reality it's called a SOC, or system on a chip), it already contain [http://gitorious.org/replicant/android_hardware_msm7k/commit/e0b55a19b2fc004915503ebdfd7c4c02c4264611 the routing fix].
217
Note several things on [http://gitorious.org/replicant/android_hardware_msm7k/commit/e0b55a19b2fc004915503ebdfd7c4c02c4264611 the commit]:
218 22 Denis 'GNUtoo' Carikli
 * the routing was disabled, I had to re-enable it
219 28 Denis 'GNUtoo' Carikli
 * I had to replace some non-existant functions, for that I used public playwav2.c source code that the author released to us under the apache 2.0 license.
220
 * I had nearly no knowledge of C++
221 32 Michael Haas -
 * it was easy
222 28 Denis 'GNUtoo' Carikli
223 41 Denis 'GNUtoo' Carikli
On the nexus one the proprietary libacoustic libraries are only used for bluetooth(all the rest works if you pushed the firmwares).
224
225 58 Paul Kocialkowski
On the dream (msm7k), libacoustic has been fully replaced, see [http://gitorious.org/replicant/android_hardware_msm7k/commit/c650b45892aa8be87f3e88ee6eae5df053a0a047]: it loads the values from the /system/etc/AudioPara4.csv CSV file to MSM shared memory, which fixes in-call volume regulation and adds support for No Mic Wired Headset. It should also add support for other other things (probably including bluetooth devices) but this has not been tested yet. 
226 56 Paul Kocialkowski
The existing replacement code (hardware/msm7k/libaudio/AudioAcoustic.cpp) should work for your msm7k device but it has only been tested on the Dream. 
227 1 Denis 'GNUtoo' Carikli
228 61 Paul Kocialkowski
'''Note that (even if unconfirmed) it should more likely work the same way for every msm7k device, so try the code without any modification first and do the following steps only if the code does not work for your msm7k device! '''
229 60 Paul Kocialkowski
230 59 Paul Kocialkowski
If it does not work, check that your device contains the /system/etc/AudioPara4.csv CSV file. If it does not, the file may have another name, then you should modify replicant code to use the filename of your device and test if it works.
231 1 Denis 'GNUtoo' Carikli
232 59 Paul Kocialkowski
If you don't see any CSV file anywhere, then your device must not work like HTC Dream and you'll probably have to write the code to support acoustic or find another working replacement. You can read jbruneaux's work on audio acoustic for WinCE devices from {{{ git://gitorious.org/~jbruneaux/xdandroid/hardware_msm7k_libacoustic.git }}} (userland) and {{{ git://gitorious.org/linux-on-qualcomm-s-msm/linux-msm-home-work.git }}} branch {{{ htc-msm-2.6.27-libacoustic }}} (kernel-space). Note that audio acoustic is not absolutely necessary to make audio work, it'll just cause some minor issues as written above. 
233
234 56 Paul Kocialkowski
To make sure it parses the CSV file, run adb logcat | grep Audio and find the following lines: 
235 1 Denis 'GNUtoo' Carikli
{{{
236 56 Paul Kocialkowski
D/AudioAcousticMSM72XX(  122): Successfully opened /system/etc/AudioPara4.csv
237
D/AudioAcousticMSM72XX(  122): CSV Header: Dream_TMU_20090305
238
D/AudioAcousticMSM72XX(  122): Read:
239
D/AudioAcousticMSM72XX(  122): 24 Audio_Path_Table entries
240
D/AudioAcousticMSM72XX(  122): 24 Audio_Path_Uplink_Table entries
241
D/AudioAcousticMSM72XX(  122): 35 Phone_Acoustic_Table entries
242
D/AudioAcousticMSM72XX(  122): 35 BT_Phone_Acoustic_Table entries
243
D/AudioAcousticMSM72XX(  122): 24 HTC_VOC_CAL_CODEC_TABLE_Table entries
244
D/AudioAcousticMSM72XX(  122): 0 CE_Acoustic_Table entries
245 1 Denis 'GNUtoo' Carikli
}}}
246 56 Paul Kocialkowski
Then, if it parses the file but does not work, it's probably because the addresses (or the size) where the tables must be written in MSM shared memory are not the same for the Dream and for your device. 
247
In order to find the correct addresses, you'll have to use CyanogenMod code with the non-free libhtc_acoustic.so lib that you can get from CyanogenMod downloadable zip for your device.
248
move the hardware/msm7k/ directory to another place '''not in the build tree''' or it'll fail ({{{ mv hardware/msm7k/ ../msm7k }}}.
249
Then download CyanogenMod code:
250
{{{ git clone git://github.com/CyanogenMod/android_hardware_msm7k.git -b froyo-stable hardware/msm7k/ }}}
251
Now you need to modify the kernel-side driver to print some useful infos on file kernel-msm/arch/arm/mach-msm/htc_acoustic.c, function acoustic_mmap(), add the following code:
252
{{{
253
D(" -- vma dump start --\n");
254
255
D("vm_start=%x (%d)\n", vma->vm_start, vma->vm_start);
256
D("vm_end=%x (%d)\n", vma->vm_end, vma->vm_end);
257
D("vm_page_prot=%x (%d)\n", vma->vm_page_prot,vma->vm_page_prot);
258
D("vm_flags=%x (%d)\n", vma->vm_flags, vma->vm_flags);
259
D("vm_pgoff=%x (%d)\n", vma->vm_pgoff, vma->vm_pgoff);
260
261
D(" -- vma dump end --\n");
262
}}}
263
264
Then build the code (make -j9 bootimage && make-j9 systemimage), and flash system.img and boot.img to your device, boot it, copy the libhtc_acoustic.so lib to /system/lib/ (you need to remount /system using {{{ adb remount }}} to write under /system) and check the kernel logs with {{{ adb shell dmesg | grep acoustic }}}. You should see something like:
265
{{{
266
<6>[   22.250274] htc-acoustic: open
267
<6>[   22.252716] htc-acoustic: mmap
268
<6>[   22.253265] htc-acoustic:  -- vma dump start --
269
<6>[   22.254028] htc-acoustic: vm_start=4010c000 (1074839552)
270
<6>[   22.254699] htc-acoustic: vm_end=40119000 (1074892800)
271
<6>[   22.255310] htc-acoustic: vm_page_prot=38f (911)
272
<6>[   22.256011] htc-acoustic: vm_flags=400844ff (1074283775)
273
<6>[   22.256622] htc-acoustic: vm_pgoff=1f4a (8010)
274
<6>[   22.257293] htc-acoustic:  -- vma dump end --
275
<6>[   22.742675] htc-acoustic: ioctl
276
<6>[   22.743103] htc-acoustic: ioctl: ACOUSTIC_ARM11_DONE called 123.
277
<6>[   22.746612] htc-acoustic: ioctl: ONCRPC_ACOUSTIC_INIT_PROC success.
278
<6>[   22.747344] htc-acoustic: release
279
}}}
280
281 61 Paul Kocialkowski
Now you can get the size of the dedicated memory area: vm_end - vm_start = 0x40119000 - 0x4010c000 = '''0xd000'''.
282 56 Paul Kocialkowski
Then, you'll have to dump the entire memory to a file that you need to create: {{{ adb shell touch /data/dump }}}. Add a function to AudioHardware.cpp :
283
{{{
284
void acoustic_mmap_dump(void)
285
{
286
	uint8_t *test_map_base;
287
	uint8_t *ptr, nval;
288
	int fd, fdd=0;
289
	off_t TargetAddr;
290
	int len;
291
292
	fd = open("/dev/htc-acoustic", O_RDWR | O_SYNC);
293
	fdd = open("/data/dump", O_RDWR | O_TRUNC | O_CREAT);
294
295
	test_map_base = (uint8_t *)
296
	    mmap(0, 0xd000, PROT_READ | PROT_WRITE, MAP_SHARED, fd,
297
		 0);
298
//	test_virt_base = test_map_base + (TargetAddr & MAP_MASK);
299
//	LOGD("virtual base at %p (phys=0x%X)\n", test_virt_base, TargetAddr);
300
301
	LOGD(" -- htc-acoustic memory read -- \n");
302
	LOGD("beginning adress is@%p\n", test_map_base);
303
          for (len = 0; len < 0xd000; len++)
304
		{
305
			if( write(fdd, test_map_base, sizeof(uint8_t) ) < 0)
306
			{
307
				LOGE("write failed");
308
				break;
309
			}
310
			//LOGD("0x%x (%d) @%p",  *(test_map_base), *(test_map_base), test_map_base);
311
		  test_map_base++;
312
		}
313
314
315
	munmap(test_map_base, 0xd000);
316
	close(fdd);
317
	close(fd);
318 1 Denis 'GNUtoo' Carikli
}
319
}}}
320
replace 0xd000 by the size you found out and call it after {{{ int rc = set_acoustic_parameters(); }}} on the AudioHardware::AudioHardware() function.
321 58 Paul Kocialkowski
Build the code (make -j9 systemimage), flash system.img to your device and get /data/dump: {{{ adb pull /data/dump }}}. This should copy dump to your current directory. You can try to load that file in MSM shared memory at the exact place where you dumped it. To do that, add the following functions to AudioHardware.cpp (don't forget to replace the size, 0xd000 if it's different for your device):
322
{{{
323
#define ACOUSTIC_IOCTL_MAGIC 'p'
324
#define ACOUSTIC_NOTICE		_IOW(ACOUSTIC_IOCTL_MAGIC, 42, unsigned int)
325
#define ACOUSTIC_ARM11_DONE	_IOW(ACOUSTIC_IOCTL_MAGIC, 22, unsigned int)
326
327
void acoustic_mmap(void)
328
{
329
	char *test_map_base;
330
	volatile int *ptr, nval;
331
	int fd, fdd;
332
	off_t TargetAddr;
333
	int len;
334
335
	fd = open("/dev/htc-acoustic", O_RDWR | O_SYNC);
336
	fdd = open("/data/dump", O_RDWR);
337
338
	test_map_base = (char *)
339
	    mmap(0, 0xd000, PROT_READ | PROT_WRITE, MAP_SHARED, fd,
340
		 0);
341
//	test_virt_base = test_map_base + (TargetAddr & MAP_MASK);
342
//	LOGD("virtual base at %p (phys=0x%X)\n", test_virt_base, TargetAddr);
343
344
	LOGD(" -- htc-acoustic memory write -- \n");
345
          for (len = 0; len < 0xd000; len++)
346
		{
347
		  read(fdd, test_map_base, sizeof(char) );
348
		  test_map_base++;
349
		}
350
351
352
	munmap(test_map_base, 0xd000);
353
	close(fdd);
354
	close(fd);
355
}
356
357
void acoustic_done(void)
358
{
359
     int fd;
360
	       fd = open("/dev/htc-acoustic",O_RDWR);
361
362
               if (fd < 0) {
363
	            LOGE("Cannot open htc-acoustic device");
364
	            close(fd);
365
	            return;
366
               }
367
368
       ioctl(fd,ACOUSTIC_ARM11_DONE, NULL);
369
       close(fd);
370
}
371
}}}
372
Now replace:
373
{{{
374
    set_acoustic_parameters = (int (*)(void))::dlsym(acoustic, "set_acoustic_parameters");
375
    if ((*set_acoustic_parameters) == 0 ) {
376
        LOGE("Could not open set_acoustic_parameters()");
377
        return;
378
    }
379
380
    int rc = set_acoustic_parameters();
381
    if (rc < 0) {
382
        LOGE("Could not set acoustic parameters to share memory: %d", rc);
383
//        return;
384
    }
385
}}}
386
with:
387
{{{
388
acoustic_mmap();
389
acoustic_done();
390
}}}
391
392 1 Denis 'GNUtoo' Carikli
Build system.img: {{{ make -j9 systemimage }}} and flash it to your device. Now '''audioacoustic should work''' but it's not a clean way to make it work: the clean way is to parse the CSV file and load it to MSM shared memory with free code. If it does not work, then your device is definitely not working like the Dream and you'll have to find another way to make it work. 
393 59 Paul Kocialkowski
394
Replace the hardware/msm7k/ folder by the replicant one. The next step is to find the right addresses to write the tables in MSM shared memory. To find this out, you have to read the dump and understand where each table begins. So first, you have to hexdump the dump:
395
{{{ hexdump -C dump > dump.txt }}}. This will create dump.txt, containing the hexedacimal values of dump as text. So now you should be able to understand where each table begins. As an example, here's how it was done with the dream values: consider the following as the beginning of the dump.txt file: 
396
{{{
397
00000000  35 71 36 61 37 00 38 00  39 03 3a 00 3b 00 3c 00  |5q6a7.8.9.:.;.<.|
398
00000010  3d 00 3e 00 3f 00 40 00  41 1c 42 00 43 00 44 00  |=.>.?.@.A.B.C.D.|
399
00000020  45 00 46 00 47 00 48 00  49 00 4a 01 4b 00 4c 00  |E.F.G.H.I.J.K.L.|
400
00000030  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
401
*
402
00000080  35 71 36 61 37 00 38 00  39 03 3a 00 3b 00 3c 00  |5q6a7.8.9.:.;.<.|
403
00000090  3d 00 3e 00 3f 00 40 00  41 1c 42 00 43 00 44 00  |=.>.?.@.A.B.C.D.|
404
000000a0  45 00 46 00 47 00 48 00  49 00 4a 01 4b 00 4c 00  |E.F.G.H.I.J.K.L.|
405
000000b0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
406
}}}
407
it's the 2 first elements of the table we want to find the address (which will be 00000000, the beginning of the table). Now read AudioPara4.csv. On the dream, you can read:
408
{{{
409
A0,HTC_VOC_CODEC_EARCUPLE_VOICE,35,71,36,61,37,0,38,0,39,3,3A,0,3B,0,3C,0,3D,0,3E,0,3F,0,40,0,41,1C,42,0,43,0,44,0,45,0,46,0,47,0,48,0,49,0,4A,1,4B,0,4C,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
410
A1,HTC_VOC_CODEC_EARCUPLE_MIDI,35,71,36,61,37,0,38,0,39,3,3A,0,3B,0,3C,0,3D,0,3E,0,3F,0,40,0,41,1C,42,0,43,0,44,0,45,0,46,0,47,0,48,0,49,0,4A,1,4B,0,4C,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
411
}}}
412
you can see that {{{35 71 36 61 37 00 38 00  39 03 3a 00 3b 00 3c 00}} is the same as {{{ 35,71,36,61,37,0,38,0,39,3,3A,0,3B,0,3C,0 }}}, so {{{35 71 36 61 37 00 38 00  39 03 3a 00 3b 00 3c 00}} is the beginning of the first element of table A. So table A starts at 0. 
413
414
Now if you read the ParseAudioParaLine function from AudioAcoustic.cpp (on the already existing free audio acoustic code), you can see:
415
{{{
416
        case 'A':
417
[…]
418
            while ( (token = strtok(NULL, ",")) ) {
419
                Audio_Path_Table[table_num].array[field_count++] = strtol(token, &ps, 16);
420
            };
421
            break;
422
}}}
423
424
So "A" is for the Audio_Path_Table table. 
425
Now you have to do the same work for every table. You can see that another tables begins when the table-specific characters change e.g.:
426
{{{
427
00001780  35 00 36 00 37 ff 38 00  39 00 3a 00 3b 00 3c c4  |5.6.7.8.9.:.;.<.|
428
00001790  3d c4 3e 08 3f 80 40 05  41 00 42 00 43 00 44 00  |=.>.?.@.A.B.C.D.|
429
000017a0  45 00 46 00 47 00 48 00  49 00 4a 00 4b 00 4c 00  |E.F.G.H.I.J.K.L.|
430
000017b0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
431
*
432
00001800  00 00 00 40 13 20 00 00  b2 7f fd 23 00 00 33 2d  |...@. .....#..3-|
433
00001810  00 00 80 0c 9a ff 80 1d  33 f3 ec 01 ee ff 0a 20  |........3...... |
434
00001820  65 7f 00 00 00 ed 00 00  00 00 d9 3f 00 00 80 0c  |e..........?....|
435
00001830  9a ff 0c 1b 33 f3 ec 01  ee ff 0a 20 65 7f ff 7f  |....3...... e...|
436
00001840  00 08 ff 7f 9f 14 00 00  14 00 00 08 00 20 00 20  |............. . |
437
00001850  fa 00 46 00 02 00 ff 02  40 00 20 00 50 46 40 00  |..F.....@. .PF@.|
438
00001860  a0 41 00 08 63 00 ff 4d  ff 4d 02 00 00 3f d0 07  |.A..c..M.M...?..|
439
00001870  00 00 00 00 00 01 00 01  00 02 50 00 00 03 50 01  |..........P...P.|
440
00001880  64 00 a8 1c c2 01 e0 2e  a0 0f ff ff 00 00 00 00  |d...............|
441
00001890  00 00 00 00 00 00 00 00  00 40 00 00 00 00 00 00  |.........@......|
442
000018a0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
443
}}}
444
445
You can see that a new table begins at 0x1800.
446
Note that some tables may not start at easy-to-find addresses such as 0x1800 but may start at in the middle of an hexdump line (so it makes the task even harder).
447
448
When you have found all the correct addresses for every table in your CSV file, you should check that your tables have the same size than the tables you got from the dump. If it's not, adjust the tables defined in AudioAcoustic.h and the tables defined at the top of AudioAcoustic.cpp. 
449
When all that stuff is ok, it's possible that there is a necessary footer to make it work. On the Dream, it is:
450
{{{
451
0000c8e0  78 56 34 12 00 00 00 00  00 00 00 00 00 00 00 00  |xV4.............|
452
}}}
453
(present at the end of the dump file).
454
455
Now that you found out the size of the memory map, the address of each table, adjusted the size of the tables and found the footer, it's time to put the remaining infos on the free code.
456
Modify with the values you found out, on the file hardware/msm7k/libaudio/AudioAcoustic.cpp:
457
{{{
458
static int mmap_size = 0xd000;
459
static int mmap_address_audio_path_table = 0x0;
460
static int mmap_address_audio_path_uplink_table = 0xc00;
461
static int mmap_address_phone_acoustic_table = 0x1800;
462
static int mmap_address_bt_phone_acoustic_table = 0x4a00;
463
static int mmap_address_htc_voc_cal_codec_table_table = 0xc700;
464
static int mmap_address_htc_acoustic_end = 0xc8e0;
465
}}}
466
and adapt the array sizes both on the top of AudioAcoustic.cpp and AudioAcoustic.h (if you didn't do it already).
467
468
Then build an image (make -j9 systemimage) and it should work. If it does not, please check that you successfully passed all the required steps. 
469
But the fact is that you replaced Dream values with the correct values for your device, so it will break audio acoustic for Dream.
470
The solution would be to write a set_device_configuration() which selects the good values for the device we build replciant for and the appropriated tables. 
471
Nothing like that has been written yet since replicant AudioAcoustic hasn't been ported to any other device yet. Please notify replicant developers to write such a function (or do it yourself) before you send the code.
472 56 Paul Kocialkowski
473 42 Denis 'GNUtoo' Carikli
=== GPS ===
474
Two GPS libraries exist:
475
 * libgps
476
 * libloc_api
477 43 Denis 'GNUtoo' Carikli
Both provide the same functionalities at the application level.
478 1 Denis 'GNUtoo' Carikli
Choose the one that is supported by your device or that has support for a device close to your device.
479 43 Denis 'GNUtoo' Carikli
==== libgps ====
480
For adding support to libgps you need to enable it like in [http://gitorious.org/replicant/android_device_htc_dream_sapphire/commit/153ab7e8fcf6bfc294b200d60a6f01feb5bb571a this commit]:
481
add the following(or modify if it's already there but holds another value) in device/htc/dream_sapphire/BoardConfig.mk (replace dream_saphire by your device code) :
482
{{{
483
BOARD_HAVE_GPS_HARDWARE := true
484
BOARD_GPS_LIBRARIES := libhardware
485 1 Denis 'GNUtoo' Carikli
}}}
486 43 Denis 'GNUtoo' Carikli
I'm not sure if the "BOARD_HAVE_GPS_HARDWARE := true" is really needed.
487
488
If your device is different from the htc dream you may have to modify the GPS library code to match your device,
489
Here's the adaptation made for the htc dream:
490
{{{
491
hardware/libhardware_legacy/gps$ diff -u ../../../../repos_external/phh_libhardware_legacy/gps/gps-rpc.c ./gps-rpc.c 
492
--- ../../../../repos_external/phh_libhardware_legacy/gps/gps-rpc.c	2010-08-15 11:35:03.210095153 +0200
493
+++ ./gps-rpc.c	2011-01-06 16:46:45.417685002 +0100
494
@@ -464,8 +464,8 @@
495
 }
496
 
497
 int init_gps6125() {
498
-	struct CLIENT *clnt=clnt_create(NULL, 0x3000005B, 0, NULL);
499
-	struct CLIENT *clnt_atl=clnt_create(NULL, 0x3000001D, 0, NULL);
500
+	struct CLIENT *clnt=clnt_create(NULL, 0x3000005B, 0x90380d3d, NULL);
501
+	struct CLIENT *clnt_atl=clnt_create(NULL, 0x3000001D, 0x51c92bd8, NULL);
502
 	int i;
503
 	_clnt=clnt;
504
 	SVCXPRT *svc=svcrtr_create();
505
@@ -538,33 +538,21 @@
506
 
507
 
508
 int init_gps_rpc() {
509
-	int fd=open("/sys/class/htc_hw/amss", O_RDONLY);
510
-	char buf[32];
511
-	bzero(buf, 32);
512
-	read(fd, buf, 32);
513
-	if(strncmp(buf, "6125", 4)==0)
514
-		amss=A6125;
515
-	else if((strncmp(buf, "5225", 4)==0) || (strncmp(buf, "6150", 4)==0))
516
-		amss=A5225;
517
-	else
518
-		amss=A6125; //Fallback to 6125 ATM
519
-	if(amss==A6125)
520
-		init_gps6125();
521
-	else if(amss==A5225)
522
-		init_gps5225();
523
+	amss=A6125;
524
+	init_gps6125();
525
 	return 0;
526
 }
527
 
528
 void gps_get_position() {
529
 	int i;
530
-	for(i=5;i;--i) if(!can_send) sleep(1);//Time out of 5 seconds on can_send
531
+	for(i=3;i;--i) if(!can_send) sleep(1);//Time out of 5 seconds on can_send
532
 	can_send=0;
533
 	pdsm_get_position(_clnt, 0, 0, 1, 1, 1, 0x3B9AC9FF, 1, 0,0,0,0,0, 0,0,0,0,0, 0,0,0,0,0, 0,0,1,32,2,client_IDs[2]);
534
 }
535
 
536
 void exit_gps_rpc() {
537
-	if(amss==A6125)
538
-		pdsm_client_end_session(_clnt, 0, 2);
539
+	//if(amss==A6125)
540
+	//	pdsm_client_end_session(_clnt, 0, 2);
541
 	//5225 doesn't seem to like end_session ?
542
 	//Bah it ends session on itself after 10seconds.
543 1 Denis 'GNUtoo' Carikli
 }
544 44 Denis 'GNUtoo' Carikli
}}}
545
546
so let's go step by steps on that diff:
547
First we see that:
548
{{{
549
+	struct CLIENT *clnt=clnt_create(NULL, 0x3000005B, 0x90380d3d, NULL);
550
+	struct CLIENT *clnt_atl=clnt_create(NULL, 0x3000001D, 0x51c92bd8, NULL);
551
}}}
552
This corresponds to some devices nodes:
553
{{{
554
# ls -l /dev/oncrpc
555
crw-rw----    1 radio    system    253,   0 Jan  6 16:43 00000000:0
556
crw-rw----    1 radio    system    253,  11 Jan  6 16:43 30000000:5a10cf88
557
crw-rw----    1 radio    system    253,   9 Jan  6 16:43 30000002:aa2b1a44
558
crw-rw----    1 radio    system    253,   4 Jan  6 16:43 30000003:94103dec
559
crw-rw----    1 radio    system    253,  30 Jan  6 16:43 3000000a:71d1094b
560
crw-rw----    1 radio    system    253,  28 Jan  6 16:43 3000000e:2bf06595
561
crw-rw----    1 radio    system    253,  26 Jan  6 16:43 3000000f:46d257e5
562
crw-rw----    1 radio    system    253,  23 Jan  6 16:43 30000013:e94e8f0c
563
crw-rw----    1 radio    system    253,  22 Jan  6 16:43 30000014:7cfcd2c6
564
crw-rw----    1 radio    system    253,  21 Jan  6 16:43 30000016:c713bd79
565
crw-rw----    1 radio    system    253,  19 Jan  6 16:43 30000019:acb4a896
566
crw-rw----    1 radio    system    253,  18 Jan  6 16:43 3000001b:97d7b24a
567
crw-rw----    1 radio    system    253,  12 Jan  6 16:43 3000001d:51c92bd8
568
crw-rw----    1 radio    system    253,   8 Jan  6 16:43 30000021:f330a24e
569
crw-rw----    1 radio    system    253,  14 Jan  6 16:43 3000003c:03d4377c
570
crw-rw----    1 radio    system    253,  29 Jan  6 16:43 30000048:0da5b528
571
crw-rw----    1 radio    system    253,  17 Jan  6 16:43 30000059:00000000
572
crw-rw----    1 radio    system    253,  16 Jan  6 16:43 3000005a:00000000
573
crw-rw----    1 radio    system    253,  13 Jan  6 16:43 3000005b:90380d3d
574
crw-rw----    1 radio    system    253,   7 Jan  6 16:43 3000005f:95d1d9f5
575
crw-rw----    1 radio    system    253,   5 Jan  6 16:43 30000060:bcfb5d63
576
crw-rw----    1 radio    system    253,   2 Jan  6 16:43 30000061:fb837d0b
577
crw-rw----    1 radio    system    253,  31 Jan  6 16:43 30000066:1f4b343e
578
crw-rw----    1 radio    system    253,  27 Jan  6 16:43 3000006b:0aabc7a4
579
crw-rw----    1 radio    system    253,  25 Jan  6 16:43 3000006c:00000000
580
crw-rw----    1 radio    system    253,  20 Jan  6 16:43 30000075:f708938d
581
crw-rw----    1 radio    system    253,  15 Jan  6 16:43 30000079:00000000
582
crw-rw----    1 radio    system    253,   1 Jan  6 16:43 30000081:ccc5b439
583
crw-rw----    1 radio    system    253,  24 Jan  6 16:43 3000fe00:00000000
584
crw-rw----    1 radio    system    253,  10 Jan  6 16:43 3000fffe:00000000
585
crw-rw----    1 radio    system    253,   6 Jan  6 16:43 30100001:00000000
586
crw-rw----    1 radio    system    253,   3 Jan  6 16:43 30100002:00000000
587
}}}
588
Theses 2 lines should ring a bell:
589
{{{
590
crw-rw----    1 radio    system    253,  13 Jan  6 16:43 3000005b:90380d3d
591 1 Denis 'GNUtoo' Carikli
crw-rw----    1 radio    system    253,  12 Jan  6 16:43 3000001d:51c92bd8
592 45 Denis 'GNUtoo' Carikli
}}}
593
594
Next there is that line:
595
{{{
596
+	for(i=3;i;--i) if(!can_send) sleep(1);//Time out of 5 seconds on can_send
597 1 Denis 'GNUtoo' Carikli
}}}
598 45 Denis 'GNUtoo' Carikli
This is the time between 2 requests, if you put it too low it can reboot your phone(it will crashes and reboot)
599
600 47 Denis 'GNUtoo' Carikli
601
==== libloc_api ====
602 49 Denis 'GNUtoo' Carikli
For adding support for libloc_api you need to modify the BOARD_GPS_LIBRARIES variable
603 45 Denis 'GNUtoo' Carikli
604 50 Denis 'GNUtoo' Carikli
[https://github.com/CyanogenMod/android_hardware_qcom_gps That repository] should have newer devices support(like in AOSP) and older too(like rmcc's commits)
605
606
==== testing ====
607
{{{
608
cd hardware/libhardware_legacy/tests/gpstest/
609
mm
610 45 Denis 'GNUtoo' Carikli
}}}
611 43 Denis 'GNUtoo' Carikli
gives you a gpstest binary, copy it to the device and run it, it'll tell you if it has a fix
612 1 Denis 'GNUtoo' Carikli
==== Note on the GPS ====
613 45 Denis 'GNUtoo' Carikli
Note that messing with GPS can reboot(that is to say your phone crashes and reboots because of that) your phone on certain devices(like the htc dream or the nexus one).
614
615
The GPS is attached to the modem on the htc dream and the nexus one.
616
The only way to request a fix or to activate it is trough a rpc mecanism that is between the modem and the CPU that runs Android.
617
That RPC mecanism uses shared memory between the modem and the CPU that runs Android.
618
619
On the htcdream and the nexusone a serial line is emulated on top of the RPC mecanism: the serial lines can be accesed at /dev/smd0 for the modem(AT commands) and /dev/smd27 for the GPS NMEA.
620 46 Denis 'GNUtoo' Carikli
So compatibility with applications that understand NMEA is garanteed.
621 42 Denis 'GNUtoo' Carikli
622 51 Denis 'GNUtoo' Carikli
Note that the GPS parsing library doesn't require to use NMEA, it could also uses the RPC directly(to be verified)
623
624
=== Sensors ===
625
Devices with an hardware keyboard slide can rotate with the slide of the keyboard, so accelerometers are not strictly necessary. Examples of such device include the HTC dream.
626
Other devices lack that hardware keyboard, and so the only way to rotate is trough theses accelerometers. Examples of such device include the nexus one.
627
628 52 Denis 'GNUtoo' Carikli
The nexusone has akmd.free which is the free implementation of akmd, the sensor daemon(which handle rotation)
629 51 Denis 'GNUtoo' Carikli
630
==== akmd.free ====
631
akmd.free is located in:
632
{{{
633 1 Denis 'GNUtoo' Carikli
hardware/akmd_free
634 52 Denis 'GNUtoo' Carikli
}}}
635 51 Denis 'GNUtoo' Carikli
it has currently(at the time of writing) support for akm8973+bma150 based sensors.
636
akmd.free was made specifically for the htc hero by its authors.
637
The device supported include the nexus one(tested) and the HTC hero(not tested,not activated).
638
639 1 Denis 'GNUtoo' Carikli
In order to activate the support for it you must add that in your BoardConfig.mk
640 52 Denis 'GNUtoo' Carikli
{{{
641
BUILD_AKMD := true
642
}}}
643
644
If you need to add support for other akm sensors  you could modify hardware/akmd_free/jni/Android.mk, for instance the nexusone had an issue with rotation beeing done in the reverse sense, so I did that:
645
{{{
646
+#ifdef TARGET_DEVICE_NEXUSONE
647
+    abuf[index] = Vector(-bma150_data[0], -bma150_data[1], bma150_data[2]);
648
+#else
649
     abuf[index] = Vector(bma150_data[0], -bma150_data[1], bma150_data[2]);
650
+#endif
651
}}}
652
And that:
653
{{{
654
ifeq ($(TARGET_DEVICE),passion)
655 51 Denis 'GNUtoo' Carikli
  LOCAL_CFLAGS += -DTARGET_DEVICE_NEXUSONE
656 32 Michael Haas -
endif
657
}}}
658 63 Paul Kocialkowski
659
=== Slowness issues ===
660
661
If the device is too slow without non-free libs, there can still be some workarounds:
662
 * Adding debug.sf.hw=0 in the proprieties: in a makefile on the device files, add:
663
{{{ PRODUCT_PROPERTY_OVERRIDES += debug.sf.hw=0 }}}
664
 * Use a patched gralloc: the [https://www.codeaurora.org/gitweb/quic/la/ Code Aurora] had a fix for a nasty Nexus One graphics bug on the {{{ froyo_almond }}} branch.
665
 * Use TARGET_LIBAGL_USE_GRALLOC_COPYBITS with libagl: if your device uses gralloc+copybits, you can try a fix that improved the speed on Nexus One: in a makefile on the device files, add:
666
{{{  TARGET_LIBAGL_USE_GRALLOC_COPYBITS := true }}}
667
668
The commits with these fixes for Nexus One are:
669
 * https://gitorious.org/replicant/android_device_htc_passion/commit/86aeb1822a90b71e2cbb1af71200e759d98f4993
670
 * https://gitorious.org/replicant/android_hardware_msm7k/commit/d2d79391f10789ed9d2f5dd818aac3b23c48d69e
671
672 28 Denis 'GNUtoo' Carikli
== Re-using source code ==
673
The previous source code re-used some public source code that was licensed under the Apache 2.0 license.
674 22 Denis 'GNUtoo' Carikli
The ril will also re-use some public source code licensed under Apache 2.0.
675
That is the advised way to do it as it save some time and is easier to do, however proper credit must be attributed, at least in the commit message.
676 23 Denis 'GNUtoo' Carikli
It is even advised to look at the public apache 2.0 source code of other rils libraries or components of android.
677
678
=== Ril ===
679
 * vilvord ril
680
 * openmoko (android on freerunner) ril
681
682
== Source organization and commit access ==
683
Until now we made some changes in the tree, but we want the changes to land upstream in replicant.
684 24 Denis 'GNUtoo' Carikli
For instance let's say we modified only the ril path like in the ril section in 
685
{{{
686
device/htc/dream_sapphire/full_dream_sapphire.mk 
687
}}}
688
first we save our modifications:
689
{{{
690
cd device/htc/dream_sapphire/
691
git diff > git_diff.patch
692 1 Denis 'GNUtoo' Carikli
}}}
693
then we find where is the root of the git repository we are in:
694 24 Denis 'GNUtoo' Carikli
{{{
695
cd replicant-2.2 #top replicant directory where everything is in
696
cd .repo
697
cat manifest.xml
698
}}}
699
and we find that:
700
{{{
701
  <project path="device/htc/buzz" name="CyanogenMod/android_device_htc_buzz" remote="github" />
702
}}}
703
so...now our repository is in device/htc/buzz
704
We will now look where the source repository is:
705
{{{
706
cd device/htc/buzz
707
cd .git
708
cat config
709
}}}
710
We find that:
711
{{{
712
	url = git://github.com/CyanogenMod/android_device_htc_buzz.git
713 25 Denis 'GNUtoo' Carikli
}}}
714
715
Then create a directory, not under the replicant-2.2 directory that will contain your repositories:
716
{{{
717
mkdir repo
718
cd repo
719
}}}
720
and clone the source:
721
{{{
722 26 Denis 'GNUtoo' Carikli
git clone git://github.com/CyanogenMod/android_device_htc_buzz.git
723
cd android_device_htc_buzz
724 27 Denis 'GNUtoo' Carikli
}}}
725 26 Denis 'GNUtoo' Carikli
apply the previous patch:
726
{{{
727
git apply path/to/git_diff.patch
728
}}}
729
commit locally the result:
730
{{{
731 32 Michael Haas -
git commit -s
732
}}}
733 1 Denis 'GNUtoo' Carikli
Note that the commit message should have the following format:
734 27 Denis 'GNUtoo' Carikli
The first line should be a summary
735
Followed by a linebreak
736
And then the details explaining the commit
737
If you made an error writing the commit message do
738
{{{
739 1 Denis 'GNUtoo' Carikli
git commit --amend
740
}}}
741
742
TODO: complete for sending the git patch(git format-patch -1,git send-email)
743
744
==== Pushing to replicant ====
745
TODO: git remote add+git push