How do i fix Blackberry App submission compatibility? - android

When submitting an Android app to the Blackberry App World for compatibility, it says my app uses features that are not compatible with current version of Blackberry Runtime for Android Apps. What should I do?

There is quite the list of unsupported features on Blackberry's site.
If they won't give you more details on what you're using that's unsupported, that list is a good starting point.
There are also some downloadable tools that can help you verify things locally and possibly give you more details on what's wrong.

Related

Android Things project status: where to get information?

I am designing a product around a NXP Pico i.MX7D SOM, which is officially supported by Android Things. I need to be able to use Google services and would like to use a pre-certified solution to cut on certification/validation costs.
The latest Android developers post about Android Things (https://android-developers.googleblog.com/2019/02/an-update-on-android-things.html) makes me wonder whether Android Things is a viable solution for production.
The FAQ at https://developer.android.com/things/faq suggests that Android Things is either a commercial solution for OEM or a toy platform to play with as a developer.
Where can I find more information about the Android Things platform?
Is there an official place to ask for such information about Android Things?

Minimal supported platform versions for xamarin.uitest

I'm currently looking into test frameworks that run UI-tests for Xamarin projects. I've narrowed it down to two options:
Xamarin.UITest
Appium
However, it's unknown what the minimal versions of iOS and Android are, which are supported in Xamarin.UITest. I've found an old form post that suggests there are indeed minimal versions. However, the answer that is given, redirects to the new Microsoft documentation which doesn't contain those versions.
Does anyone know the minimally supported versions of Android and iOS which Xamarin.UITest supports?
Edit
After the suggestion of James Lavery to contact App Center, i've got the following answer from Microsoft:
Hi There, Thanks for writing to us! Xamarin.UITest will support all version of Android and IOS, the only thing you need to check is the app which you are running in supported respective versions.
Please refer the below article the list of devices and respective versions we have
https://learn.microsoft.com/en-us/appcenter/test-cloud/devices
James Lavery has gotten the same answer!
The response I've had from Microsoft is:
Hi There, Thanks for writing to us! Xamarin.UITest will support all version of Android and IOS, the only thing you need to check is the app which you are running in supported respective versions.
Please refer the below article the list of devices and respective versions we have
https://learn.microsoft.com/en-us/appcenter/test-cloud/devices
If you have an App Center account, I suggest you contact the support team there (button at the bottom right of the portal screen). They respond pretty quickly.
If you don't have an App Center account, let me know and I'll pose the question for you.

Does Android OS for Mobile Phones share the same code base with Android Things?

Do they share the code base and version number?
Does Google release the same piece of code for both and just use different flags for mobile phones and Android Things?
This may be a strange question, as I am particularly interested in Android Application Framework.
Do they share the code base and version number?
From an Android application developers's view point there is not much difference between Android OS and Android Things. I.e. you can successfully deploy an Android app developed for Android (OS version 7+) on a platform running Android Things.
Does Google release the same piece of code for both and just use different flags for mobile phones and Android Things?
No "flags" at all. It's rather a matter of adding new system (C/C++/Java) services specific to the supported platforms with its underlying hardware or removing the old ones, needed for mobile devices and not related to embedded systems. Actually Android Things is pretty much an inheritor of Brillo.
As a quick look consider the following overview of Android Things OS to see how it differs from Android.
With regards to the Android Application Framework, you can expect the vast majority of APIs to be the same on Android phones and Android Things. Specifically, this page details the APIs that are not available:
CalendarContract
ContactsContract
DocumentsContract
DownloadManager
MediaStore
Settings
Telephony
UserDictionary
VoicemailContract
Additionally, a few Google Play Service APIs are not available.
In terms of whether Google releases "the same piece of code for both" the answer is a bit complicated. Android's framework is a combination of a lot of files, some of which only make sense for specific form factors. Different build configurations state what files to include, which to not include, and how exactly to build the correct system image.

Mixare - How to in built into Android app

I was wondering, for integrating MIXARE into my Android app. I came across the post
http://damianflannery.wordpress.com/2011/06/13/integrate-zxing-barcode-scanner-into-your-android-app-natively-using-eclipse/
but i got a question that is, do my phone or tablet need to be installed with MIXARE ? or i will be just launching the functions of mixare in my app ?
Apologies if you guys don't quite understand my question.
Nevertheless i still hope to have some answers.
Thanks.
The instructions given do NOT require that other software be installed on the device - the library referred to is an android library which is installed on your development machine are including in your application as part of the distribution (i.e in the APK).
If you choose this route be sure to test on some devices which DO have the other app installed because if you get the intent filters even slightly wrong it will fail in this case.
However this is NOT the best solution: there are several different reasons why it is better to install the Mixare application and use the intent system to access it from your code, possibly the best of these is that it allows the user to keep the latest version of the external app updated. The author of your link clearly indicates that the only reason he chose this path was because within his enterprise solution no access to the play store was permitted.

Now that Android 4.0 is out, is Multi Touch possible in android emulator?

There are similar questions like this uptill Android 2.3 sdk on Stackoverflow. But as per the answers it was not supported back then. I have even seen a feature request ticket for it with Google but it is still pending!
With the recent release of 4.0 sdk, does any one know if it is now possible to simulate the multi-touch feature in the emulator? If yes, please do information on how to do it.
Thanks in advance!
Multitouch in the emulator is still unsupported and has not been announced as a planned feature. This would most likely come as an update to the SDK tools and not the operating system itself so the Android Tools recent changes feed is probably the best place to follow for any news on this feature.

Categories

Resources