I'm currently developing an app for Android Automotive. It's works well on the default simulator but to match to the reality I'd like to change screen orientation. When I go to Virtual Device Configuration and I edit the Automotive hardware, no system image are available.
Also, I get the following error message : "No System Images available. Are you connected to the Internet?"
Therefore, System images are available for all other hardware.
Am I constrained to use the only one hardware proposed ?
I'm using Android 12L (Sv2) api level 32.
Thanks
Related
When I check the device camera parameter IsVideoSnapshotSupported, it is set to false despite my device seemingly supporting this functionality. This setting is used to detect if a photo can be taken while the device is recording a video. My device can natively do this, and I can successfully take a photo while recording within my app if I just ignore the IsVideoSnapshotSupported value.
I don't like the idea of blindly assuming the feature is supported by all devices using my app, but I am not able to determine why the value of this parameter is false. The only device I have tested is a Samsung Galaxy S4 running Android version 5.0.1. The application is being built using Xamarin. The app is built on API 15.
This link lists the supported Android devices that can cast their screen over a Chromecast dongle onto a bigger display. Why aren't other devices like Moto X or E present on the list (both on version 4.4.4 as per the requirement) ? I observed that the "Cast screen" option appears under Settings -> Display on these devices. But it doesnt work.
Are there any hardware requirements for any device to support screen casting?
Thanks in advance!
The Cast Screen feature is currently just in beta. Only a few select devices - like the Nexus 5 - are supported at this time, but this list will be expanded later on. Maybe at some point all Android devices will be supported.
Its all fake no need any hardware. Cast screen works by some system software module which might be missing. some devices gets updated with including cast screen function.
In Google play (app market), if an application is not compatible to your device (for some reason, say small screen size, etc). Then it is not even shown in the list.
Now, as an app developer I never want to unintentionally add a limitation in my app that forbids it from a range of devices.
So, while developing how can I make sure that the application will be able to run on atleast the type of devices that I intend.
Also, right now I'm developing an app & testing it in on my phone with version 2.3.5. And every now & then Google changes some method names & flags.
For newer android releases, I CAN test it on emulator, but testing it on phone/tabs/etc. is a different thing.
Please suggest.
how can I make sure that the application will be able to run on atleast the type of devices that I intend.
In manifest file you can mention, which type of device you want to run your app. And for testing you can create emulators for different devices to test your app. Try to make app UI such that it runs on all devices.
Google changes some method names & flags
Whenever Android changes any thing it will always be upward compatible means if you have made app for 2.2 it will run on 2.2 and above (screen size or resolution is other thing)
Regarding UI see my answer here
Layout for 720*1280 devices
By default apps will be available to as wide a range of users as possible.
There are certain limitations you can define in your manifest file, such as not being available on small screen sizes, but they are at your discretion.
The only limitation Google imposes on you is that any user who has a lower Android version than your minimum SDK version cannot see your app. To get around this, you can either design the app for lower SDK versions (I believe building for 2.2 and up gives you access to about 95% of the user base) or maintain multiple versions of the APK.
Read this. It will really help. Next Eclipse will help you a lot, firstly you can define what you wish to support (screen sizes and hardware requirements or even if they're not necessary but may be used) in the manifest. You can run a version check and implement APIs dependent on which version of Android you're running on. That's personally what I do, I check the API level and if it's greater than or equal to the API I wish to run I run it, otherwise I attempt to find compatible code (often using the compatibility library) or alternatively drop support for that feature, for example JellyBean notifications there's not really any work around for expanded notifications but I can use the NotifcationCompat builder.
I`m new in Android development. I work with Android version 4.x, and it has emulated web cam with very low resolution, like 640x480.
I need to make an emulated webcam so it will work in high-def modes, like (4320x2880). In android 2.x I used variables hw.camera.maxHorizontalPixels and hw.camera.maxVerticalPixels, but it looks like they don't work any more in Android 4.x emulator of webcam.
Please assist, how to set high-def camera resolution in new emulator.
Short form: there does not appear to be an option for this today.
Long form: devices.xml, in your Android directory (e.g., ~/.android/), uses this XML schema an XML schema that I cannot find anymore. The only configurable options for the camera appear to be location (front/back), flash, and autofocus. Since devices.xml is what now controls what your emulator behaves like, it would appear that there is no equivalent to the old resolution options.
I just put an app on the market and it is showing on all phones I have except for my Acer Liquid Mini. This one:
http://www.gsmarena.com/acer_liquid_mini_e310-3711.php
I have phones with the same res screens, Android 2.2, and close enough to the same hardware specs yet this is the only phone that it doesn't show for. It is running on factory defaults. When I try to install by the browser Google just says that the app isn't compatible and no more information.
I have the minSDK set to 4, maxSDK set to 10, I'm not specifying any screen resolutions in the Manifest (as recommended by the Android Doc post Android 1.6) and install location is set to "auto".
Does anyone have any ideas?
Apparently Google has problems with knowing the hardware constraints on some devices, such as this one, my Desire with the 2.3 upgrade and my Irish Galaxy 10.1" tab. They are working to sort it out
You could try deploying you app on appslib, they got a list of devices supported. You can choose a set of features required by your app and see the devices that will be able to run it.
I can't promise that both Android Market and appslib will give you the same results, i.e. will associate a device to the same requirements but that's a track to follow.