Android connection giving error while connecting to a Flutter app - android

I am learning Flutter and When I tried to run the app in the physical device but it is giving error.
The following error is displaying in the Run Console in Android Studio:
F/vendor.qti.esepowermanager#1.1-service(18196): Error while registering eSE power manager service
I am trying to run the app on Redmi Y3/Redmi 7 running a custom ROM: PixelExtended-5.0 _onclite-13.0-20221011-1032-OFFICIAL.
I have tried to turn off and on the Developer Options and USB Debugging multiple times and even reset the handset, but nothing works..

Related

Unity remote debugging to android is not working

Im quite new to mobile development and im having a hard time getting the debugging on the phone to work. This is the error message i get
CommandInvokationFailure: Unity Remote requirements check failed
C:\Program Files\Unity\Hub\Editor\2021.3.9f1\Editor\Data\PlaybackEngines\AndroidPlayer\SDK\platform-tools\adb.exe forward tcp:7201 tcp:7201
Im using Unity Remote 5 on the phones
Ive tried 2 different android phones
Ive tried 2 different projects. My own and a brand new Unity Mobile template.
Ive enabled developer mode on the phones
Ive enabled USDB debugging on the phones
Ive tried disabling /renabling usb and developer mode
Ive given the phones transfer files access
The editor Unity Remote device setting in the unity project is set to Any Android Device
If i go to Build Settings i can see my phone as selectable
I can actually build and run and have the project start on the phone

Why did Android Studio successfuly pair to Device by WiFi then suddenly drop?

Problem pairing Android Studio to Device by Wi-Fi
I managed to pair an Android Device to Android Studio via Wi-Fi using a QR code. But then I got a "Default Activity Now Found" error when I tried to run my program to the device, I went through the steps to fix that error. And that led me to not only cleaning and rebuilding the project but when I restarted Visual Studio, I thought I would remove and re-add the listing in Device Manager.
And this is where the problem is. Since I removed the device listing in Device Manager, I have not been able to get it back. I have been trying both the QR code as well as the pairing code. The Android cell lists the computer. But each method I have tried to get Android Studio to recognize the cell, it fails. It says it may take up to 2 minutes to complete but it will say that there is an error pairing the device. It does not matter if I the computer name from the list of paired devices on the android or not.
The address and port number appear on the page for Wireless debugging on the Android device. When I try to use it in the Ubuntu OS where I am using Android Studio with:
(adb connect ip_address:port_number)
adb connect 192.168.0.13:37049
It states:
failed to connect to '192.168.0.13:37049' Connection refused
When I try to
adb tcpip 37049 it says:
error: no device/emulators found

"Service Protocol" Error Prevents Testing Flutter App on Real Device

While testing Flutter apps on a connected (by USB) Android (Samsung S5, running API 23) device using:
Android Studio 20201.3.1 Patch 3
Mac OS Monterey
The app will run on the device the first time, but subsequent attempts result in the run tab saying:
Error connecting to the service protocol: failed to connect to
http://127.0.0.1...
The only way I can solve it is by restarting the device (the phone).
There must be a better way than restarting the device every time I test/build.
Does anyone know the cause and/or solution to this?
A workaround is:
While the project is open in Android Studio as a Flutter project,
Navigate to MainActivity in the Android\app\src... folder
Select "Open for editting in Android Studio" at the top-right of the screen.
Then when the project is open "as an Android project" you can run it however many times you want. (Flutter is no longer involved).

Android Device Manager fails to start device

I was trying to test a xamarin app on an emulated android device so I set up hyperV, created the device and started it. However, as seen below, it fails to boot and it's unclear to me as to why. I'm guessing this has to do with hyperV but really not sure.
Update: After leaving it running for a bit it popped up the following:
Emulator error
Device error: Could not get emulator name after starting AVD pixel_2_pie_9_0_-_api_28

React-Native android device can't see console remote debugging

I'm working on a React-Native app, I am testing it on a physical android device, the MOTO Z2 Play. I would run an emulator, except I have an AMD processor on my rig and can't run those emulators, unfortunately.
So I'm trying to enable remote debugging on this device while developing, so I can see console.log() statements that I put in the code. The problem is that when I the debugger opens the browser and I go to the console to view the logs I see the following errors:
What do these errors mean, and how can I get the console to show logs? Or is there another way I can view logs without having to enable remote debugger? Thanks!

Categories

Resources