, peter gottlieb gottlieb...@gmail.comwrote:
I finally got the adb to recognize my old Experia, after I made sure the
USB debugging was turned on. The new Experia doesn't seem to have that
option available or any other Development options. I will have to talk to
Sony support about
UTC+4, peter gottlieb wrote:
I'm not sure what you mean by a response from ADB. I can debug from
Eclipse on the virtual device, but Eclipse android plug in won't even
recognize the hardware phone.
On Fri, Nov 29, 2013 at 8:11 AM, Kristopher Micinski krismi...@gmail.com
wrote:
Can you
:
On Fri, Nov 29, 2013 at 12:45 AM, peter gottlieb gottlieb...@gmail.comwrote:
The windows 7 has worked in the past, but doesn't work now. The windows
8 setup hasn't been used for this purpose before. I have made sure to set
debug = true in the manifest, and that the phones (a new Sony Xperia
On Fri, Nov 29, 2013 at 10:52 AM, peter gottlieb gottlieb...@gmail.comwrote:
Bad guess. I clearly stated that the windows 7 setup had already worked
with the Sony Erickson, but now doesn't. For all PC-phone interactions
(browse files on the phone from the PC, update phone software from
be able to see the phone from PC connect.
On Fri, Nov 29, 2013 at 9:47 AM, Kristopher Micinski krismicin...@gmail.com
wrote:
I mean, if you type in adb devices do you get any output to indicate
that ADB can find your device?
Kris
On Fri, Nov 29, 2013 at 11:27 AM, peter gottlieb gottlieb
The common practice is to test an app on an emulator (such as what one gets
from the Eclipse ADT plug-in) and then on an attached phone. I have 9 apps
on Google Play that were developed in this manner. Now I can no longer get
the Eclipse environment to recognize the attached phone. I have
I have gone through several stages in the development of an app, compiling
and executing just fine. After my latest increment of code the app builds
fine, but crashes with the following message in the Log:
unable to instantiate ActivityComponentinfo {}:
java.lang.NullPointerException.
My
7 matches
Mail list logo
