Android Studio 3.1 not showing logs properly - android-studio

I am using Android Studio 3.1 for Android Development and it is not showing logs properly.
See the image below for more details:
In the above screenshot i am currently running app on an emulator. Only 2 lines in the logs are of the app that is running on the emulator. If i run the application on physical device, results are same.
I was also facing this problem on Android Studio 3.0 and earlier.
Any suggestions?

You need to set the granularity of the filter, this can be done from .
Enter the configuration in the dialog.
There is also option of "Fold lines like this" on the logs. You just need to right click and select.
This SO explains both configuration in detail.

Related

Setting up the Android Studio

[Here is the Screenshot] While setting up the Android studio, I can't run even the simple Application. when I click the run it shows to select the target device. but for devices, I can't select any device. It is still loading. What would be the reason?
Is there any version issue or Windows issue? I'm using Windows 11 and android-studio-2020.3.1.24-windows
There may be a problem with Windows 11. to solve that issue follow the steps
Go to the android studio app
Right-click the app
Go to Properties
Go to compatibility
Check the Run this program in compatibility mode
Select windows version 10 or 8 or 7
Then apply and ok
After these changes start the Android Studio App

How to run VUZIX Blade Template application?

Trying to create the first template application with the sample code provided by VUZIX Blade glasses. But, unfortunately do not know how to use the template application using Android Studio.
The Blade_Template_AppV2 has been imported and I am wondering on Android Studio to see the results.
Anyone tried to run the template application and got success?
You just need to enable debugging on your Vuzix Blade as described on https://www.vuzix.com/Developer/KnowledgeBase/Detail/1077 and you can run the template app directly from Android Studio on the glasses.
In order to run the sample Vuzix Code, you'll need to activate developer mode and adb bugging.
Because https://www.vuzix.com/Developer/KnowledgeBase/Detail/1077 is down and many other vuzix manual links are down, below I have detailed the steps to activate Developer Mode and ADB bugging on the Vuzix Blade.
Navigate to your settings, then click system,
system
followed by the info tab,
info
and once you're in the info tab,
swipe left until you activate Developer mode.
swipes will display like this
To enable adb bugging,
look for adb debugging in Dev Options and enable it on.
Before we move to the next step, make sure your device is manually plugged into your system.
In order to verify that the adb debugging worked, load your app from Android Studio, open up the terminal and type ./adb devices. Your device should be displayed now.
When you run your first app, you may notice gradle builds and other things differ and pop-ups will display asking to possibly downgrade certain options so that the hardware api on the glasses matches the app. Follow these instructions accordingly.
Afterwards, you should have a fully functioning app ready to use on your glasses' home screen.
This answer was supplemented by a response at https://blog.csdn.net/sinat_28962939/article/details/103065417

android studio emulator not selectable

I want to start coding with flutter, so i decided to download android studio.I created an avd called "Pixel 2 API 28" with android pie. When i want to select the pixel 2 as the avd device, the programme tells me that theres no avd, but on the right i can see the avd i created. When i put my cursor on it, it says "not applicable for the main.dart configuration". i have HAXM installed and Hyper-V is disabled, but i also tried it with both being active. I used the default code, which appears when you launch android studio.
Please help!!!
Edit:
I somehow managed to select it now, but i get this error: Running multiple emulators with the same AVD is an experimental feature. Please use -read-only flag to enable this feature.
Try starting the emulator from avd and then check if the device is showing up there if not try running
flutter devices
If the device shows there you can try running
flutter run -d <your-device-name>
You can also check whether the android sdk is configured with flutter try running
flutter config --android-sdk /path/andriod/sdk
hope it helps
Close Android Studio and Run again as Administrator
This is Only the solution i got after working hard for 3 days.

Wrong build being deployed on Android device using Visual Studio 2012 Xamarin.Android

I am using Visual Studio 2012 and Xamarin.Android Beta release to develop an Android application. When I try to deploy the android application for debugging purposes onto an Android device, it deploys the previously built application on the device and not the recent changes I made and deployed (i.e No refresh of build). However, if I use Xamarin Studio to do the same, it deploys the correct build everytime (i.e refreshes the build with new code changes).
Any idea why this is happening?
Thanks in advance!
I had a similar issue: With Visual Studio 2019 the debug version of my driver was deployed while building the release version.
The cause of my problem was, that in the Properties -> Driver Install -> Package Files I had an absolute path pointing to the debug version of my driver in the column File. This setting is valid for all configurations (not separated for debug/release), and when entering macros, they are immediately expanded to absolute paths.
I fixed this by editing the .vcxproj file with my favourite editor and changed the path back to $(TargetPath).
I had the same problem. My solution was to add "deploy" to the build configuration:
BUILD => Configuration Manager... => (select "Debug" from left-hand combo-box) => (tick "Deploy" in grid)
Courtesy of this xamarin forum post.
I have no idea why it does this, I had this issue before. I also noticed that the device log was somewhat behind (ie, at 3.30pm, the last record on the device log was 11.00am).
Uninstalling the app from the device and re-deploying it seems to correct it.
Note: I had this issue in VS, didn't check with XS.
I would look at the difference in your deployment settings in VS and XS (I think it may have something to do with the Fast Deployment option).
Similar question (though for iOS Simulator) here.
I had a similar problem (though on an Android emulator).
What didn't work for me:
restarting the computer
restarting Visual Studio
deleting bin / obj folders
going into Configuration Manager (Debug / Release / Configuration Manager) and ticking everything there - everything was ticked
changing the version of the app in the manifest
What worked for me?
Uninstalling the app from the emulator and then running Debug again.
It was an Android emulator, so I uninstalled by clicking on the app icon and holidng for long, and then dragging it to "Uninstall App". On an iOS simulator it should be similar.

there was an error attaching the debugger to the role instance

I am getting an Exception when I am trying debug my application on Emulator (Web Role).
you can see exception by clicking following link
Configuration which I am using Windows 7 pro, VS 2012 Pro, Azure SDK 1.8
Hope it might help others.
I Also had the similar problem and I restarted PC and **Run Visual Studio as Administrator**.
And let Visual Studio start the emulator with same privilege resolved the issue.
I was using Visual 2013 and Web API application under IIS Express.
Do you have IIS added? Most likely it's already installed but you've to enable it via Add Windows Compoenents on Control Panel...
I had this same issue all of a sudden, luckly I remember changing the ServiceDefinition.csdef file. I rolled this back to an earlier version and the debugger ran again correctly. The only thing I changed in the 'broken' version was instance size from small to medium.
Go to visual studio installer(search it from window's start)
and update the visual studio.
After updating, hit modify
button, after that on right side you will find a box named
debug (or something like that), select that box
Then hit install.
Restart your visual studio and debugger will start working.
In my case it worked perfectly.

Resources