ADB ERROR

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
VERSION".
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
either.
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
ignoring.
ANY HELP IS GREATLY APPRECIATED...Rc3375

--



ADB Error

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


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

--


Sponsored Links


Other Threads

1. Shop Stats ready for open signups!

Hi,

I posted a while back about a web service I created for Android sales
stats (

2. Question about intent filters for NFC tags (tech)

I'm reading the documentation on NFC tags and intent filters to match
on. For an action of ACTION_TECH_DISCOVERED, the intent filter must
list the technologies to match on, using a filter file. What I wanted
clarification on is whether or not I need to also specify for example
NfcA when I'm looking for a Mifare Utralight tag.

For the Mifare Ultralight tag, the documentation says this:
NfcA will also be enumerated on the tag, because all MIFARE Ultralight
tags are also NfcA tags.

This suggests to me that my XML filter file should say this:

<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
    <tech-list>
        <tech>android.nfc.tech.NfcA</tech>
        <tech>android.nfc.tech.MifareUltralight</tech>
    </tech-list>
</resources>

because if the tag is enumerating NfcA in addition to
MifareUltralight, my intent filter will only match if I specify both
technologies, not just MifareUltralight. Is that true? This applies to
IsoDep as well, which enumerates both NfcA and NfcB, in which case I
would need to specify all three. True? I don't have available hardware
to test this for myself. Thanks for your help.

-- 

3. How to disable global search key when dialog is shown?

4. LVL and new SDKs

5. android.media.MediaController

6. OK for one Service to bind to another?

7. Help with tabbed view