8 Answers

• Ok,

  So I have now investigated the ini files which all seem to be just fine. During my android development the only thing I can say is that there are two targets created in an older version (still useable) avd manager and two new ones for titanium with a new avd manager, the four targets reside in the same android path and shows up just fine for each of the two managers and systems. The older one with 1.5 target in Eclipse and the new titanium one with target 1.6. My system with titanium runs as standard, so if I run android.exe from cmd then the new avd manager is run. The new avd is not recognising the old targets, but the new ones are there and fully ok. So, it still remains to understand why the adb is not recognising my newly created targets, which obviuosly are run from titanium test/debug folder.

  It might seem as a solution to remove the old targets, however that will destroy my earlier development that I am still using at present.

  So I tried to move them out of the way. but avd still finds them . .

  I do not want to delete them from avd manager . . . :(
  I should be able to run both systems you might think . .

  /Jörgen

  Anyone?

  /Jörgen

• Wow, what a great response. :(

  I still have the same problem. I removed all the old targets and recreated these new ones, no luck, now at least I have no ini file problem, but I get a python error stack. If I stop the adb I get the ini file corrupt again. :(:(

  Anybody know why?

  [INFO] Creating new Android Virtual Device (1 HVGA)
  [TRACE] Traceback (most recent call last):
  [TRACE] File "C:\Documents and Settings\All Users\Application Data\Titanium\mobilesdk\win32\1.4.0\android\builder.py", line 991, in <module>
  [TRACE] s.run_emulator(avd_id,avd_skin)
  [TRACE] File "C:\Documents and Settings\All Users\Application Data\Titanium\mobilesdk\win32\1.4.0\android\builder.py", line 253, in run_emulator
  [TRACE] avd_name = self.create_avd(avd_id,avd_skin)
  [TRACE] File "C:\Documents and Settings\All Users\Application Data\Titanium\mobilesdk\win32\1.4.0\android\builder.py", line 227, in create_avd
  [TRACE] initfiledata.write("{0[0]}={0[1]}".format(hw_options))
  [TRACE] NameError: global name 'initfiledata' is not defined
  [INFO] Building helloworld for Android … one moment
  [DEBUG] C:\android-sdk\tools\adb.exe start-server
  [DEBUG] Waiting for device to be ready …
  [TRACE] adb devices returned 0 devices/emulators
  [TRACE] adb devices returned 0 devices/emulators
  [TRACE] adb devices returned 0 devices/emulators
  [TRACE] adb devices returned 0 devices/emulators
  [TRACE] adb devices returned 0 devices/emulators

• Testing to write since I have had forum crashes now for a while

• Have you looked at the Troubleshooting section of the Getting Started Guides? There are cases where the avd's may need to be deleted, so that Titanium can recreate them. There may be some other hints there that could help as well.

  Let's see if anyone else has some other ideas.

• Have you looked at the Troubleshooting section of the Getting Started Guides? There are cases where the avd's may need to be deleted, so that Titanium can recreate them. There may be some other hints there that could help as well.

  Let's see if anyone else has some other ideas.

• answering this myself, my user name consist of åäö, this was not supported, so changing this in the ini files fixed that problem.

  /J

• Have you looked at the Troubleshooting section of the Getting Started Guides? There are cases where the avd's may need to be deleted, so that Titanium can recreate them. There may be some other hints there that could help as well.

  Let's see if anyone else has some other ideas.

• [RESOLVED] So in conclusion

  Do not use user accounts in Windows that uses none english letters, in my case swedish åöä. The reason is that scripts in Titanium and ini files are created with the letters åöä exchanged for stranger looking pairs of signs, which when using titanium stops things like starting the android emulater properly, it stops the avd manager to create proper targets and it stops starting the application in the emulator because of a sqlite connection. Ofcourse I am not sure exactly what the problem is, but by using a standard name like "Mobile" everything just worked, so if you have these problems, try this one too before you give up!! ;)
  (And yes, I tried recreating everything in my first user namespace but with same problems)

  Was this helpfull for you? Please let me know. ;)

  Regards

  Jörgen Buder
  Purple Scout AB
  Sweden