I'm having some problem with developing an android app. Everything runs smooth until a while ago. Lately I've been debugging on a couple of different physical devices and everything works great on all of them. The other day when I tried to run the application in the emulator I got an error:
ERROR/JNIHelp(313): Native registration unable to find class 'android/debug/JNITest'.
Is this something to worry about? The app is supposed to be released today on the market but it doesn't feel right to release something that wont even load in the emulator. Since the app works seemingly flawless on all physical devices I've tested it might not be a problem?
Try -wipe-data ... if it doesn't work, delete the emulator images .. and if that doesn't work re-install the SDK .. No other fancy solution, afaik.
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.
I am developing an Android App with Eclipse and the Android SDK on my mac and everything works fine. I am debugging on a Samsung Galaxy S5.
And I got the problem, that as soon as I add google-play-services_lib as library to my Android project and try to debug it again, my Eclipse uses every percent of my processor it gets and gets slower and slower till it freezes. I have to kill it on the commandline, otherwise it remains in this state and I can not work on.
Anyone faced the same problem? I could really need some help, because I don't know, how to solve that problem.
Kind regards
rholtermann
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!
Emulator --- Device
Hey people. I'm not very experienced in Android development, so I would like to know what I have to expect.
I wrote an app of about 1000 lines of code, which is running perfectly fine in the emulator. So what will it be like when I install it on a physical device? Ain't got one here at the moment, but I will get my hands on one on the next days. Will there be a bunch of nasty errors? Just some design stuff? Errors, that cant be reproduced in the emulator?
Thanks in advance
EnflamedSoul
Note: emulator runs the real Android code. It emulates ARM device and runs the whole stack on top: linux kernel, libs, android code. It is the same as device sans some hardware (camera, mobile network stuff, gps) and much slower.
So what will it be like when I install it on a physical device?
Will there be a bunch of nasty errors?
No problems really. It should work ok.
Just some design stuff?
If you set your emulator to the same resolution and pixel density of your device, then it should look identical.
Errors, that cant be reproduced in the emulator?
There ares some thing that you can not do in emulator: primarily make calls and use camera. Otherwise emulator behaves like a plain phone.
My Android apps have all been very simple, but I have really only had to make small changes to their layouts when I tried them on my phone. Over-all, the process of moving to the phone was a rather painless one.
I had a code that took 4 minutes on the emulator to complete, and on the real device it is just 10 seconds.