Develop Reference

Parsing Error, When load Android SDK

After creating an Android application project I have found these two errors in console:
Error: Error parsing E:\Android\ANDadt\adt\sdk\system-images\android-22\android-wear\armeabi-v7a\devices.xml
Error: Error parsing E:\Android\ANDadt\adt\sdk\system-images\android-22\android-wear\x86\devices.xml

It might be a permission issue. Make sure you have writing permissions for that folder. Try starting Eclipse or the SDK Manager as Administrator.

in windows:
copy devices.xml file from
sdk\tools\lib\devices.xml
and paste(override it) to
sdk\system-images\android-22\android-wear\armeabi-v7a\devices.xml
This solution worked for me(try it).

For OS X user this is the only thing work for me:
sudo ./eclipse

Copy file devices.xml file(\sdk\tools\lib), and paste it to the location folder where the error occurred. This solution worked for me in Windows 10.

android eclipse error creating google map

[2015-02-06 17:50:29 - Mmap] Installation error: INSTALL_PARSE_FAILED_MANIFEST_MALFORMED [2015-02-06 17:50:29 - Mmap] Please check logcat output for more details. How I can solve those errors ?

Got same problem. Check your manifest file. Activity name should be prefixed with a period ".".

Android parse error Installation error: INSTALL_PARSE_FAILED_MANIFEST_MALFORMED (because of Capital letters in package name)

This question is linked with my earlier question. please see below link.
Android - Change package name of live application
So now i am buiding my apk with older package name i.e.,'AnantApps.Moodlytics'.
I also have made all required changes for that.
but after that when i try to run it on device, it gives me a console error like this.
[2013-10-22 11:26:03 - Moodlytics] Android Launch!
[2013-10-22 11:26:03 - Moodlytics] adb is running normally.
[2013-10-22 11:26:03 - Moodlytics] Performing Anantapps.Moodlytics.ui.ActivitySplashScreen activity launch
[2013-10-22 11:26:04 - Moodlytics] Automatic Target Mode: Unable to
detect device compatibility. Please select a target device.
[2013-10-22 11:26:07 - Moodlytics] Uploading Moodlytics.apk onto
device '4E4400F02B00CE54'
[2013-10-22 11:26:08 - Moodlytics] Installing Moodlytics.apk...
[2013-10-22 11:26:16 - Moodlytics] Installation error:
INSTALL_PARSE_FAILED_MANIFEST_MALFORMED [2013-10-22 11:26:16 -
Moodlytics] Please check logcat output for more details. [2013-10-22
11:26:16 - Moodlytics] Launch canceled!
After that i made one apk file. but here also, it gives me an error while installing apk.
Parse Error : There was a problem parsing this package
I think this error is coming because of the capital package name.
So now, i am in very much trouble. I can't change the package name to small letters and with capital letters the code is not working.
So help me guys. what should i do? How can i give un update to my already live application on Google Play which has 'capital letters' in package name?

So finally i find solution. Hope it will help others who are facing this issue.
I ran project in Linux OS. In linux os, eclipse doesn't give any error for capitalised package name.
1.) I renamed package name with capital letters
2.) Then I imported appropriate R in java files. (in my case it is AnantApps.Moodlytics.R). (We can replace old R with new one easily by find/replace functionality of eclipse)
And thats it.
Main problem is that you need to have Ubuntu Linux OS for this.

Please You should delete your gen folder from your workspace..After that give build project. Now You can run your application..Please try it.

Using Android Studio.
U must change in manifest file like that
<uses-sdk android:minSdkVersion="14" />
and Also change In Gradle Script
Gradle Script->build.gradle(Module:app)
defaultConfig {
applicationId "" >>//Your Package Name
minSdkVersion 15 >>Here also give minsdkversion which is given in manifest file
targetSdkVersion 21
versionCode 1
versionName "1.0"
}
Package Parsing error solution

Error:java.lang.NullPointerException in android

[2011-02-18 23:41:16 - ddms]null
java.lang.NullPointerException
at com.android.ddmlib.Client.sendAndConsume(Client.java:571)
at com.android.ddmlib.HandleHello.sendHELO(HandleHello.java:142)
at com.android.ddmlib.HandleHello.sendHelloCommands(HandleHello.java:65)
at com.android.ddmlib.Client.getJdwpPacket(Client.java:670)
at com.android.ddmlib.MonitorThread.processClientActivity(MonitorThread.java:317)
at com.android.ddmlib.MonitorThread.run(MonitorThread.java:263)
What kind of error is this..All xml files are having error suddenly like below..
Multiple annotations found at this line:
- Premature end of file.
- error: Error parsing XML: no
element found
thank you,

The first group of errors generally mean that there's a problem in the communication between ddms and the emulator you have fired up. I've found those errors to be generally harmless.
The XML errors sound like you should restart Eclipse (if that's what you're using), or else clean your project. Something got out of sync. (If the problem persists, post an example of the XML that's generating the errors.)

This error started showing up for me after I experimented with deleting files from the AVD. I must of deleted something that was important. I got rid of the error by closing the emulator and deleting the AVD in Eclipse and then recreating and running it.

Cannot run Android application on emulator/device - activity doesn't exist?

When trying to run my application on the emulator I get an error from the activitymanager:
ActivityManager: Error type 3
My activity exists, is listed in the manifest (in fact, its the MAIN launcher activity).
Anyone know what this error means?

If you are running Eclipse try Projects-->Clean... and clean the project before running again.

i faced the same issue. I cleaned the project and removed the android:enabled=false in android manifest. This solved the issue.

Check "android:installLocation" in your AndroidManifest.xml.
"preferExternal" will cause the problem.

I got this error because I used invalid characters in my project name and Android didn't warned me about it so I had no idea that was the problem...
Example: "Thís ís íncorrect!"

nothing to worry about that it happens sometimes when activity manager unable to find activity of your app that means your target that is emulator is not started yet or may be because of following reason:
when you try to run your app on emulator you may be cancled in between building or forcefully closed your emulator.In that case when try to start emulator again it will sometimes not maximized.
now you have to restart your eclipse and then launch emulator and run your app now you will not face this type of error

Dont remember how I fixed this - most probably I wiped the local copy and re-checked out of svn.

ActivityManager: Error type 3
I don't know how true it is, but I used the same shared preferences file from another app..and got this error. I chose a new name for the shared preferences and the problem has gone away. It's working now

I had not enough space on my phone, that's why I had this problem.
So I cleaned it and go RUN )

I got this error when I mistakenly added a second application tag in my manifest as I was trying to add hardware acceleration to my app:
<application
android:hardwareAccelerated="true" />.
I added it above my actual application tag and I think this resulted in Android deploying an empty 'app' to my phone. It reported 'Installation success' in the logs and yet there was no launcher icon. It did appear, though, under Settings -> Apps but the only thing I could do there was to uninstall it. Hope this helps someone.

Thus, it seems there can be many reasons to see this error.
For those who can't fix it using the above mentioned methods:
In my case, i renamed the name of my activity (using F2 in Eclipse) and it is fixed.