I recently bought a Moto X and was following the online instructions for setting it up to test my android code. I installed the USB drivers and got to the place where it tells me that the phone is unlockable. I quickly returned the phone at this point before activating it and subsequently porting my number over.
Can I test code on the Moto X specifically even if it is NOT bootloader unlockable? Is this the case for all android devices?
Unfortunately I don't know anyone that is a developer or even anyone that owns a Droid phone that I could experiment with.
You do not need to unlock bootloader to test your Android applications. Please refer to Using Hardware Devices for more information regarding setting up any Android device for testing. Following is the relevant part quoted for your information:
You can use any Android-powered device as an environment for running, debugging, and testing your applications. The tools included in the SDK make it easy to install and run your application on the device each time you compile.
This is a general answer, not specific to Moto X. I do not see any reason why it should not apply to Moto X.
Related
Trying to get the ARCore sample hello_ar_java running on an Xperia XA1 device. Seems to be going ok and it recognises that I need to install latest ARCore on the phone. All it gives me though is item not found and a retry button.
Anybody know what I'm missing?
I have "implementation 'com.google.ar:core:1.0.0'" in the dependencies, use of the feature in the manifest and I believe there to be a configuration file for the XA1 too so I'm under the impression it's a supported device.
Only been poking at Android apps for about a week. My money is on something really nooby!
Any ideas?
Sony Xperia XA1 has no hardware gyroscope what is unacceptable when using ARCore. Instead of a real one, Xperia XA1 has a virtual gyroscope. So, it'll never be on the list of supported devices, and if so, you can't install ARCore app on it.
Check this thread on a forum.
OK so I am trying out Genymotion for testing my app, so that I can reproduce the errors that my users are telling me they experience with my app, which leads me to fixing the issues. I guess that is the main reason for using Genymotion.
Real life example:
A guy says: "I'm using a Moto X (2013) on Android 5.1.1 and I can't do X with your app.
Me: Looks at Genymotions list of virtual devices and can't find neither the brand of phone nor the android system. I can only find android 5.1.0.
Does this mean that I Genymotion just doesn't have what I need, or is it because one of the other options are just as good? I really don't know. What am I missing?
Any help would be appreciated.
Brian
An emulator, be it the default android emulator or Genymotion or any other emulator will not be able to replicate a real physical device to the complete extent.
The devices available on Genymotion are just templates to recreate the device with values such as RAM, Screen size etc. You could try creating a custom device by using the values for Moto X.
One possible idea would be to get the stacktrace from your friend and see what's going on. The best way to do that would be to integrate crash reporting system like Crashyltics. You will automatically get crash reports in your fabric dashboard.
I developed my first Android app targeting KitKat ( 4-4-2) with minimum SDK being set to 4.1.2 (JellyBean)
Beside standards UI stuff, this apps is dealing with device sensors end using java multithreading ( standard way, no fancy stuff)
it's now running fine on Nexus5 (kitkat) and Wiko5 ( JellyBean ), however I sent the .apk to a friend for testing on Sony Xperia Z and it's crashing... he si going to send me the device for debugging over tehre...
as I am used to develop w iOS ( one platform, one constructor ) , I'd to know if there is anything to take care before developing for multiple Android devices... additional APIs , should I test locally all these platforms ?
on windows
try
adb logcat -v time > D:\log.txt
then open the log.txt by some editer like notepad++, search 'fatal' and lookup crash stack, you can find the reason app crashed. Or Please post it on, so we can help.
In an ideal world, the Xperia Z should be able to run the app as long as it has the required OS and the sensors your are trying to access. So this looks like something device specific(esp. since it works on your other jellybean device.).
So the way forward would be to look at the logcats.
Also, instead of waiting for the device to reach you, just ask for the logcats - the logs would be the best way to further debug this issue.
Ask your friend to connect the USB to a machine and do the following(assuming android sdk and platform tools are downloaded)
adb logcat
Better still - copy logs to a text file
adb logcat > log.txt
I have some problems with SmartWatch2:
Sony Xperia Z1:
Accessory Version:1.0.B.0.60;
Host Application Version:1.0.12;
Smart connect: 5.4.8.
Verizon Samsung galaxy note 2:
Smart connect: 5.4.8.
My two apps do not show up in the installed application list in Sony Smart Connect. I really don't know what to do!
Does anyone have problems like this and solved it?
Many thanks.
Update:
I use "Sony add-on SDK 2.0" and SmartExtensionAPI, SmartExtensionUtils from this pack as linked libraries in my apps. Also "Sony add-on SDK 2.0" marked as a target platform for apps.
Update 2:
Another user with SmartWatch 2 write me that my app didn't listed on his phone smart connect app list.
I assume that you have tried the extension yourself on real HW and it works for you? Couple things you can tell them to try:
Uninstall the extension and reinstall it.
Unpair the bluetooth connection to SW2 and re-pair it.
Make sure:
Your SmartWatch2 extension gives the correct dimensions about itself
(i.e. the dimensions of the SmartWatch2 screen)
Your application maps correctly those dimensions, and transfers the control to your
extension
That was in case your extension never appeared on the SmartWatch2 screen. If it did, but does no more, restarting your phone normally helps. In more difficult cases, uninstall the SmartWatch2 app from your phone (it will be reinstalled once you pair your SmartWatch2 again).
I have a similarly problem but related to the development process. I'm working on a control extension app for SW2, and I was able to compile the code and see the app on the SmartConnect Installed Apps and then test it in the real device (i.e. SmartWatch 2).
After a couple of iterations on Edit code > Compile > Test, the app stops to show on the SmartConnect App list and on the SmartWatch 2 too.
I don't understand why this happens and its not clear what is the solution for this. Rebooting, uninstall, etc. Its like a random try&error solution, and leads to o much time lost on getting the app running again.
Sony SDK Team should give one word on this...
My droid works fine. The other two droids I've tried are never recognized by adb and don't debug. Debugging is turned on with all 3 of them.
What's the problem?
To test that you have the correct drivers installed (on windows) or have everything setup right (on os x or linux):
Open a command prompt/terminal
Navigate to the tools folder of the android sdk
run "adb devices" (no quotes)
If all is well it will list all the device names on a new line. If something is wrong with your setup you will see question marks a line
I'm guessing you've seen this already but if not take a look at the instructions for setting up a devices for development.
Just as a side note, I'm not sure you can have 3 of the exact same device working at the same time (I assume you meant you have 3 Droids). Might only work with 3 distinctly different devices.
Did you remember to enable debugging in the phone settings ?
(in Settings => Applications => Development )
what do you mean by droid? Motorola Droid, HTC Droid or are you using droid to just mean you have three different models of android phone?
If the latter there is some configuration necessary - for my HTC Desire I had to setup some drivers: http://myhtcdesire.com/tutorials/how-to-install-the-adb-driver-on-windows