Time for Eclair

Eclair was integrated to AOSP several days ago by Jean-Baptiste Queru and company. Well, most of it, as some parts of Android 2.0 codebase are not open-sourced. Today’s snapshot is quick and dirty build of Eclair, which as you all know, includes some tasty things. I hope, HTC will provide Android 2.0 for Hero in next few weeks, cause I’m really starving without VPN support in 1.5.

You may note, that there are no API levels at platform selection in android tool anymore, only AOSP related platform. It seems correct, although I’ve not performed robust testing of API changes yet.

Related changes were not uploaded for review yet, I’ll do it a bit later, most of them are my old patches actually, which were used on Donut branch, however there are several not significant new patches.

Tags: ,

19 Responses to “Time for Eclair”

  1. Pois says:

    Hi,
    I have an hero and a fresh install of freebsd8.0,
    I have downloaded :
    # v.20091117-Eclair, 115Mb download (external link) snapshot notes (external link)
    # v.20091110, 97Mb download (external link) snapshot notes (external link)
    # and the adb tools via the link on your blog

    But which everyone I got this :
    # ./adb start-server
    * daemon not running. starting it now *
    * daemon started successfully *
    ADB server didn’t ACK
    * failed to start daemon *

    Does I need something more than this files ?

  2. taleks says:

    Hi,
    it’s deep night at my local time zone, I’ll try to check for possible problem tomorrow.

    As for your question, in 20091117 and 20091110 builds you don’t need no to download any additional adb (it was for earlier builds only)

    What will be if you kill any adb instances (pkill adb) and just execute: ./adb devices
    ?

    Usually, “didn’t ACK” error occurs when forked adb server not answers or answers not expected reply.
    Last one may be if stderr contains debug info or any other not related for communications text (communications between server and client are via stderr).
    Do you have adb debugging related variable set in environment?

  3. Pois says:

    “As for your question, in 20091117 and 20091110 builds you don’t need no to download any additional adb (it was for earlier builds only)”
    Yes I know but it was just to be sure and test multiple version.

    No debug variable in my environment,
    $ set | grep -i adb
    $

    It’s a little bit long :
    http://pastebin.com/m7bdc988e

  4. taleks says:

    Hm, I’ve checked on 8.0-PRERELEASE (I’ve not installed RELEASE yet). All was ok. However I was able to simulate similar error
    ———————–
    %setenv ADB_TRACE transport
    %./adb start-server
    * daemon not running. starting it now *
    ADB server didn’t ACK
    * failed to start daemon *
    %setenv ADB_TRACE 0
    %pkill adb
    %./adb start-server
    * daemon not running. starting it now *
    * daemon started successfully *
    %./adb devices
    List of devices attached
    HT98NL901502 device

    ————-
    So, check for ADB_TRACE. in csh: setenv | grep ADB_TRACE

    Also, check for /dev/usb permissions. Although it must not affect adb start, but it’ll prevent from device searching. In my case, I’ve such devfs rules:
    —————
    %id
    uid=1001(taleks) gid=1001(taleks) groups=1001(taleks),0(wheel),5(operator),920(vboxusers)
    %cat /etc/devfs.rules
    [usbrules=10]
    add path ‘ugen*’ mode 0660 group operator
    add path ‘da*s*’ mode 0660 group operator
    add path ‘usb/*’ mode 0660 group operator
    —————
    and:
    —————
    %ls -l /dev/usb
    crw-rw—- 1 root operator 0, 69 Nov 27 14:24 0.1.0
    …skipped…
    %ls -l /dev | grep ugen
    lrw-rw—- 1 root operator 9 Nov 27 14:24 ugen0.1 -> usb/0.1.0
    …skipped…
    —————-

    If nothing of this helps, I’ll compile debug version of adb and we’ll try to catch problem from adb debug logs.

    PS:
    I’ve similar dmesg output, it’s normal.

  5. Pois says:

    %setenv | grep ADB_TRACE
    %ps auxwww | grep adb
    xxx 1652 0.0 0.0 3448 992 1 S+ 2:45PM 0:00.00 grep adb
    %./adb start-server
    * daemon not running. starting it now *
    * daemon started successfully *
    ADB server didn’t ACK
    * failed to start daemon *

    For the usb permissions, I am actually trying to do this in root, I will see for make it cleany when it will work :)

  6. Pois says:

    # truss ./adb start-server
    [...]
    readlink(“/proc/1790/file”,0xbfbfbf94,1023) ERR#2 ‘No such file or directory’
    [...]
    ADB server didn’t ACK
    [...]
    # echo “proc /proc procfs rw 0 0″ >> /etc/fstab; mount /proc
    # ./adb start-server
    * daemon not running. starting it now *
    * daemon started successfully *

    Maybe you should write that on a readme.
    Thank you for your work, now let’s go play with that :D

  7. taleks says:

    Damn, I completely forgot about this possibility.
    Thanks, I really need to write it in FAQ.

    Some of Android tools depend on procfs, e.g. it used to get executable filepath via resolving symbolic link /proc/pid/file

  8. [...] que BSDroid – le projet de portage du framework de développements de Android sous FreeBSD – propose une version fonctionnelle sous FreeBSD 8. « Floss Weekly 104 avec Randi Harper aka FreeBSD [...]

  9. Gustik says:

    I have downloaded and have install 20091117-Eclair
    > cd /home/Gustik/android/sdk/tools/
    > ./adb start-server
    * daemon not running. starting it now *
    * daemon started successfully *

    > ./adb devices
    List of devices attached
    HT98ML903744 device
    It’s work fine.
    Then I have installed Eclipse and ADT and
    Eclipse can not create R.java automatically and show that’s error messages:

    [2010-01-23 16:48:26 - hello]W/ResourceType(11110): Unable to get buffer of resource asset file
    [2010-01-23 16:48:26 - hello]/usr/home/Gustik/workspace/hello/res/layout/main.xml:2: error: No resource identifier found for attribute ‘orientation’ in package ‘android’
    [2010-01-23 16:48:26 - hello]/usr/home/Gustik/workspace/hello/res/layout/main.xml:2: error: No resource identifier found for attribute ‘layout_width’ in package ‘android’
    [2010-01-23 16:48:26 - hello]/usr/home/Gustik/workspace/hello/res/layout/main.xml:2: error: No resource identifier found for attribute ‘layout_height’ in package ‘android’
    [2010-01-23 16:48:26 - hello]/usr/home/Gustik/workspace/hello/res/layout/main.xml:7: error: No resource identifier found for attribute ‘layout_width’ in package ‘android’
    [2010-01-23 16:48:26 - hello]/usr/home/Gustik/workspace/hello/res/layout/main.xml:7: error: No resource identifier found for attribute ‘layout_height’ in package ‘android’
    [2010-01-23 16:48:26 - hello]/usr/home/Gustik/workspace/hello/res/layout/main.xml:7: error: No resource identifier found for attribute ‘text’ in package ‘android’
    [2010-01-23 16:48:26 - hello]/usr/home/Gustik/workspace/hello/AndroidManifest.xml:2: error: No resource identifier found for attribute ‘versionCode’ in package ‘android’
    [2010-01-23 16:48:26 - hello]/usr/home/Gustik/workspace/hello/AndroidManifest.xml:2: error: No resource identifier found for attribute ‘versionName’ in package ‘android’
    [2010-01-23 16:48:26 - hello]/usr/home/Gustik/workspace/hello/AndroidManifest.xml:6: error: No resource identifier found for attribute ‘icon’ in package ‘android’
    [2010-01-23 16:48:26 - hello]/usr/home/Gustik/workspace/hello/AndroidManifest.xml:6: error: No resource identifier found for attribute ‘label’ in package ‘android’
    [2010-01-23 16:48:26 - hello]/usr/home/Gustik/workspace/hello/AndroidManifest.xml:7: error: No resource identifier found for attribute ‘name’ in package ‘android’
    [2010-01-23 16:48:26 - hello]/usr/home/Gustik/workspace/hello/AndroidManifest.xml:7: error: No resource identifier found for attribute ‘label’ in package ‘android’
    [2010-01-23 16:48:26 - hello]/usr/home/Gustik/workspace/hello/AndroidManifest.xml:10: error: No resource identifier found for attribute ‘name’ in package ‘android’
    [2010-01-23 16:48:26 - hello]/usr/home/Gustik/workspace/hello/AndroidManifest.xml:11: error: No resource identifier found for attribute ‘name’ in package ‘android’
    [2010-01-23 16:48:26 - hello]/usr/home/Gustik/workspace/hello/AndroidManifest.xml:16: error: No resource identifier found for attribute ‘minSdkVersion’ in package ‘android’

    What will advise to make?

    ps: sorry for my bad inglish

  10. Gustik says:

    ps: sorry for my bad English =)

  11. taleks says:

    Sorry for delay, I’ve caught cold again.
    What API you’ve used for project (you may select several, when creating project)?

    PS:
    можно и по-русски, в принципе, пообщаться

  12. Gustik says:

    API выбирал AOSP, да и выбора кроме него не было =)
    ps:
    - java version “1.6.0_07″
    Diablo Java(TM) SE Runtime Environment (build 1.6.0_07-b02)
    Diablo Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)
    - ADT v0.9.5.v200911191123-20404
    - DDMS v0.9.5.v200911191123-20404
    - Eclipse v3.4.2
    - FreeBSD 8.0-RELEASE-p2

  13. XclusR says:

    Guestlk,

    А где ты скачал этот SDK?

    это не официальная версия, а построенная кем-то из исходников.

    официальную можно скачать здесь: developer.android.com

    Если есть возможность перестроить sdk, то говорят, что помогает:

    “You can exchange the .arsc file inside android.jar with an older version or patch the aapt tool by editing frameworks/base/include/utils/Asset.h.

    Change both lines UNCOMPRESS_DATA_MAX = 1 * 1024 * 1024 to something bigger. As the new resources file currently has a size of 2.3Mb you should change the lines (both lines mind you) to at least 3*1024*1024. ”

    Источник:
    http://en.androidwiki.com/wiki/Using_the_Android_SDK_tools

  14. taleks says:

    Gustik:
    пардон за длительное молчание. Командировка была в места не столь близкие.

    Что касается первой ошибки, XclusR говорит верно, я собираюсь пересобрать aapt с большим буфером. Что касается остальных – пока не разбирался, возможно они не связаны, есть такая вероятность.

    XlusR:
    он скачал сборку bsdroid. Которая неофициальна и предоставлят родные утилиты, работающие под FreeBSD без режимов совместимости,, в частности adb и эмулятор. Официальный SDK сейчас не качается с той ссылки, там качается инсталлятор SDK. Но влюбом случае, нет нативной сборки под FreeBSD и часть утилит, которые вызываются через скрипты банально содержит неверные пути к бинарникам (в общем-то, в основном к bash).

    Что касается bsdroid, скоро он будет работать абсолютно также – маленький инсталятор и версии фрэймвёрков с сайта качается отдельно, возможно с официального (поскольку сама платформа без утилит одинакова для всех версий).

    Как временное решение – можно использовать SDK от Linux в режиме совместимости, поменяв у скриптов she-bang пути и оставив из всего только adb, поскольку ИМХО линуксовая версия некорректно работает под FreeBSD.

    Следующая сборка должна быть до конца февраля, елси ничего плохого не случится.

  15. XclusR says:

    taleks,

    Все остальные ошибки – следствие первой.

  16. taleks says:

    XclusR:
    тем лучше.

  17. François says:

    Hi,

    I saw that Gustik (above) is using the ADT plugin for eclipse. Is this working? Can we use ADT with BSDROID?

    Thanks.

  18. taleks says:

    François:
    I’m not using Eclipse now, thus I can’t say for sure, however when I’ve tried to use ADT about one year ago, there were problems.

    Probably Gustik may answer your question and share more recent information on this subject.

  19. mike says:

    just want to pass this on to anyone scouring the web for stuff about using the android sdk under bsd – everyone does seem to end up here eventually ;)

    First, I’ve got eclipse running in linux compat mode and installed the linux plugin with no problems. I then copied over the ASOP platform and so far, it seems like its recognized. Just starting though.

    On another note, I was very frustrated that the latest linux sdk would not let me download any platforms (the original reason I came here). All archives were red X’d out. I’ve solved this by adding -Dos.name=”Linux” into the exec javacmd found in the android script in the tools folder. (also modified the scripts to use /compat/linux/bin/bash)

    I hope this is of use to others and hope one day we have a complete native BSD environment. Thanks for the hard work so far on this project.

Leave a Reply