I'm using to make automatic build and releases of my android library.
One of the steps is, of course, automated testing. Since I can, I run the tests on a real device.
The issue is, I have to unplug then re-plug my device between every launch otherwise I get an error saying that my device is either not found or offline.
So the drivers are all fine since it's working the first time, but I can't figure out what's happening after that.
I'd love to be able to build and test release candidate everytime I push on develop but this is preventing me from doing it properly ;(
I tried re-installing everything with no changes. Has anyone else encountered the same issue or have a fix to this behaviour?
Thanks a lot!
Related
No emulators are currently running
Wrote a program in Kotlin. Everything was fine, everything worked. I turned on my laptop a week later. Launched Android Studio/AS/. The code opens fine. Only emulators do not display the phone. Writes that there are no working emulators. No reboots of either the system or the AS, updates with a full restart of the program help. I want to delete the device, Device Manager/DM/ also does not allow it, because DM says that it is now working. I can’t find any AVD services. In the Task Manager, I can’t find anything either.
Dear gurus advise what to do.
The next step is to reinstall AS. I just can’t reinstall AS every time the emulator freezes.
Thanks in advance.
By the way, as I have no choice I reinstall the AS that helps.
I'm not really sure how to word this.For some reason when I install an app that I'm working on from Android Studio it runs very slow (when an option is pressed it takes 10-20 seconds to register). But if I install the app from either my coworkers Android studio or adb from my own machine it works fine.
My specs are:
OS: Windows 10
Android Studio Version: 3.0.1
Phone OS: Android API 24
It was working fine this morning, but during the course of the day, something has happened. Has anyone run into this sort of problem before?
I'm using a Samsung Galaxy S8 physical device. I have tried a factory reset on the phone which worked for one install after I changed some things I'm back where I started. I have also restarted both the machine and phone multiple times. I'm at a loss as to what is going on. If you guys need any more info let me know. Also INSTANT RUN IS NOT ON.
EDIT: I'm at a total loss as to why this is happening. I've tried everything from restoring the phone, reinstalling Android Studio, changing wires, changing settings, but nothing is working. If anyone has a suggestion I will gladly try anything.
I've finally found a solid solution to my problem. I'm positive now that something went wrong with m usb drivers for windows 10. I went to this page https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/windows-10-slow-usb-30-transfer-speeds/a5e1eebb-74bb-4777-8902-5131f3e8ec3e and I completed the steps in method 1 and that did the trick for me. it took a while to find this out, but hopefully, someone else will find this helpful.
Have you compared your yesterday build and today build which is making your app slow. Any Significant change in code?
Have you set up breakpoints or similar? Some debugging options can significantly slow the app down at runtime. When this happens, if you disconnect the phone from ADB - e.g. pull out the cable - and it speeds up again, then it's likely related to your debug connection to that particular instance of Android Studio.
So I'm using an Android emulator (the stock one) to test out my react native application I'm building.
I can load my app on the emulator using react-native run-android and then my app loads fine. However I can only ever do pretty much one interaction, such as pressing a link, after that my app just doesn't respond and I have to restart my react packager to get it to reload. Are there any reasons why this might be happening and how this can be resolved please, it's making it super hard to develop any project.
There is no strenuous code in place and runs fine on my IOS emulator.
I've been having similar issues, especially after rebooting the emulator. I've found that the best solution is to reset the emulator and check the wipe user data box. You then need to wait until the emulator is fully booted before starting the packager. This works for me most of the time in 0.14, but isn't foolproof. I would also check the chrome debugger and make sure there aren't any IOS exclusive parts of the code causing issues, but I'm guessing you've tried that already.
I'm using Cloudpebble to develop a watchface for myself. Everything compiles well and I've not had troubles sending the face to my watch until now.
After compiling the watchface and linking to the phone, it returns an error of "Installation failed. Check your phone for details." However, the phone does not shed any light on what these details might be.
I've checked the usual suspects such as full watch slots and inability to connect to phone, but those were not issues in my case and I'm rather stumped as to what the problem might be. Any help would be greatly appreciated.
Pebble App Version:
2.1.0-beta9 2.1 (Android)
Watch Firmware: 2.7 2.8
Watchface Source: GitHub
UPDATE 11/20:
I didn't mention before that the phone app would crash often when attempting to load my watchface on the watch because I chalked it up to beta software. Today brought watch firmware 2.8 and phone app 2.1 proper, and while the phone app no longer crashes, the mysterious error continues without additional information on the phone.
The answer to my particular issue, as it turns out, was that I had unused fonts. It's not a very obvious problem, so I hope this helps others out.
The main issue really was poor error reporting from cloudpebble due to the lack of error clarification returned from the pebble app to cloudpebble.
I have opened an issue on the cloudpebble github (that's where I found the answer) so if any further developments happen, they'll more than likely be there.
I found that the app had to be on a specific page for it to properly install on the pebble. I found this to be true if I installed on the terminal using the Pebble commands or using the web IDE CloudPebble.
The app has to be on the "My Pebble" scene/activity. Make sure when you attempt to install an app to Pebble that you are on that scene/activity regardless if you are installing using the web IDE or the command line.
I use IntelliJ IDEA to write Android apps, and use the DDMS Windows application to view the Android logs (separate from the IDE). It works fine, but after a seemingly random period of time, the logs vanish, except for one line of log, which gets overwritten with incoming logs. I have to shut it down and restart it, which combined with the delays of deploying an app to a device over ADB to debug and test is pretty tiresome.
Is this a known issue with DDMS? Is there anything I can do to make it work consistently without breaking itself?
Are there any other Android log viewing applications for Windows that work better? I'm not very fond of the IntelliJ IDEA one. My favourite is actually CatLog on Android itself, but on a small-screen device it's not a great experience.
It's not about the time, but number of lines being recorded. As Dave C said in the comment, just clear the log and it will be fine
Have you tried looking at "Why doesn't LogCat show anything in my Android?"? The top voted answer may solve your problem