When running my kivy app on Android Kivy Launcher it crashes instantly. I've looked everywhere for the logs, but couldn't find them. No .kivy folder is created, apps that view android logcat require root access and I couldn't get working adb logcat. Can someone explain to me how to use adb logcat to catch the error, or state another solution to my problem?
PS: The app uses kivy 1.9.1 and py 3.4.4, runs fine on windows and my cellphone is a Xperia Z5 running Android Marshmallow 6.0.1
Finally figured out how to use adb logcat. Install android studio 2.2. Connect your device to the PC via USB and enable debugging mode in the developer options. cd in command prompt to C:\Users[user]\AppData\Local\Android\sdk\platform-tools, and run adb devices. If the serial number of your android device appears, you're good to go. Then run adb logcat while executing the kivy app in your phone, and you'll get the realtime logs.
Related
i connect android studio to my phone via usb.
my android project will be work correctly when i debug it.
but when I'm clicking on apk file for installing it quickly stops and
i will receive "unfortunately has stopped" .
and there is no issue on logcat.
If you have the same project syncd on your android studio with same package name on your Android phone you will be able to debug it.
Be careful that this DOES NOT guarantee that you have the same code version on your IDE and in your device.
and there is no issue on logcat
This is highly unlikely.
Please, proceed with these comands on your prompt/bash/terminal:
adb kill-server
adb start-server
adb logcat -c
adb logcat (and press "play" button)
See logs.
I know this question was asked a lot, but going through dozens of answers none have been helpful.
I'm attempting to run a simple hello world on my Huawei Mate 9 using Android Studio 2.3.1 (The APP is 4.X Jellybean API) running on Debian (Jesse).
-I have enabled debugging options on the phone (I can see developer options)
-Installed the SDK and ADB through the Android Studio.
-Device is being detected successfully on ADB devices.*
-I have tried MTP and PTP (currently it's on PTP)
Despite all different combinations I don't see my phone ready for uploading my program.
*With android studio closed:
when I check adb it usually never finds the phone the first time (adb devices) but after i do kill-server and start-server, i get the unique phone ID the second time I run adb devices. Needless to say, should I run studio after the second time around when it detects it, the phone still does not appear.
Thanks
Try this two solutions :
1) Go to setting and than in security and enable " Unknown source " to allow installation of apps from unknown source. If its still not working try second solution.
2) This problem can be due to unsupported adb driver of you mobile model. For this Download PdaNet+ a universal adb driver downloader for all devices. It will ask to remove current driver and go for it. It will fix all the adb driver related issue.
Link : http://pdanet.co/a/
So after rigorous search, I've found the reason for incapability of finding the phone in the android select deployment target menu is due to an option within a hash code menu.
You need to dial ##2846579## (works on Huawei 7 and onwards phones) in order to find a hidden window, for me it says ProjectMenu as the activity title name, then you must pick Background Settings->Background Debug->Open then restart your phone, should you have avd,android running well on your pc and debugging options activated on your phone this is all that's needed in order to deploy your app successfully.
New to ADB and Android, so excuse my likely butchering of the terminology..
Google has an app available through their GitHub page (gps-measurement-tools) that allows you to view NMEA output in a terminal window, if you launch the app through Android Studio.
My question is now, how can I do this via the CMD and ADB, i.e. without relying on launching the app through the Android Studio? I know how to launch the app, but I don't see any output in the terminal window.
Many thanks
The output you see in Android Studio is just logcat. To reproduce without the Studio - start the app and then run logcat in the same adb shell session or adb logcat in a new window.
To see just NMEA events use the filter:
adb logcat GnssLoggerNmea:D
You have to launch the application from Android Studio but on your Android Device using ADB.
Install ADB driver for your device on your laptop/pc.
Now enable Debugging mode in your Android Device.(For this you
have to enable developer mode on your android device).
Connect android device with your laptop/pc and select usb
debugging mode on android device.
Now launch application from Android studio.
As the title says, I'm running Ubuntu (more specifically Xubuntu) and I'm trying to use my Android device to test my app in Android Studio.
Yes, I have developer mode turned on. Yes, I have USB debugging turned on. The USB configuration is set to MTP as well.
I've followed these instructions, but no dice. I did everything it said, and still nothing.
Android Studio says there is no device connected via USB (it is) when I try to run the app; lsusb in the terminal doesn't seem to list my device (Samsung Galaxy S6); I installed libmtp9 and used the command mtp-detect, but it said no device was found.
When I tried to execute "adb devices" as it says in the instructions, the terminal would tell me something along the lines of "adb failed to ACK," "daemon thread failed." I can't remember exactly because I actually just did it again, and it said the thread was successful this time (out of nowhere) and everything ended without any error. However, when I went back into Android Studio, it still doesn't list my device.
Help would be greatly appreciated. If I can't get this to work, I'll have to resort to Windows 10 again.
This is pretty simple: I'm using NetBeans on Linux with Android emulator 1.6. I have Logcat on my android phone, but the process of getting the messages to somewhere readable isn't smooth at all.
Can someone tell me how to get Logcat running on the emulator? Is there anything I can do to see debug messages other then having to copy the apk to my phone and testing it?
Thanks in advance!
You have a few options for viewing the debug log output, assuming you have the SDK installed and your command path set up correctly:
Type adb logcat. The log output from the connected device or running emulator will appear. I usually prefer adb logcat -v time to see the time stamps.
Type ddms. This launches the stand-alone version of DDMS. It has a logcat display at the bottom.
Install the ADT extension for Eclipse, and open the logcat view. (Since you're using NetBeans I assume this isn't what you want to do, but I'm mentioning it for completeness.)
In all cases, the interaction is the same whether you're using a physical device or software emulator, because the ADB daemon conceals the details. Whatever you're doing for the device is also expected to work for the emulator.
If you have a device and emulator connected simultaneously, you can use adb -e logcat for the emulator and adb -d logcat for the device. From stand-alone DDMS or Eclipse, just pick the device or emulator from the pop-up menu.
If you have setup nbandroid you can find the adb logcat viewer in netbeans under:
Window -> Output -> ADB Log
--edit
Just followed up on the post above and started using C:\Program Files (x86)\Android\android-sdk-windows\tools\ddms which is alot better then the one in netbeans.
The SDK comes with a handy tool called ddms it should be in the tools folder of the SDK.
At the moment an Emulator is running, or a mobile phone is connected to your machine it should show up in ddms and you can see all the log output in ddms.