android - Tons of errors when starting a virtual device -


i'm starting android (having programmed java in text editor) , appreciate input. downloaded adt bundle suggested, packages sdk manager. next set nexus 4 virtual device, default ram value of 1907mb. after reducing ram 768mb suggested, still dozens of errors in logcat when launching virtual device. however, using different device not errors?

so here questions:

  1. did wrong? nexus series particularly bad program (the nexus10 virtual device shows black screen...not errors, though nexus7 seem work)?
  2. i have 16gb ram, i7-2500k@4ghz, samsung 830 ssd, clean win7 x64, yet emulator quite slow. normal (would totally understandable) or virtual device smooth else me?
  3. is adt bundle way go or should have downloaded eclipse , sdk separately?

thank in advance help!

edit: posting first , last few of errors (the log file errors ~45kb, 362 errors in total)

08-01 05:42:42.007: e/batteryservice(292): usbonlinepath not found 08-01 05:42:42.007: e/batteryservice(292): wirelessonlinepath not found 08-01 05:42:42.007: e/batteryservice(292): batteryvoltagepath not found 08-01 05:42:42.007: e/batteryservice(292): batterytemperaturepath not found 08-01 05:42:42.109: e/powermanagerservice-jni(292): couldn't load power module (no such file or directory) 08-01 05:42:42.317: e/surfaceflinger(37): ro.sf.lcd_density must defined build property 08-01 05:43:21.147: e/sqlitelog(292): (1) no such table: secure 08-01 05:43:21.597: e/soundpool(292): error loading /system/media/audio/ui/lock.ogg 08-01 05:43:21.597: e/soundpool(292): error loading /system/media/audio/ui/unlock.ogg 08-01 05:43:21.857: e/eventhub(292): not driver version /dev/input/mouse0, not typewriter ... 08-01 05:46:23.181: e/strictmode(713):  @ com.android.emailcommon.service.serviceproxy.settask(serviceproxy.java:157) 08-01 05:46:23.181: e/strictmode(713):  @ com.android.emailcommon.service.serviceproxy.settask(serviceproxy.java:145) 08-01 05:46:23.181: e/strictmode(713):  @ com.android.emailcommon.service.serviceproxy.test(serviceproxy.java:191) 08-01 05:46:23.181: e/strictmode(713):  @ com.android.exchange.exchangeservice$7.run(exchangeservice.java:1850) 08-01 05:46:23.181: e/strictmode(713):  @ com.android.emailcommon.utility.utility$2.doinbackground(utility.java:551) 08-01 05:46:23.181: e/strictmode(713):  @ com.android.emailcommon.utility.utility$2.doinbackground(utility.java:549) 08-01 05:46:23.181: e/strictmode(713):  @ android.os.asynctask$2.call(asynctask.java:287) 08-01 05:46:23.181: e/strictmode(713):  @ java.util.concurrent.futuretask.run(futuretask.java:234) 08-01 05:46:23.181: e/strictmode(713):  @ java.util.concurrent.threadpoolexecutor.runworker(threadpoolexecutor.java:1080) 08-01 05:46:23.181: e/strictmode(713):  @ java.util.concurrent.threadpoolexecutor$worker.run(threadpoolexecutor.java:573) 08-01 05:46:23.181: e/strictmode(713):  @ java.lang.thread.run(thread.java:856) 

  1. i never had problems virtual emulator, if n4 doesn't work pick one, or use android device through usb.

  2. it's slow no matter do, if use large image resources becomes slower because has pack inside .apk, send device , install it.

  3. adt bundle way go.


Comments

Popular posts from this blog

c++ - Creating new partition disk winapi -

Android Prevent Bluetooth Pairing Dialog -

VBA function to include CDATA -