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.
Related
I've just installed the latest Android Studio (v3.1.2) with all required things to run some emulated Android firmware and test an application in it. I tried to attach my webcam to an emulated phone to simulate its own inbuilt camera, following guides you can find around (and on this site as well), doing everything as it should be done - yet none of all apps I tested were able to use it. They were just spitting some "Camera encountered an issue" kind of errors.
Here is a relevant command's output:
K:\Android\SDK\emulator\emulator -webcam-list -avd
emulator: WARNING: enumerateDevices: Webcam device '\\\usb#vid_0ac8&pid_3500&mi_00#6&197c435a&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global' does not support required dimensions.
So, apparently current version of AVD deems my webcam as "unworthy". I have a budget A4-Tech PK-910H device alright, yet it's capable of 2MP video stream, does even better when it comes to photos. How it can be possibly not enough? Why does it even care, and why it didnt' before?
I used a very similar setup a year ago, and everything worked like a charm. Even more, I used MUCH worse webcam back then without any issues (this old camera is still with me, and it isn't accepted by AVD the same way; that's why I actually bought the new one, assuming 2MP just must be enough for everything). Nothing was changed since that day, except of Studio's and AVD's versions, so I'm pretty sure those are culprits.
Is it possible to resolve it without reinstalling everything from some old obsolete Studio's package? May be I can somehow use an older AVD emulator in parallel to the newest one?
I was able to achieve what I need by installing Android Studio 2.3 with an older version of AVD emulator (25.3). I got the package from this site.
Ironically, my new webcam still didn't work with it, though in a different manner. It at least was shown as connected, and in the app I need to test, instead of spitting an error, there was just black screen when the app tried to get feed from it. I suppose this may be due to the fact all webcams are connected using some BGR4 pixel format. May be it's not supported by this model.
The old camera still worked like a charm, so I'm good for now. A rotten egg flies in direction of Google, for meddling with a perfectly working feature for no reason, breaking it as a result.
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.
Hi I'm trying to compile a Titanium Android app directly on my Nexus 7 (2013, SDK 4.3) device but I can't see any 'Titanium on Android Device' option in the Run Configurations.
My device is in Developer mode, connected to the USB, detected by Android File Transfer (Mac OS X 10.9, Titanium 3.1.4), detected by adb...
I tried to restart adb, restart Titanium, plug and unplug the device, but I still cannot see the option.
I also tested all this with Titanium 3.1.3, with no success.
I have no clue of what's happening :/ any help would be appreciated. thanks
It may sound stupid, but my friend had similar problems with his Nexus and he changed the USB slot to which he plugged his device and it worked.
Try using a different cable. Most cables are only able to load the device, somehow. Not every micro-USB-cable is capable of sending data, correctly.
Again a reason why I don´t like to work in the android environment. No one checks whether software and hardware is working the way it´s supposed to. That´s why I love Apples restrictive "closed" system. No 1000 viruses and other crap.
Well, that was a bit confusing but I finally found such option inside a Project Explorer menu...
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...
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.