CloudServices/NativeSync: Difference between revisions

Jump to navigation Jump to search
(→‎Native Sync: Added Troubleshooting section.)
Line 7: Line 7:
=== Emulators ===
=== Emulators ===


* create emulator with $SDK/tools/android, menubar>Tools>Manage AVDs...
* to create:
* Target (probably) needs to match build specified in .mozconfig (see Building Fennec Native below)
 
Use the command line <tt>$SDK/tools/android</tt>, or use the graphical Android AVD Manager (from within Eclipse: <tt>Window > AVD Manager</tt>).
 
$ android create avd -t android-10 -n NAME -c 2047M
Auto-selecting single ABI armeabi
Android 2.3.3 is a basic Android platform.
Do you wish to create a custom hardware profile [no]
Created AVD 'NAME' based on Android 2.3.3, ARM (armeabi) processor,
with the following hardware config:
hw.lcd.density=240
vm.heapSize=24
hw.ramSize=256
 
{{note|Target (in the example above, 'android-10') probably needs to match build specified in .mozconfig (see Building Fennec Native below).}}
 
* to launch:
* to launch:
$SDK/tools/emulator -wipe-data -avd <AVD> -partition-size 2047


(so you don't run into insufficient storage error)
$ $SDK/tools/emulator -wipe-data -avd NAME -partition-size 2047
 
{{note|The partition size is set large so that you don't run into an insufficient storage error.}}
 
* to delete:
 
$ android delete avd -n NAME


After installation, fennec would crash on installation (unable to locate mozutils library, although it's in the apk). Possibly related to emulator failing to run NDK applications?
After installation, fennec would crash on installation (unable to locate mozutils library, although it's in the apk). Possibly related to emulator failing to run NDK applications?
Confirmed users
355

edits

Navigation menu