by Rc3375 » Sat, 23 Jan 2010 23:09:16 GMT

Sponsored Links
 Does ANYONE(besides myself) had any problems installing WIN7, AND
getting this error msg WHEN eclipse fires up: "UNABLE TO PARSE ADB
I have download a fresh copy of eclipse thinking that the first copy
might of been corrupt.  NOT the problem.  Checked AND rechecked the
paths, SAME ERROR.  I have done EVERYTHING that I can think of.  I
have even tried changing the properties on the ECLIPSE short cut, for
ECLIPSE to run under WIN XP mode(service pack 2/3), that doesn't work
Is anyone using WIN7 and developing with ECLIPSE 3.4.X??  Perhaps you
would be kind enough to explain what you did to get Eclipse to work
(with out this error).  I'm starting to think that ECLIPSE has
problems that the software engineers have either over-looked, or


ADB Error

by Joaquin Vacas » Wed, 17 Feb 2010 05:12:37 GMT

 Maybe a Windows (Normal) error!
Try to run eclipse as Administrator
This worked for my friend!


Sponsored Links

Other Threads

1. service dead cause ap gotten killed by system?

Hi all,

I have a quick experiment about service and app.
Ap who bound the service will be killed by system if the service dies.

Here is my experiment steps:
1. start camera and taking a picture
2. kill the within adb shell.
3. the camera will killed by system with following logcat.

I/ActivityManager(   60): Process (pid 1968) has died.
I/ActivityThread( 1942): Removing dead content provider: media
I/ActivityThread( 1962): Removing dead content provider: media
I/ActivityManager(   60): Killing app (pid 1942) because
provider is in dying process
I/Process (   60): Sending signal. PID: 1942 SIG: 9
I/ActivityManager(   60): Killing app (pid 1962) because
provider is in dying process
I/Process (   60): Sending signal. PID: 1962 SIG: 9
D/Zygote  (   33): Process 1968 terminated by signal (15)

Following is my questions.
1. is camera killed by ibinder?
2. is there any way to handle the service died in java ap? because in low
memory condition, the service is easy to be killed. Since service will
restart later, maybe AP can just wait for these services restart instead of
killing by system. It seems easy to handle it in native with ibinder's
deadnotifier, but the whole story seems different in java layer.



2. Problem with global variables

So I am creating a simple RSS reader. I managed to implement
ListActivity and to fill it with desired data(rss titles). However,
now I wanted to implement onItemSelectedListener() method in order to
show the description of rss on the next Activity. Here is the code:

package stefan.rssreader;

import java.util.ArrayList;

import android.os.Bundle;
import android.widget.ArrayAdapter;

public class B92Rss extends ListActivity {
    /** Called when the activity is first created. */
    public void onCreate(Bundle savedInstanceState) {
        RssStorage storage = new RssStorage();
        RssFeed currentFeed;
        ArrayList<String> titles = new ArrayList<String>();
        ArrayList<String> descriptions = new ArrayList<String>();
        }catch(Exception e){}
        for(int i=0;i<storage.getSize();i++){
                currentFeed = storage.getNextFeed();
        setListAdapter(new ArrayAdapter<String>(this,
                android.R.layout.simple_list_item_1, titles));

So in order to implement this, I need to somehow declare titles and
descriptions variables outside onCreate() method. I tried but then the
list is empty and it doesn't work!
How exactly do I do this? Please help. I searched the web but couldn't
find explanation for this.

3. Install .odex + .apk

4. java.lang.VerifyError -- in Android

5. USB Host Mode: How to change permissions/ownership of newly created devices

6. Bug while selecting from a list of multi-select items whilst using filterable

7. Building Android using tcsh