I'm working through a few Android applications and whenever I try to filter out the LogCat to find why my app is not running, nothing shows up anymore.
I've tried going to DDMS, resetting the adb and restarting Eclipse. I've also tried to make sure my Emulator is selected from the list of devices, although my app does not seem to be present under the Emulator (com.android.myapp), so not sure if that's the issue.
I also do realize that this question has been asked many times but I can't seem to find a fix using other solutions.
Any help would be greatly appreciated, thank you.
Also let me know if I need to provide any extra info.
Related
There seem to be too many bugs which have not been properly documented, regarding android studio. I am trying to run a basic Hello world app, and this error is truly making me give up any more efforts.
What I did:
Open Android studio(also tried running as administrator) and tried to run the default Hello world app on an Android 10 device(Xiaomi). At the start it shows Failed to start monitoring 7D8XXCOJGQQCZLJV(device number). At first I ignored it being a beginner and clicked on the run button. The file was successfully built and the RUN section shows 'Install successfully finished'.
Now for clarity here are some screenshots that will display what happened on my android device after the above steps:
The app seemed to be installed correctly, but whenever I click on the app logo the response I get is really frustrating:
As per the this link I tried to go to the device manager and do some changes, by setting and enabling Xiaomi drivers for Portable devices.
But then windows shows:
If anybody knows how to solve this, please do help me in doing so. It is quite discouraging to experience so many errors, right at the beginning. If somebody could give a working solution then that would really help me in continuing my android journey.
There was just a tiny error that led to this entire problem. This was because I had set the value of android:exported="false" in the main activity, which had to be set to true. Hope that this may help anybody in the future!
set the value of android:exported="true" in the AndroidManifest
If this is a stupid question because I made some terrible mistake, please let me know. Anyways, I just encountered the error and after searching on internet for quite some time, the only similar error that I could find was here But my situation was different.
1). I tried to create a new project from File menu of a previous project.
2). I clicked on Basic Activity and selected mininimum supported API to be 19.
3). I was following this tutorial by Google Developers.
4). I was previously able to successfully build and run from Empty Templates, but now, even they show this same error.
Here are two screenshots: Error & Window
I have tried to restart computer. I have NOT yet tried to download and re-install Android Studio yet. I do not know of any good troubleshooting besides restarting computer; so, if someone wants to share some tips, please be kind enough to do it.
I have not edited or tried to do anything in the automatically created project. I have not editted any file, until I noticed that even #color/primaryColor could not be resolved. So, I went on to look into the res/values/color file and found out that it had no color values in it, instead there was a single line: androidx.constraintlayout.widget.ConstraintLayout xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-au. So, I checked further, and found out that many of the automatically generated files had several errors in them.
I am on a Windows 10 machine. Please help, if this question needs to be edited, please let me know. Thanks a lot in advance.
I know this may have been asked here before, but still didn't get any solution. I have closed logcat and reopened it, closed eclipse then restarted it, nothing helps. This was working perfectly before but suddenly I found out that logcat not showing messages of my apps anymore, it is showing device messages only. I use a spice mobile device instead of emulator, at first I thought it can be a problem related to device, but then tried the same with android emulator and same thing happened. What have gone wrong? What should I do now?
Create a filter for your app using the package name.
Eclipse do it automatically when you launch your app, but it fails sometimes.
Hope this helps.
Can u see these? Try Android Studio.
images to all messages!
I have this annoying problem, that Im pretty sure happens to all of you too.
I add a filter to the logacat in order to see message that belongs only to my application.
The problem is that the logcat doesn't get updated while im in the current filter (it happens for every filter, including "All Messages (no filter)" filter).
In order to see all the messages i've missed, I need to click on the filter with the mouse.
How to fix this??
thanks!
Unfortunately, this is a bug in eclipse or in the adb or logcat. maybe other versions of eclipse beside "classic" won't suffer from that bug, such as Eclipse Indigo. worth trying
I recently started messing with Android Apps, but I have had nothing but problems trying to get them into the Virtual Device for testing. For some reason, they never seem to show up in the AVD. It has worked one time, but that's it out of hours spent just trying to test one or two very simple apps.
I've redone the AVD setup many, many times, trying different settings and what not to no avail. I've followed multiple guides and tutorials to the letter to get it working, but they just refuse to show up in the list. :(
Any insight would be appreciated, thank you.
I would start by testing apps that are known to work. Here are sixty or so of them.
In particular, I would start with this one. Do not change anything. Do not import it into Eclipse. Just install Apache Ant (if you haven't already), and run ant install in the project directory with your emulator running.
Either this shows up in your emulator, or it does not.
If it does not, try reinstalling the entire SDK.
If it does, then you know that your base environment is OK, and you can start slowly determining the differences to figure out where things are going wrong.
Helping you is difficult right now because your symptoms are a bit generic. It could be that you are using Eclipse and Eclipse is having a problem. It could be that your adb daemon is having a problem. It could be that you don't have any activities in your manifest, so the application is actually installing but there are no icons in the launcher. And so on.