@@ -26,6 +26,66 @@ This project gives the opportunity to use your phone even with a broken screen.
2626
2727[ wiki ] : https://github.com/xSAVIKx/AndroidScreencast/wiki
2828
29+ ## Configuration
30+
31+ There are 2 ways to run application:
32+ 1 . Run ADB server on your own
33+ 2 . Provide correct ` app.properties ` file
34+
35+ ### Run ADB server on your own
36+
37+ In order to run server on your own you have to run already installed (or one from our OS-specific bundle) ` adb `
38+ with following command:
39+ ```
40+ adb start-server
41+ ```
42+
43+ ** Note** :
44+
45+ If ` app.properties ` will have ` adb.path ` filled - AndroidScreencast will shutdown ADB server on application termination.
46+
47+ Additionally, in order to use, for example, remote ADB server with ssh forwarding you should not use ` app.properties ` or ` adb.path `
48+ property should be commented.
49+
50+ ### Provide correct ` app.properties ` file
51+
52+ Right now to successfully run application you ** should** create ` app.properties ` file in the same folder as
53+ AndroidScreencast's jar and provide at least one property - ` adb.path ` which should point to the ` adb ` executable file
54+ within your OS, for example such location could be configured for Windows OS:
55+ ``` properties
56+ adb.path =adb/windows/adb.exe
57+ ```
58+
59+ Both absolute and relative paths are supported.
60+
61+ Example of valid ` app.properties ` could be find [ here] ( app.properties ) .
62+
63+ Also we have got some valid OS-specific examples:
64+ * [ OSX app.properties] ( adb/macosx/app.properties )
65+ * [ Windows app.properties] ( adb/windows/app.properties )
66+ * [ Linux app.properties] ( adb/linux/app.properties )
67+
68+ They are actually the same, just ` adb.path ` is OS-specific. Files listed above are automatically included into OS-specific bundles.
69+
70+
71+ ### Additional properties
72+ Here is the full list of available properties for application configuration.
73+ Properties should be places in the ` app.properties ` file in the same folder as AndroidScreencast's jar file.
74+
75+ ``` properties
76+ # relative or absolute path to ADB
77+ adb.path =./adb
78+ # maximum time to wait for device (in seconds)
79+ adb.device.timeout =30
80+ # maximum time to execute adb command (in seconds)
81+ adb.command.timeout =5
82+ # initial application window width (in pixels)
83+ app.window.width =1024
84+ # initial application window height (in pixels)
85+ app.window.height =768
86+ # Defines whether application should look 'natively' to OS. Possible values: true/false
87+ app.native.look =false
88+ ```
2989## JNLP
3090
3191Application is available using Java web start technology via [ androidscreencast.jnlp] [ jnlp ] .
@@ -59,6 +119,10 @@ Additionally OS-packages would be created with ADB executables bundled:
59119* ` androidscreencast-VERSION-linux.tar.gz `
60120* ` androidscreencast-VERSION-macosx.tar.gz `
61121
122+ In order to provide correct configuration see [ configuration] [ configuration_section ] section.
123+
124+ [ configuration_section ] : https://github.com/xSAVIKx/AndroidScreencast/blob/develop/README.md#configuration
125+
62126# Requirements
63127
64128Currently AndroidScreencast works directly with ` adb input ` program through ` ddmlib ` and abuse functionality of:
@@ -81,6 +145,7 @@ Also, to run AndroidScreencast you will need *adb* installed (or you can use bun
81145[ Android_4_1_1_Input ] : http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/4.1.1_r1/com/android/commands/input/Input.java#Input
82146[ seven_square ] : https://github.com/yangh/sevensquare
83147[ droid_at_screen ] : http://droid-at-screen.org/droid-at-screen/
148+ [ android_screen_monitor ] : https://github.com/adakoda/android-screen-monitor
84149
85150[ travis_badge ] : https://travis-ci.org/xSAVIKx/AndroidScreencast.svg?branch=master
86151[ travis ] : https://travis-ci.org/xSAVIKx/AndroidScreencast
0 commit comments