MOTODEV Studio for Android

[marcioandrey]

Hi.

I'd like to know why 

Every time I create an emulator occur the following:

1 - It is shown on Device Management.

2 - I'm able to use it without any problem at all.

3 - Some days later (it may take 1 day or 10 days to happen) Device Manager shows my emulator twice.

One of them is still working fine.

The other one has status "Not available" and I can't start it.

I get error message "The selected AVD is not repairable." every time I try to repair it.

4 - If I erase this device that has status "Not available" on Device Management, the device that worked stops working and when I restart MOTODEV it's gone.

You can see what I'm saying on pictures bellow.

This problem happens since MOTODEV 2.2.

My environments:

Linux Ubuntu 11.04 32 bits

MOTODEV 3.1.0

and

Windows 7 64 bits

MOTODEV 3.1.0

[juperdigueiro]

Hi marcioandrey,

This sounds like someone's misbehaving

Can you give us some information so we can try to find the root of the problem and plan how to fix this?

1. There is a file used by the Device Management View to keep a list of available devices - check if this file contains duplicate entries: <your home dir>/.org.eclipse.sequoyah/sequoyah_devices.xml
2. The Android SDK keeps files for each AVD, check what it is storing here (what kinds of files for each AVD available): <your home dir>/.android/avd

Thanks for your report!

[marcioandrey]

Hi, Julia.

Question 2: yes, all avd files are under <HOME_DIR>/.android/avd.

Question 1:

Every device that appears more than once in Device Manager has more than one <instance> in sequoyah_devices.xml.

For instance,  CLIQ_XT_api3 appears 3 times in device manager (as you can see in the screenshot in my previous post) and it has 3 <instance> entries.

My guess is that somehow when I change some emulator's configuration the program that handles sequoyah_devices.xml file is creating new <instance> entries instead of just update the existing one.

Bellow you can see the entries for CLIQ_XT_api3 emulator:

<instance deviceType_id="com.motorola.studio.android.emulator.androidDevice" name="CLIQ_XT_api3">
<Command_Line>-dpi-device 160 -scale 0.52 -no-boot-anim</Command_Line>
<Vm_Skin>CLIQ_XT</Vm_Skin>
<Vm_Path>C:\Users\plicatibu\.android\avd\CLIQ_XT_api3.avd</Vm_Path>
<Abi_Type>armeabi</Abi_Type>
<UseProxy>false</UseProxy>
<Timeout>120</Timeout>
<Skin_Plugin_Id>com.motorola.studio.android.emulator.skin.android.androidSkin</Skin_Plugin_Id>
<UseVnc>false</UseVnc>
<Emulator_Type>com.motorola.studio.android.emulator10.defaultEmulatorDefinitions</Emulator_Type>
<Vm_Target>CLIQ_XT</Vm_Target>
</instance>

<instance deviceType_id="com.motorola.studio.android.emulator.androidDevice" name="CLIQ_XT_api3">
<Command_Line/>
<SaveSnapshot>false</SaveSnapshot>
<Vm_Skin>CLIQ_XT</Vm_Skin>
<Vm_Path>C:\Users\plicatibu\.android\avd\CLIQ_XT_api3.avd</Vm_Path>
<Abi_Type>armeabi</Abi_Type>
<UseProxy>false</UseProxy>
<Timeout>120</Timeout>
<UseSnapshot>false</UseSnapshot>
<startFromSnapshot>false</startFromSnapshot>
<Skin_Plugin_Id>com.motorola.studio.android.emulator.skin.android.androidSkin</Skin_Plugin_Id>
<UseVnc>false</UseVnc>
<Vm_Target>CLIQ_XT</Vm_Target>
<Emulator_Type>com.motorola.studio.android.emulator10.defaultEmulatorDefinitions</Emulator_Type>
</instance>

<instance deviceType_id="com.motorola.studio.android.emulator.androidDevice" name="CLIQ_XT_api3">
<Command_Line/>
<SaveSnapshot>false</SaveSnapshot>
<Vm_Skin>CLIQ_XT</Vm_Skin>
<Vm_Path>C:\Users\plicatibu\.android\avd\CLIQ_XT_api3.avd</Vm_Path>
<Abi_Type>armeabi</Abi_Type>
<UseProxy>false</UseProxy>
<Timeout>120</Timeout>
<UseSnapshot>false</UseSnapshot>
<startFromSnapshot>false</startFromSnapshot>
<Skin_Plugin_Id>com.motorola.studio.android.emulator.skin.android.androidSkin</Skin_Plugin_Id>
<UseVnc>false</UseVnc>
<Emulator_Type>com.motorola.studio.android.emulator10.defaultEmulatorDefinitions</Emulator_Type>
<Vm_Target>CLIQ_XT</Vm_Target>
</instance>

Regards.

[juperdigueiro]

Hi marcioandrey,

Thanks a lot for the info! This is definitely a bug and we filed it for the Sequoyah project, which is responsible for Device Management View: https://bugs.eclipse.org/bugs/show_bug.cgi?id=371126

We'll keep in touch with the Sequoyah team to see this fixed