As the most of you will know Android Emulators for >3.x don't support Renderscript. Now I found an Android Player called Bluestacks (tge most of you will know it I think). So I wanted to ask, if it's just me or does Bluestacks also not support Renderscript.
Regards,
Ahmad
Google has published a compatibility library for Renderscript, which allows you to use it starting from Android 2.2 (API8).
This means that Renderscript could run even on bluestacks if it is still android 2.3.
The disadvantage is that it uses the CPU unless the OS version is 4.3 and above.
more information about it is available on the android developers blog, here
It is supposed to support RenderScript. As RenderScript is a part of android framework, all renderscript openGLES operations should be forwarded to host stack eventually.
According to the Bluestacks help forum Bluestacks is equivalent to Android 2.3.4 which doesn't support Renderscript as far as I know.
Actually the emulator images for Ice Cream Sandwich (4.0.x) and JellyBean (4.1.x) which come with the Android SDK does support Renderscript. The Honeycomb (3.0, 3.1, 3.2) emulator images do not.
Related
Which minimum android version is supported by flutter?
Do some plugins have any effect on which version is not supported?
I tried to run my flutter app on an android emulator, but with the version android 16 it doesn't work and the app crashes. Do I have to change the compile version in some config files or why doesn't it work?
Flutter support 16. But to run app on Android emulator, use over 19.
https://github.com/flutter/flutter/issues/11094
https://github.com/flutter/flutter/issues/9108
https://github.com/flutter/flutter/issues/8610
From Flutters FAQ
flutter.dev/docs/resources/faq#what-devices-and-os-versions-does-flutter-run-on
Mobile operating systems: Android Jelly Bean, v16, 4.1.x or newer, and
iOS 8 or newer.
Mobile hardware: iOS devices (iPhone 4S or newer) and ARM Android
devices.
Note Flutter currently does not support building for x86 Android
(issue #9253) directly, however apps built for ARMv7 or ARM64 run fine
(via ARM emulation) on many x86 Android devices.
We support developing Flutter apps with Android and iOS devices, as
well as with Android emulators and the iOS simulator.
We test on a variety of low-end to high-end phones but we don’t yet
have an official device compatibility guarantee.
We believe Flutter works well on tablets. We do not currently
implement all of the tablet-specific adaptations recommended by
Material Design, though we are planning further investment in this
area
The answer to this question also, partly, needs to take into consideration what parts of Android you want to take advantage of in your application. The question of what min version Flutter supports has been answered here a couple of times so I won't answer that, but the Android support libraries will also need specific min versions.
If you plan to use plugins of any kind then you will probably hit multiple issues if your min version is too low. Do you need Firebase? Do you need specific camera functions?
Google also just announced required bumps for min versions with regards to Google Play that you should review.
My advice is to follow documentation, analytics and best practices to determine what you "true" min version should be.
The Flutter documentation has this answer to Android and iOS. Now it says that support: Android Jelly Bean, v16, 4.1.x or newer, and iOS 8 or newer. However, this information can change according to the new Flutter version. By this reason, it is better that you review the next link:
https://flutter.dev/docs/resources/faq#what-devices-and-os-versions-does-flutter-run-on
Furthermore, it would be best if you analyzed the plugins because they could need higher versions of Android and iOS.
This answer can be useful :
Devices and OS versions on which Flutter runs
Mobile operating systems: Android Jelly Bean, v16, 4.1.x or newer, and iOS 8 or newer.
Mobile hardware: iOS devices (iPhone 4S or newer) and ARM Android devices.
You can learn more here
I need to emulate Android device (Samsung Tab 2) with version 4.0.3, but after choosing it in Android Virtual Device Manager and running it I get info in settings that it is a 4.0.4 version.
I need to run my web app written in html5 to reproduce some bugs.
Any idea about it?
The problem is that the emulator Android versions only correspond with specific versions from each API level. 4.0.3 and 4.0.4 are both in API level 15, so the emulator is only made available for Android 4.0.4. There is no Android 4.0.3 emulator; you'd have to find the system image for that or build it yourself.
I'm following a tutorial that utilizes the Motorola Java ME sdk for device profile customization, as it uses quite a user-friendly UI, but this SDK seems to no longer exist. Can anyone suggest an alternative?
I'm using netbeans as my IDE.
Currently you can't find any Motorola emulator for Java ME. Because they fully moved to Android. So better you can try with some other emulator for Java ME.
I have installed android tools and eclipse successfully (making the hello World and hello widget examples) and have run these successfully on the Xperia X10 add-on that I downloaded from the developer site of SE.
However, my phone is running the updated Android 2.1, and any apps that I make will either have to run on 1.6, or will not be able to be tested on the Xperia X10 during development without moving it to my physical phone.
I have contacted Sony and they told me there is no add-on with 2.1 on it. And that is all they would say.
My Question:
Is there anyone out there who has developed for this phone, who knows what to do? Do I somehow run the SE update tool on the virtual phone to upgrade the OS of the image? Or am I missing something much more obvious?
As of April 2011, this is (an estimate of) Android usage share:
That's 3.5% for Android 1.6 and 2.7% for Android 1.5. As time goes by, those percentages will only decrease.
Just develop for 2.1.
Why do you prefer to use the emulator, anyway? Most Android devs (myself included) have found that the emulator is painfully slow, and it's just plain easier to plug in a real phone and test on that.
You can use the adb for getting your phone in debug mode.
Or you can just install your APKs via OTA or via USB in your physical phone.
Or you could just develop on 2.1 knowing that almost everything will work. I don't get the problem, really.
I started developing with Titanium and now I really stuck on one part.
I downloaded the Adroid SDK and added the path to Titanium:
/Users/michael/Downloads/android-sdk-mac_86/
I can open e.g. Kitchen Sink in the iPhone Simulator without problems, but when I want to open it in Android then my screen looks like this: Screenshot
Why is down there all the time, even after 2 hours of waiting, the label "loading..." ?
some great advice given here - helped me out.
Switching to TRACE will probably show that Android SDK Platform 1.6 and API 4 is missing.
More info here
1) You can install Android SDK 1.6 (run tools/android from your Android SDK folder and download the older SDK 1.6 from the Google Repository),
and Titanium will detect Android SDK
2) As for Android SDK 2.2, adb moved to platform-tools folder, so you will have to create a link in [your-android-sdk-folder]/tools e.g. :
ln -s ../platform-tools/adb
(full instructions for non-linux here : http://guides.appcelerator.com/en/getting_started.html)
Finally, in the Titanium Test&Package/Run emulator window, you will have the choice between Android SDK 1.6 and 2.2
Try to open your Android_SDK_Dir/tools, run file android to create a new Android Virtual Device. After that, open your Titanium again. Maybe this will solve your issue.
Take a look at your image. Value of SDK listbox is "...loading...". This means you Titanium cannot determine which Android Virtual Device is. So, as I said, try to create new Android Virtual Device first.
having the same issue - have you found a workaround?
found out that after downloading the android sdk - there are other components to be downloaded, which is different from previous versions. Also found some implication that loading the android emulator prior to launching the app from titanium may yield better results.
check the android docs for updating the sdk via the avd manager
load the emulator first video:
http://vimeo.com/10866226
Try setting the Filter from "Info" to "Trace" that may illuminate things.
Most commonly, you may not have the right platforms installed. Just install all of them if that's the case.
add a blank folder android-7 in android/platforms ..n restart titanium ..it worked for me on ubuntu