I need to enable logging in my Android's release version. Nothing is currently showing up in LogCat. I'm using Android Studio 1.5.1. Is there something in Gradle that I need to include?
There are a few things you could try.
1) Restart Android Studio and/or your computer. If you're using adb twice or more (e.g. in the terminal as well), things get confused.
2) Make sure you don't have a Logcat filter applied.
3) If you see "Devices | Logcat" it means you have both pieces of content in the same place, and might have accidentally made the Logcat part take up no space – try looking for a resizeable border that you can move to make them sized better.
Related
i have android studio 4.1.3 and i'm wondering if it has a setting that i can change so i can see debug in real time. I'm currently using visual studio which tells me in console where i'm wrong as i'm typing. I'm typing the code in vs and then pasting into android studio but it's getting tiresome especially if i have a lot of screens. Is there an easy way that i'm missing? And yes i have tried to google the question already so please don't tell me to google.
Unfortunately, android Studio does not currently have a live debug feature.
You do have a debug option on the top right corner of the screen if you need it.
The closest thing to what i was looking for is the "Dart Analysis". It's located at the very bottom next to the "terminal" button. I've tested and i see if i change something, it immediately notifies me in the "Dart Analysis window"
I've been having issues with security while submitting to Google Play, but I've finally determined that the issue lies with Xiaomi Mi Game Center (thanks to this and the first image, from my Play Console). However, I can't seem to find any way to uninstall it. The option to remove it has disappeared from my Build Settings (image 2), so I tried to find it via Finder and didn't have much luck. I searched for it, but I didn't want to just start deleting files willy nilly in case I deleted something important (image 3). Any idea how to get rid of it? I'm using Unity 2019.2.13f1 on a Mac running High Sierra 10.13.6.
You should be able to remove it from the Build Settings indeed, I do see the option to remove it, but I am on 2018.4.11f1.
Can you try going to the package manager via Window --> Package Manager, and checking there? I do see it there, with also an option to remove it.
When I run my Android application in Eclipse on my machine, it automatically sets up a LogCat filter for my application, and only shows lines that are relevant to it.
However, running the same application on another PC (which happens to have Eclipse 'Mars') running on it, it just has one filter saying 'All messages (no filters)'.
Is there a setting somewhere to turn this on?
And incidentally, I know that I can set up a filter manually, but I liked the functionality that I had before, so I just want to turn that back on.
Regardless of what IDE you use I would recommend you take a look at pidcat.
From the repo:
Colored logcat script which only shows log entries for a specific application package.
You do need a bash terminal.
I will also recommend you move your project over to Android Studio.
I'm trying to create a (root) app in /system/app, but having an issue that I can't resolve without seeing some errors and debugging to see exactly where it's going wrong.
If I run from Eclipse, errors are expected however, as the app won't have appropriate permissions.
How can I run a local (/system/app) installation, and somehow see what's going wrong?
Can it be done from Eclipse? I had a look at this - but it's so poorly formatted I couldn't make sense of it. If it can't - is there some way to print errors as text?
STEPS-TAKEN: Not sure what the source of the problem is, but the quick description of the bug is that:
I install all required software, SDKs, configs,
Then create two new projects each using the tabbed-window template, each of which support deployment to Android.
Then I run one project via Titanium Studio's Run option, let the Android Emulator load, and confirm it's the app is installed an working.
Then I closed the emulator, and then run the other project the same way as the last, though when the app is shown on the screen it has the name of the first app, not the app run.
FIXES-TRIED: I've attempt executing "Project >> Clean" for all projects before the second run, and still get the same "bug".
SETUP: To my knowledge all of my configs are correct, and clearly the build "works" though it is very possible there is something wrong with my installation build chain to get to the point I'm running the app in Titanium Studio via the Android Emulator.
ERRORS: I've reviewed the console output for FastDev, AppInstall, Android-Emulator, etc and have seen no error messages that jump out; meaning I have seen no error messages, except for build.py error after the first script runs saying it didn't find the script running on a port when it attempt to kill it; given the request is to kill itself, and it's not found, I just assume this is a confusing way of saying the script did what it was suppose to do.
Current build: is on Windows-XP-SP3 using TiStudio 2.0.1 build, JavaSDK 1.6, r18-Android, and Android-2.2
Recent emulators have persistent state, so your second launch probably gets back the system you were running before.
You should not have to resort to this on a regular basis unless something is broken in the workflow, but deleting the AVD and making a new one should get you a clean slate.
I believe there is also a startup flag to the emulator which tells it not to use the checkpoint from a previous run, but start from scratch - you could try to change your configuration to use that flag.
A downside to either deleting or forgoing checkpoints is that the emulator will take longer to start up.
Really though, you are supposed to be able to re-install or launch a given application, or install a completely different one, all within the same running of an emulator. You aren't supposed to need a new emulator, any more than you need to go buy a new device (or perform a factory reset on it). So something is not right in the setup, and the best solution for long term productivity is to identify and fix that. Short term of course, you might need to wipe the slate clean if that helps you meet today's deadline.