I’ve been using Android Studio under Win 10 for ages with no problems. Within the last couple of eras, I’ve started to encounter a odd difficulty: my app won’t install and run on my Android phone. The app body-builds successfully, and my phone is connected by USB to my Win 10 computer. The telephone has USB debugging enabled and is registered as connected when ranging ‘adb devices’. When I select ‘Run’ in Android Studio, then~ 50% of the time it pictures an installation fault,~ 40% of the time the app appears to install actually hasn’t( the previous copy of the app is still on the phone) and~ 10% of the time the station labours( but app doesn’t launch automatically despite that specifying being permitted in AS ).
I have 😛 TAGEND Rebooted telephone, unplugged and reconnected via USB Updated AS with the most recent developments and greatest revises Restarted Windows and AS Invalidated and restarted
and several other nips to try to get things driving again. To emphasise: this is after at the least a couple of years of developing this same app in AS, connected via USB to this same phone. What’s extremely baffling is to do the exactly same thing( selecting Run, successful build, trying to run on target invention) and get different results as described above: some station mistakes, some silent flops( app appears to have installed but hasn’t) and the periodic success.
A possible clue is a build send about the emulator on port 5556 being undone. But I am selecting my USB-connected telephone as the specific objectives maneuver( as I have done for the past two years ). To is ensured, I uninstalled the emulator in SDK Manager, but the content still appears.
Anyone else been having similar troubles or have any suggestions for a stick?
Read more: reddit.com