I just got a samsung Galaxy prevail phone and i was going to install my app on the phone. but it dosen't give me that chose. I use my brother phone the newset evo and I was able to just fine so the
android sdk was install correct. I also did not get a plane or activation.
my qustion is do i need to download a file or activation before i can install the app i made?
thank you
ok so I went to setting and made sure that unknow Sources is on. However it still not showing up on
the AVD manger and I guss i should tell you guys i have a pc.
On your phone ensure the following is checked:
Settings→Applications→Unknown sources
Download and install the Android SDK and run:
adb -d install "the_name_of_apk"
If you haven't signed your app then you need to enable untrusted apps.
From the home screen press the menu button then
Settings->Applications->Unknown Sources
That should allow you to install your application
Related
I have a clean Android project on Android Studio (just with a "hello world' screen), and I'm trying to install the app on my Samsung Galaxy S10e.
I click the Run button, and this is what I see in the Build Output:
And the apk is generated successfully.
But it's not launched and not installed on the device (no icon, and it doesn't appear in the apps list).
When I try manually installing the apk by adb install app-debug.apk, it works. The app shortcut appears on the device, it's added to the apps list, and I can launch the app.
At first also adb install didn't work, giving out the error INSTALL_FAILED_TEST_ONLY, but I solved that by adding android.injected.testOnly=false to gradle.properties.
I tried changing Gradle version to 6.0.1 (looks like this is the latest at the moment), and it didn't help.
I also have my device selected at the top:
How can I make Android Studio install and launch the app on my device?
Android Studio version: 3.5.3
Edit:
I'm seeing the same behavior on an Emulator. I opened AVD from Android Studio and chose Pixel 3A. The emulator opens up, I run the app, nothing happens on the emulator (and I see the same Build Output messages).
The same happens to me. It is probably a bug in Android Studio. At the second compilation the app installs correctly. It is tedious.
There isn't enough information to find the cause of this issue.
But since it works with adb, it means you run adb command. There could be only one instance of adb daemon running. So if it's involved externally my guess is Android Studio won't have access to it.
Possibly try adb kill-server and running again from Android Studio and see if that helps.
I encountered the same problem, which I solved by checking the running devices. The connected phone had 2 accounts (might be personal & work) which was listed on the list of devices, so I had to select the second option, and it ran successfully on my phone. see the attached image.
One thing it might be:
Enable usb debugging
Settings
System
Developer options
Turn the setting on for usb debugging
If it does not appear go to settings about phone. Then click on build number like 7-10 times and it will enable you to have the developer options appear.
I'm having an issue where the app I'm working on is not deploying to the device when I'm ready to test it out. It used to do it just fine, but then I updated to 5.0.1 Lollipop, which I believe to be the culprit. Besides downgrading back to 4.4.4 KitKat, which is quite the process on my bootloader-locked Galaxy S4, what can I do to resolve this? ADB recognizes my device and the project builds with no errors/warnings. However, the app does run and work normally if I build the signed APK manually and send it to my device via email/PushBullet which is just a lot of extra, unnecessary steps.
I'm sorry for the lack of information, I'll update as tips come along as to what I've tried. I don't know where to start. One thing I have tried was changing all compile sdk versions to 21, but no dice. It does pop up with the green bubble "session 'app' running" but nothing happens on the device. Also, the ADB pane reports "no debuggable applications." The big issue here is that I can't debug my applications at this point since I can't view the logcat. Any help would be greatly appreciated.
My phone has SuperSU (a rooting app) which updated and caused this problem. As part of the update it had switched off the preference to allow processes running as system user to gain root access without confirmation. I simply enabled the 'Trust system user' option and it worked as normal.
Hope this helps someone :)
Please un install the application if already installed and install again.
there is a kind of issue that application installed but not auto launched. You nee to launched explicitly but If app is already installed then you can't identify that your new installation works or not.
Once un install and install again and track if found installed.
Open the "Edit Configurations" pane and click the '+' button. Select the option to create a new 'Android Application' and then select the correct module. Apply, and you can then delete the test configuration you were using before if you wish. Then everytime you run, make sure you are running as an Android Application and not a test and it will auto-launch on install.
It turns out on my device (Galaxy S4 Lollipop) they added a security feature which didn't allow for ADB installs. The solution was to get root permissions and install adbd Insecure app from Chainfire and run it. Works flawlessly now.
i have one doubt,i have created new project in eclipse with android 2.3.1 and try to debug directly from eclipse to device.and it's wokring well,it's debugg in device.now when i am converting that version of android 2.3.1 to GoogleApi 2.3.1 by right clicking project and changing android property.after that when i run my project i am getting such warrining kind of symbol as u can see in below image.
again when i am changing version to simple android 2.3.1 than it's get debugging from eclipse to device.
my device name is Sony Ericon Walk Man Live and ya one more thing Google API version working well when i copy apk to sd card directly and installed in device,but getting problem only when i am running from eclipse to device directly.
One another thing i noticed is that when i create a simple project than right clicking project and runing it's asking me to wether to run in device or emulator but in older one it's not even asking and directly running in emulator...in both's project manifest there is no tag like android:debuggable="true/false" also...
any one have idea what is a solution of this problem i have already insatlled device driver to pc as well.
please help me to short out this
Thanks in advance
Aamirkhan I.
Enabling USB debugging is key, but there's something else as well. Eclipse, by default, runs your application automatically after the first run. So, if you choose an emulator as your first run, Eclipse will default to run by emulator every run afterwards.To change this, go to your "Run Configurations".
There will be an option to run manually or automatically.
Choose "Manual" and you will prompted to choose between your emulator and device every time you decide to run. Otherwise, you can set whether to run automatically with your device or emulator.
try as in this link
If you already connected your mobile device with your computer via the USB cable, please unplug it from your phone, otherwise your device will prompt you a warning requesting to do so.
I have downloaded some sample source codes, modified them and made a audio-video player.
The player is supporting minimum Android version 2.2. I ran the app in my tab, as well as phone.
It's working fine for my Android phone, but not in my tab. I am not sure why this is happening.
I am not even able to install the .apk file in my Android tab.
Can anybody suggest me what may be cause of this?
In order to install apps from places other than the market, you need to enable that in Applications settings - allow unknown sources. enable it.
enable usb debugging also
With the debug tools installed, you can install an apk from the command line by saying
adb install my.apk.
I want to run my Android Project iwrote with emulators on my Android Device. The Device is Connected on an USB-Port. When I start the "Android Device Chooser" nothing happens. No running device in the "Choose a running Android Device"-Table is displayed.
I tried to reboot the system(PC and Smartphone) while connecting. I tried every USB mode. I tried another Device( G1 and HTC Desire). Unknown Source is always true.
I tried another Eclipse-Version(64 and 32 bit), tried another SDK(64 and 32 bit) and reinstalled the android sdk.
I still can't see any device. Everything worked fine on my old 32 bit system. Now i have to work with my 64 bit lenovo. (both windows 7)
somebody got another idea?
Thank you.
Fabian
See this link for detailed info: http://developer.android.com/guide/developing/device.html#setting-up
In short, you have to:
Mark your app as debuggable (in Manifest)
Allow USB debug on your device (Settings->Application)
And, if developing in Windows, download drivers.
Try command line "adb devices" to see if your phone is detected ok. Except limited number of phones supported by Android by default, manufacturer-supplied setup needs to be used to start usb mode. In my case, Vodafone 845, setup was contained in phone storage. So after phone was detected as normal usb storage, I located that utility and simply ran it. Then it started to be detected as android phone.
The easiest way to this dilema i found here. If you are on windows,
Make sure you have install the google usb driver
Ensure USB Debugging is enabled.
download the adbdriver setup from http://adbdriver.com/downloads/
just follow the wizard and install, automatically it should see your device or you try restarting android studio.
Enable USB Debugging :
Setting - About Phone - Tap Build Number 5 times.
Then go to : Setting - Developer Options - Turn On Usb Debugging.
Download and install Wondershare Mobile Go / Snappea. That program will download and install your android device.
If this popup appears, click allow.