Changes between Version 1 and Version 2 of Documentation/hAndroid/OMF
- Timestamp:
- Oct 18, 2013, 10:22:07 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Documentation/hAndroid/OMF
v1 v2 1 = OMF on Android=1 == OMF on Android == 2 2 3 == 0. Setup device == 3 1. Setup device 4 4 5 5 In order to run OMF Resource Controller on an Android device, we need a Ruby interpreter. … … 19 19 To install the JRuby interpreter, press Menu and then View > Interpreters. From here you can see all installed interpreters. To add a new one, press Menu and then Add > JRuby. The .apk should automatically download. Install and open it. Press install, and it will download the necessary libraries to start the JRuby interpreter from SL4A. 20 20 21 == 1. Get OMF source code == 21 2. Get OMF source code 22 22 23 23 Now we need the OMF source code to run. … … 30 30 Copy the root directory that holds omf-common and omf-resctl to sl4a/scripts on the device's SD card. You should now be able to view the OMF files in SL4A. 31 31 32 == 2. Bootstrap OMF == 32 3. Bootstrap OMF 33 33 34 34 If you just try to start the resource controller by running omf-resctl/ruby/omf-resctl/nodeAgent.rb, you will run into errors regarding the load path. This is because the resource controller is supposed to be started via omf-resctl/sbin/omf-resctl: … … 75 75 This script is in essence a Ruby translation of the shell script above that loads all Ruby dependencies (RESCTL_DIR and COMMON_DIR) to the LOAD_PATH variable before running nodeAgent.rb (NODE_PATH). 76 76 77 == 3. Load networking drivers == 77 4. Load networking drivers 78 78 79 79 In order to properly retreve data from the device, you need to use the corresponding driver for the wireless chipsets. nodeAgent does this by running lspci, which does not work on Android. … … 89 89 The Intel driver is not completely compatible with the wireless chipsets on the device, but it works. 90 90 91 == 4. Vendorize Gems == 91 5. Vendorize Gems 92 92 OMF relies on several gems that we do not have on the SD card. 93 93 … … 136 136 This is necessary because the native Yaml parser returns a hash with symbols for keys, and RbYAML returns a hash with strings as keys. We recursively copy the data into a new hash and convert the key from a string to symbol. 137 137 138 == 5. Configure node == 138 6. Configure node 139 139 Resource Controller should be running now, you need to configure it accordingly.