Android Emulator 2.1: Setting HTTP Proxy

by donivem » Wed, 17 Feb 2010 03:02:23 GMT

Sponsored Links
 Does anybody know the resolution to the problem of setting the HTTP
proxy for the emulator. The cmd line option does not work. It's an
essential to work behind a corporate firewall...

Any help is appreciated...



Other Threads

1. ORMLite 3.2 with native Android support for Sqlite released

We have released version 3.2 of the ORMLite package with a new backend which 
supports Android OS native database API calls to SQLite.

You can download the Android release files here:

Example projects using ORMLite are posted here:

ORMLite home page here with the feature set and online documentation:

Documentation about how to get started with Android is here:

Love to get some feedback from more Android developers.


ORMLite provides the following features:

* Setup your classes by simply adding Java annotations.
* Powerful abstract Database Access Object (DAO) classes.
* Flexible QueryBuilder to easily construct simple and complex queries.
* Supports native support for Android OS.  Also has backend for JDBC 
* Handles "compiled" SQL statements for repetitive query tasks.
* Supports "foreign" objects with the class field being the object but an id 
stored in the table.
* Basic support for database transactions.
* Auto generates SQL to create and drop database tables.
* Support for configuring of tables and fields without annotations.


2. Verizon Moto droid auto update to 2.2 yesterday


Yesterday my Verizon Motorola droid was automatically updated from
Android 2.1 to 2.2. I was informed that it had been done via text
message. I was not consulted or warned, only informed after the fact.
It does not cause any problem in my app. I used the getSDcardPath
(syntax approx) rather than hard-coding /sdcard/data..... and I have
not found any other conflicts.

How are Android updates handled on devices? Always done automatically,
this instance of auto update was unusual, or what?

If it is always done automatically then we MUST incorporate all
accommodations for future changes that are not backwards compatible
just to keep our apps running on machines that they were designed to
run on. (it is difficult to anticipate all future changes!)

Previous to this automatic update, I was thinking that we should
incorporate all accommodations for future changes that are not
backwards compatible so the app would run on future Android versions.
(this option does not require knowledge of the future.)

Thanks, John Brown

PS. I did opt to do the Adobe update yesterday. But that just seemed
like a normal application update. No indication that it affected
anything else.


3. getting and stopping a single running service

4. How to add option to "share via" menu

5. Fil-rate workaround with FBOs?

6. communication to oracle

7. Interface Plugin?