Android Studio not showing logs - android

I recently updated OS of my phone(Lenovo K3 Note) to Android Marshmallow(API level 23) after that I'm not able to see any logs related to any application which is running on the phone. I'm not able to check on any other device which have Marshmallow but I tried working on emulator which have Android Marshmallow(23) and everything is working fine. Everything else is working fine if I use any other device which have Lollipop or lower version. I'm not sure what is wrong. Please help.

Restarting the devices (mobile and computer) or updating Android Studio did the trick for me. So if something like this ever happens after an update then try restarting the device.

Is it possible that the update disabled developer mode?

Restarting the device worked for me too.
For the safer side, I did Invalidate cache and restart in android studio

Related

Why Android studio won't run app on Android Pie (9.0)?

I've upgraded my Google Pixel to Android 9.0/Pie.
When I try to run an application from Android studio I don't see the Google Pixel in the list, there's only a null device named FA69R0306649. When I run my application, Android studio tries to install the app but then fails.
It looks like Android Studio is not recognizing the phone anymore. It Worked perfectly fine a couple of hours ago under Oreo (8.x).
Also, if I deploy the app on google play as alpha and then download it runs perfectly under 9.0/Pie.
Any suggestions to get the run/debug working with android 9.0 phone under Android Studio (3.1.4)?
The Pixel running 9.0 requires USB 2.0 high speed.
Apparently the Pixel running Android Pie cannot talk to the PC using neither USB 3.0 nor USB 1.1 full speed nor USB 2.0 running at full speed.
I had a similar problem with my Xiaomi Mi A1. When I upgraded from Android 8.1 to 9 Android Studio would hang on "Installing application" forever.
After trying revoking USB debugging authorization and completely reenabling developer options with no success it turned out a simple restart did it.
Looks like there are multiple issues that lead to the same problem.
I had the same issue with a Xiaomi Mi A2 after upgrading to Android 9. If you are using Linux, try adding the udev permissions manually, following the steps described here. In my case, that was the only solution that worked.
Please re-enable developer options again after the OS version upgrade, the device name will appear and it will be working fine again
Install Sdk Platforms of Android 9. In Android studio Top Right besides Search Icon.Press That Icon of SDK manager and look either sdk platform is updated and installed.
A simple solution just go to your Developer option on your phone , right below the USB Debugging option it says to "install via USB" just enable it and you are all set to install an app through android studio into your 9.0 device.

Instant run issue on Android Studio 2.2

I have updated my android studio to 2.2, Since then I get this strange issue when running the studio gives me error Instant Run requires that the platform corresponding to your target device (Android 1.0) is installed. I am using Note 4 on android 6.0.1. Why is this error happening ?
If you have connected your android device, unplug it then uninstall the current app. Then plug the usb back and click run. You good to go.
Am also facing similar issues since i downloaded the upgrade patch for android studio 2.2
i have noticed it happens when Android monitor says device offline Android device says offline yet connectet
The reason why the device goes offline and yet its connected properly i don't know yet. When i click download i get this error Package id platforms;android-1
I currently sole this temporarily by checking if android monitor says device offline, if yes i unplug the USB and plug it back in else it just runs fine
I had the same problems as you all and I solved it.
If you get an error like 'error Package id platforms;android-1 ' you must go to: Tools -> Android->SDK Manager, and thed to SDK Platforms. Make sure that 'Show Package Details' tab is checked (so that you can see all packages) and Android 1.1 package installed.
Otherwise just install it like all others packages. After you do this, restart Android Studio, unplug/plug phone. You will be asked then to conform something at your device, say ok and you fixet problem.
I got the same problem, but with an emulator.
So the answer of unplug/plug the device is not applicable to me.
I deleted my emulator and create a new one in Android Studio.
And, it's solved...
Connect to your computer as MTP. After this Android Studio will recognize your device and SKD could install for it.l
I've solved this by changing the USB cable. The one given by Samsung is useless.
I had the same problem but it solved after I approve the confirmation box for connecting the phone to the computer.
Running the android studio as sudo did the trick for me.
i got same problem , i have unplug my Device then uninstall the current app. Then plug the usb back and click run. i am good to go and my Problem
In this Video there is a Solution for Error running app: Instant Run requires 'Tools | Enable ADB integration' to be enabled. It worked for me to disable the instance run error messages.
In my case SDK location was incorrect.
I disabled Instant_Run option.
please check SDK version in local.properties file.

Xamarin Android Player is unable to run API 21 or higher emulators

I'm using Xamarin Studio and Xamarin Android Player on my windows 10 PC.
I'm having trouble starting Lollipop/Marshmallow (API 21/23) devices using the XAP, but on the other hand, launching Kitkat (API 19) works prefectly.
I've downloaded the required android SDK, tried reinstalling everything again and again but nothing works.
It seems wired, because it is not a problem with Virtual Box, nor with my PC or my XAP installation (if it was, than why Kitkat works?).
I've tried every solution I could possibly find, but nothing works.
Any ideas on what could cause this problem?( If further information is required, I will be happy to add :)
EDIT
It does not matter whether I start the devices through VS/XS/XAP. It all comes down to the same problem, but for the sake of simplicity, let's say I'm running them directly through XAP. Here is a screen shot of what happens when I launch Lollipop (which is API 22, and not 21, for a strange reason) :
For like 5 minutes, the following occur:
Than, forever:
And after a few hours it says booting or something like that, and than restarts to the first position.
With Kitkat, it just starts :).
you probably missed the intel HAXM update.. may be a possible duplicate: Android 5.0 (API Level 21) AVD not launching Intel Atom x86_64
First off, it's difficult to determine the problem without more information. Please list or screenshot the build error(s) you receive when you try to debug your app on a XAP emulator.
But on a hunch... within the past week, I had a problem with similar symptoms. In my case, I had to update project packages in order for my Xamarin Forms project to run on the higher Android APIs.
Reference on how to update packages: https://developer.xamarin.com/guides/cross-platform/application_fundamentals/nuget_walkthrough/#Package_Updates
It might be that hyper-v is causing the problem: "VirtualBox and Hyper-V cannot co-exist on the same machine".
Try to disable it using bcedit as explained in the link.
For further reference, see this discussion
After launching xamarin android player, manually launch virtual box.
You should see the device listed on the left. There is a good chance it will say "stalled." If it says anything other than "Running," try reseting it or starting it.
I also had problems with XAP and my solution was to use Genymotion instead.
Did you try Genemotion
I think it is best Android emulator.
I would post a comment but my reputation is too low.
I don't know if this emulator works with Xamarin studio but if you use Visual Studio it may be an option for you.
Here is the solution:
I had the similar issue and fix the issue as follows.
delete the existing device simulator
reinstalled the simulator again
deploy the solution again.

Visual Studio Cordova App not updating on Android device

When I deploy my app to any Android device I get an old version of the app. I have factory reset the android phone on Kitkat 4.4.4 and have also tried installing on a newer android 5.0 device. I am always getting the same old version cached. When I debug with the ripple emulator I always get the newest changes with no issue.
I have tried adding 'preference name="useBrowserHistory" value="false"' to the config.xml in the solution with no luck. One notable change that has happened is I have moved to a new computer and I did not have this issue on the old one.
Any help would be greatly appreciated.
Have you tried to delete the bin and bld folders in your project before you deploy? It might be that for some reason your Android project is not being rebuilt. This should force it.
Try to use the option "Revoke USB debugging authorization" above "USB debugging" to update the authorization Keys in Developer Options in your Android Phone or Emulator.
I use Visual Studio 2015 with Xamarin and works for me.

Unable to debug on IntelliJ on some phones

I am unable to debug on IntelliJ one of my apps, other apps debug just fine. The issue is only happening on my Galaxy Nexus 4.2.2 and on my Nexus 7 4.4.2. My GS3 with 4.3 works just fine.
The error I get is:
Warning: debug info can be unavailable. Please close other application using ADB: Monitor, DDMS, Eclipse
IntelliJ support says it is an issue with ddms, and I do tend to agree with them because when I open ddms by hand I can see no processes under the phones that don't work but I can see a bunch of processes under the phone that works.
Has anyone else had this issue?
IntelliJ is version 13.0.2 and I am on OSX 10.9.1
Thanks.
EDIT: I should mention I already tried restarting phone and laptop, removing the app from the phone, clearing data, clearing cache, clearing caches on intellij. Also I tried other apps yesterday and they worked just fine on all devices, so it seems to be just one app, I don't know if there is a way to clear something on ddms that it might be remembering about my app?
Turns out that when using an artifact that signs your app you must set debuggable=true on your application on the manifest.

Categories

Resources