arduino - Android ADK development in practice - what are best practices? -


i'm trying clear picture of what's involved practically when doing android/adk development. there scattered android/adk related questions on few relevant answers.

i have questions related development , idea of answer - great if can confirm thoughs or provide additional information.

  1. can android/adk development done within avd?

    answer: no, because pc cannot function usb slave. adk usb host in accessory mode, (without extreme levels of hacking) adk cannot connected development pc running avd

  2. will ddms / debugger work on device that's hooked adk?

    answer: no, since device can connected either development pc or adk, not both. can connect adk using micro usb port pc , arduino-level serial debugging, that's quite different debugging java code android device running

  3. what workflow used when developping android / adk?

    answer:

    1. write arduino code in sketch, upload adk development board.
    2. connect physical android device yo development pc
    3. write code in eclipse, compile apk, install physical device.
    4. unplug phyisical android device, hook adk board, test if things work. either use app debugging (e.g. write log statements screen) or use arduino serial connection logging arduino software.
    5. if there issues, fix them (either in arduino or java), go 1. or 2.

am correct in above answers? sounds complex/slow develop/test code way. simulated adk avd big improvement.

you right answering own questions 1. , 3.

however when comes question 2., there way debug adk project usual while device attached accessory. can use adb connect functionality connect device via wifi debugging , ddms purposes.

have here details on how that:

adb, wifi , eclipse: how can configure?


Comments

Popular posts from this blog

delphi - How to convert bitmaps to video? -

jasper reports - Fixed header in Excel using JasperReports -

python - ('The SQL contains 0 parameter markers, but 50 parameters were supplied', 'HY000') or TypeError: 'tuple' object is not callable -