I'm developin with the google's add-on package com.android.future.usb to communicate with a USB accessory on Android 2.3.5 the app is designed to run specifically on Samsung Galaxy y ,
My problem is that the phone is refusing to install the app, i added the uses-library tag in the .xml, i went through the tutorial on develop.android.com...
IS there a way to get past this error,missing_shared_library, from my understanding it means that the phone doesn't include this shared library specifically,
and since the added external jar file from the google add on lib to my project wouldn't be included in the .apk file that's going to be installed on the Android device, Is there any way to communicate with USB on that device ?!!!...
Did you take care of the minor difference because of using the Add On?
http://developer.android.com/guide/topics/usb/accessory.html#usage
Guess this is the same problem as described here: USB Accessory API on Samsung Galaxy S2 Android There is an answer by Naresh Noby which sounds promising but I couldn't test it so far since I'm lacking the device. I would be very interested to hear the result though.
Related
I am developing a multicasting application and I need to know if multicasting is enabled on the nexus 5x or on the 6p. I currently have the nexus 5 and it is disabled.
Ref: https://code.google.com/p/android/issues/detail?id=51195
Rooting and recompiling the kernel to enable multicasting isn't an option so I will be purchasing a new device to test with. I would like to use a nexus product, however I need to know if it is enabled.
Could someone who owns one please check if "/proc/net/igmp" exists? any file manager application will work. Sorry, I know it's a simple request. I've googled it, called google support, and looked through an emulator's files all without an answer.
Also If they don't support it, could someone please recommend a device that does support multicasting?
Thanks!
I do have a Nexus 5X with Android 6.
ls /proc/net/ig* shows:
igmp6
I also have an old ASUS K010 tablet which have both igmp and igmp6.
I tried multicast using GStreamer in Android. Both work, just make sure you have the right permissions.
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.
How do i deploy an NBAndroid app (by directly moving the .apk file or else compiling straight from NetBeans?) onto a connected tablet (HP Touch that i just put CyanogenMod ICS onto)? I connect it to my computer and it isnt recognised (like WebOS was) but Android ICS was installed fine. Do i need to use the bootloader to do this? I had a quick google and Stack search but could only see stuff relevant to using the emulator, and thought id probably get an answer here quicker.
Edit: this is the same question as this How to deploy android application to a device? which i discovered afterwards.
If the Tablet is not recogniced (have this problem at work, too, even with stock OS) maybe give it a try syncing it via a dropbox folder. Its the best bet for me, so far.
i found how to connect to a device via here
How can I connect to Android with ADB over TCP?
using this method you can get the .apk on the device without using dropbox
But the dropbox method is easier, even in development.
I am looking generally in to Android development.
I keep seeing information on root however I am unclear how this relates to general android app development.
I understand that there is an emulator however when I get to actually test the software on a phone does that phone have to be a rooted device or is this only required if you wish to edit the core features of the os?
Finally are there are any development disadvantages to rooting the device such as that is no longer behaves like other android phones I may deploy too?
Thank you
You don't need root to develop for Android.
The easiest setup is to run Eclipse with the Android Development Tools installed. Then, you can debug your application in the emulator, or register your phone with the SDK and debug directly on your phone. The only thing you need to do on your phone is check the development mode under Settings -> Applications
I can understand the allure of having a rooted device, but I can't really see a reason for changing the bootloader or os binaries. You can, however, change most of the default applications (including the Home application) with other applications available on the Market. For instance, OpenHome is about $5 and allows you to replace the home app, add themes, and replace many of the core apps (e.g. clock).
Rooting is only required, if you want to play around with advanced features or update your firmware, etc.
If you develop your software using the Android SDK you will be able to use it on your phone regularly (as long as you have the corresponding version). No rooting needed.
I have never heard of any problems according to your concerns. But I cannot deny that there are none. Though I personally don't expect that there are any problems with rooted phones.
On the Nexus S running Android 2.3, the /data folder is not visible in the DDMS File Explorer or the ADB shell, but it is visible in the emulator. This occurred with debug turned on in both the manifest and on the phone. I confirmed that debug mode was properly enabled by successfully stepping through the app using breakpoints and also by receiving messages from logcat.
Not being able to see the /data folder means that you will not be able to get your application's private data.