Android Build Quirks

[Lawrence D'Oliveiro]

Every time I add a new resource to an Android project (layout, string etc),
it seems to misbehave and invoke the wrong resources. After I do an ant
clean and rebuild and reinstall, it works fine.

I think what’s happening is that compiled classes are being included that
were built against the old version of R.java. What should happen if
resources change, is that R.java should be the the first thing regenerated,
before any Java source files are compiled. That will then trigger the
recompiling of all the necessary sources.

 

[Dirk Bruere at NeoPax]

Every time I add a new resource to an Android project (layout, string etc),
it seems to misbehave and invoke the wrong resources. After I do an ant
clean and rebuild and reinstall, it works fine.

I think what’s happening is that compiled classes are being included that
were built against the old version of R.java. What should happen if
resources change, is that R.java should be the the first thing regenerated,
before any Java source files are compiled. That will then trigger the
recompiling of all the necessary sources.

There are oddities.
And the emulator is not to be trusted 100%, esp not with networking
stuff. I have spent days trying to find a bug that wasn't there when the
s/w was debugged on a real machine

 

[Lawrence D'Oliveiro]

And the emulator is not to be trusted 100%, esp not with networking
stuff.

Hmmm ... the emulator is the only way I can test networking stuff at the
moment.

Must try and see if I can get my old Asus Eee 701 to act as an access
point...

 

[Dirk Bruere at NeoPax]

Hmmm ... the emulator is the only way I can test networking stuff at the
moment.

Must try and see if I can get my old Asus Eee 701 to act as an access
point...

I had big problems with LAN access via the emulator.
I wanted to do the Netbios getbyname() thing, which is not supported by
Android.
Tried JCIFS and that did not work.
However, it *did* work when it was used on the real Android Tablet