I'm currently trying to develop an application for Android devices on an Android Emulator. I installed Android 4.3 on a VMWare Workstation, on a Windows 10 OS.
I want to test the app I'm developping on the Android emulator, so I have to create a bridge connection between my phyisical computer where I develop the aps, and the emulator, where I can test it. But when I try to create this bridge, I have to change settings and to be root of the emulator. When I try to do a 'su' command, I have the following error :
'su : uid 10000 not allowed to su'
I tried to follow this tutorial to give me the root acces of the emulator, but it didn't worked for me. The best answer is to execute this commands :
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock03 /system
adb push su /system/xbin/su
adb shell chmod 06755 /system
adb shell chmod 06755 /system/xbin/su
How to get root access on Android emulator?
More over, When I did the installation of the Android Emulator, I've done the installation specifying the read-write option.
It is not working for me, because when I try the first row, I obtain this message :
ADB error : 'device not found'
Such as it is described in this link :
How to fix: Error device not found with ADB.exe
But the answer exists for a phone, and not for an emulator. Do you know how to fix it ? How can I be root, and how can I found the 'device not found' ?
Here are the different parameters of the VM
su stands for super users which is available only on rooted device. it is more like using android application with administrator privilege.Try using BLuestacks rooted version.
I am trying to run my application on my Device from the Eclipse In windows.But my device is not detecting there in the eclipse.
My device driver is updated. In My device, I turned on "USB debugging mode" in Settings->Application->Development and also "Allow installation of non-market Applications" in Settings->Application->Development. And in Eclipse Target tab, selected "Always prompt to select device". My ProjectBuildTarget is not newer than my device's version. And tried adb kill-server also.
When i run adb devices it shows nothing in my command prompt.
How do I get Eclipse to load my app to my phone instead of my AVD?
When i tried it in my Mac machine It works perfectly..
Any solutions? Please suggest me..
Please try the following:
Go to settings in your phone
Go to storage menu
Select connect as MTP
Worked for me!
If you are using a MAC OS.... no need to install the Driver
But for Windows, try this http://developer.android.com/training/basics/firstapp/running-app.html#RealDevice
Debugging to phone
Please see the link above, the process is defined there from google.
close you AVD if its running, then re-plug your Mobile device, check in your phone USB debugging notification should come.
try deleting your AVD and leave your phone connected, then restart your IDE. Make sure you've downloaded the OEM USB drivers. If it still doesn't appear on the list, hit refresh then just run your app.
Configuration
Os: OSX
IDE: Eclipse Juno
I don't know why but when I try to run again my Android app, the "Android Device Chooser" frame opens but my emulators are not shown in "Choose a running Android device" section. What should I do ?
Goto the DDMS view and try resetting the ADB as shown---
Please check the required API levels of the application and than on the device.
Try to run following commands in terminal that will renew the adb server state :
adb kill-server
adb start-server
You can try to use adb over the wifi and than no cables will needed.
I am currently trying to compile and test a small Android Application.
I am using Eclipse, and have SDK 4.2 (Api Level 17) installed.
I've set
<uses-sdk android:targetSdkVersion="17" android:minSdkVersion="8" />
although I've tried also different values (i.e. 17/17).
I do not use any GoogleAPI functions, nor do I use functions that are not available in API Level 8. Or at least I do not get any compile errors or warnings in that regard.
When I compile the project and run it on a real device running Android 2.2.1 the Application runs fine. However when I try to run the application on an emulator (Android Virtual Device) with Android 4.2, Api Level 17 I get the following error:
[2012-12-10 21:10:29 - SoftKeyboard] Installation error: INSTALL_FAILED_VERSION_DOWNGRADE
[2012-12-10 21:10:29 - SoftKeyboard] Please check logcat output for more details.
[2012-12-10 21:10:29 - SoftKeyboard] Launch canceled!
Logcat however is empty. I have really no clue, what this error even means...
It means you're trying to install an app with the same packageName as an app that's already installed on the emulator, but the one you're trying to install has a lower versionCode (integer value for your version number).
You might have installed from a separate copy of the code where the version number was higher than the copy you're working with right now. In either case, either:
uninstall the currently installed copy
or open up your phone's Settings > Application Manager to determine the version number for the installed app, and increment your <manifest android:versionCode to be higher in the AndroidManifest.
or https://stackoverflow.com/a/13772620/632951
You can also consider adding -d flag to adb install. It should ignore this error.
adb install -r -d abc.apk
First uninstall your application from the emulator:
adb -e uninstall your.application.package.name
Then try to install the application again.
This was happening in my project because I was using an XML resource to set the version code.
AndroidManifest.xml:
android:versionCode="#integer/app_version_code"
app.xml:
<integer name="app_version_code">64</integer>
This wasn't a problem in prior versions of adb, however, as of platform-tools r16 this is no longer being resolved to the proper integer. You can either force the re-install using adb -r or avoid the issue entirely by using a literal in the manifest:
android:versionCode="64"
This can happen when trying to install a debug/unsigned APK on top of a signed release APK from the Play store.
H:\>adb install -r "Signed.apk"
2909 KB/s (220439 bytes in 0.074s)
pkg: /data/local/tmp/Signed.apk
Success
H:\>adb install -r "AppName.apk"
2753 KB/s (219954 bytes in 0.078s)
pkg: /data/local/tmp/AppName.apk
Failure [INSTALL_FAILED_VERSION_DOWNGRADE]
The solution to this is to uninstall and then reinstall or re run it from the IDE.
In Marshmallow, I got this error,
Installation error: INSTALL_FAILED_PERMISSION_MODEL_DOWNGRADE
Please check logcat output for more details.
Launch canceled!
Looking for solution I searched and came here.
I deleted the app but still have this problem in Nexus 6. Later found that in,
Settings > Apps > [My app name] have to removed for all user.
INSTALL_FAILED_VERSION_DOWNGRADE
All Android apps have a package name. The package name uniquely identifies the app on the device. If same packageName as app that's already installed on the device then this error Showing .
You can uninstall the application from your device first and
then install the fresh one .
You could simply increase the number by one each time a new version is released.
I was having the same problem. I installed with
adb shell pm install --user <userId> test.apk
For some reason, there was no icon on the screen. It was a debug build and all other consecutive installs were not working. Simply uninstalling the package helped.
adb uninstall com.package.name
According to sdk src code from ...\android-22\android\content\pm\PackageManager.java
/**
* Installation return code: this is passed to the {#link IPackageInstallObserver} by
* {#link #installPackage(android.net.Uri, IPackageInstallObserver, int)} if
* the new package has an older version code than the currently installed package.
* #hide
*/
public static final int INSTALL_FAILED_VERSION_DOWNGRADE = -25;
if the new package has an older version code than the currently installed package.
I was having same problem. I was getting error when i tried to run in my android device not emulator.
sudo ionic run android
I am able to fix this by running
adb uninstall com.mypackage.name
you can try this:
adb install -r -d -f your_Apk_path
Do the following:
Simply uninstall the previous version of your application
Re-run the command
Enjoy :)
this happened to me when I imported an Android Studio App into eclipse.
I figured out the andoridmanifest.xml file needs to be slightly modified when importing from android studio project. I created a new test project, and copied over the headings to make it match. voila, issue solved.
This error appears in my android project with multiple kind of gfx files. At the end no change in the manifest file was accepted.
Because my lack of knowledge about the android devices I forget that my test device has a second User. This User also has an installed version of my app so I also have to delete the app for this user account and it works.
It may be a problem with the Google Play Services dependencies rather than an actual app version issue.
Sometimes, it is NOT the case that:
a) there is an existing version of the app installed, newer or not
b) there is an existing version of the app installed on another user account on the device
So the error message is just bogus.
In my case, I had:
implementation 'com.google.android.gms:play-services-maps:16.0.0'
implementation 'com.google.android.gms:play-services-location:16.0.0'
implementation 'com.google.android.gms:play-services-gcm:16.0.0'
But when I tried
implementation 'com.google.android.gms:play-services-maps:17.0.0'
implementation 'com.google.android.gms:play-services-location:17.0.0'
implementation 'com.google.android.gms:play-services-gcm:17.0.0'
I got androidX related errors, as I had not yet upgraded to androidX and was not ready to do so. I found that using the latest 16.x.y versions work and I don't get the error message any more. Furthermore, I could wait till later when I am ready, to upgrade to androidX.
implementation 'com.google.android.gms:play-services-maps:16.+'
implementation 'com.google.android.gms:play-services-location:16.+'
implementation 'com.google.android.gms:play-services-gcm:16.+'
Uninstall your current apk from the device then run
sudo adb uninstall com.package.name
It is the command to uninstall the apk via pc.
Then retry the build
the thing that kept on killing me was that i didn't know that this app was installed for my guest account (although I had uninstalled it for the other accounts..)
so i searched for the app in the app manager, and simply clicked on uninstall for all users
Just uninstall the previous Apk and install the updated APK
Like many I get this error but none of the solutions I found here did the job. I don't get this error when installing on an emulator, but I get this error with every app I'm trying to install.
This morning my phone went into save mode. After that I can't install an app anymore. The phone is already out the save mode though.
I don't get any errors in my logcat. Don't know what to do anymore. Could someone help?
It is similar to this question, but the only answer he got, I already tried.
Problem solved tanks to LisuBB
You can try to uninstall app from your device by executing
adb uninstall _nameofapp__
Try also to restart Android server
adb kill-server
adb start-server
and then try to install again.
check your phone's memory and see if you have enough memory . and restart it and check again.
Does the adb install work?
If so, try to install on an external sdcard through the cmdline.