I've tried on at least 8 different current android emulators to install and run the Udemy android app, but in all of them I get "This app is incompatible with your device," in PlayStore.
I have some courses in Udemy that I'd like to download with subtitles and currently the only way that I know of of doing that is by downloading them in android. I don't own a smartphone.
One thing I've found common in all the latest emulators is that they all emulate some sort of tablet and not a phone, as I can see in settings that all of them have "About Tablet" at the bottom.
I was hoping if someone could tell me of any emulator that's based on a phone (preferable a Samsung one) rather than a tablet. Or any other way I could change the emulator to show as a phone in PlayStore?
I know this was posted some time ago and I am not sure if you came right, but the only way I have managed to get it working is by installing Android in a VMWare Player virtual machine.
The steps I used are as follows:
1) Downloaded the Android ISO from http://www.android-x86.org/download (I downloaded the android-x86_64-7.1-rc2.iso)
2) Downloaded VMWare player from www.vmware.com
3) Followed instructions on here https://www.tactig.com/install-android-nougat-vmware/
It is possible to install on Virtual box from what I see, but I have never tried it. Instructions are here: https://www.avoiderrors.net/install-android-7-0-nougat-virtualbox/
From there I was able to install the latest version of Udemy, only message I got was that it was not optimized for the device.
Hope this helps.
Related
I am making my first developer steps on Android.
Trying my first test app on an Android Virtual Device (AVD), I noticed that the device has almost no software on it, there is no Play Store and no Chrome Browser. See Screenshot. I checked all settings up and down but found no way to tweak the basic OS software load. I tried several phone models and API levels, but had no luck.
How can I create a device providing software support similar to a physical device, I do specifically need an Internet browser.
Google Play System Images
When creating the emulator, you need to select and create a system image that contains the playstore.
I'm trying to install a Google Play app on an Android emulator on a Windows 10 machine, but see the message "This app is not available for your device". I've tried creating different virtual devices (Pixel 3 w/Play Store, Pixel 4 w/Play Store, Nexus 5 w/Play Store, etc.) with different SDK versions (Android 9.0, 10.0, and 11.0) using both Android Studio and Visual Studio, but all result in the same message.
I've tried the "Clear Cache" and "Clear Storage" tricks on the virtual device's Google Play app, but that didn't work for me.
If I load Google Play Store in a Chrome browser and find the app, I get the same message, but I also see that my device that is incompatible is named "Google sdk_gphone_x86". I've also pulled up the same app in an Incognito browser window and it looks like it will install, but once I sign in to my Google account, I get the same message.
Other coworkers are able to install the app with a similar configuration so I know this app can be installed. It looks like it may be connected to my Google account.
Does anyone have any suggestions of what else to look at?
After several days of troubleshooting, I finally found the answer so I thought I'd post here for anyone else occasionally experiencing this problem.
For some reason, this particular app didn't work with Hyper-V hardware acceleration. In order to finally get it working, I disabled Hyper-V and installed HAXM instead.
I installed Xamarin Android Player a few days ago.
I installed Oracle VM VirtualBox, Xamarin for Visual Studio,...
I installed anything that Xamarin needs to work.
When I run Xamarin Android Player, I don't see any devices to download or update or install!
Here's a screenshot:
What should I do now?
I had the same situation.
In my case my system drive C:\ was lacking free space and when I cleaned it up a little bit to have at least 4GB free space, suddenly list was full of devices to download.
Yes, I know that this is a strange behavior...
Try it again with other client IP address. Maybe your IP is not available for download.
So i'm having awful trouble trying to get the Emulators in the Android SDK to start up. I can create the AVDs just fine, and then when hitting the 'start' button from the SDK Manager, bring up the small loading console window, indicating that the emulator is launching. However, after that, nothing happens!!
I have read many threads and posts with people having the same problem, maybe to do with the settings requiring too much memory, with some people waiting 30 minutes for the emulator to load!!
When trying to run the AVD emulator through terminal, I simply get a 'Bus Error' with no further indication of what could be going wrong...could it be a memory issue?
What I did to get where I am now:
Download the Android SDK package for Mac. I'm extracting the sdk only, not eclipse. I'm on Mac 10.6.8.
Install the SDK, and download the latest version of Android in the SDK Manager, along with default tools.
create a AVD and hit start.
window pops up to boot the emulator, that process is complete and window closes.
Nothing happens.
My knowledge of the sdk tools are very limited, all I want is to be able to do some testing...
Any help greatly appreciated!
Thanks
Actually, the simplest way to get emulators running right now is probably GenyMotion. They provide an interface, and pre-configured emulator images to make it pretty simple to get running.
This is not an endorsement (I use the standard ADT myself) but a lot of people find their tools useful.
Here is my suggestion: instead of using AVD, start using espresso and virtual remote android hardware emulator from Google servers - also known as android-test-kit. You will have the possibility to run and test you App on several different devices, without the need to spend money on actually all different devices for developing and testing purposes before releasing your Apps. You find further details here:
android-test-kit
Why Espresso
The 2 videos are somewhat long, but worth watching.
Taking this approach will solve your problem, save you money, and improve your productivity.
I run into the same issue on my mac 10.6 and it only works if i do
emulator64-x86 -avd my_android
Besides, my virtual device has to configured using x86 but not ARM
maybe this link can help you.
my problem : the app I have uploaded into my cellular device is shown without the pictures I have insert to it .
steps I have done in order to install:
I have inserted the xxx.apk file into the device via usb
I downloaded an apps installer via the Market
I opened the app using the installer and instead of picture an white background appeared
when I opened the xxx.apk file using file system I found the pictures.
note: even an application icon weren't appearing.
Apparently the res libary having problem to be bined to application.
I might ness to add something to my appliction manifest?
I might need to change something on my device ? (I already made a change and enabled user's not Market application )
I would be very grateful for some life saving answer I need to show my work in a few days in this is the first time i tested her on a real devise.
I also tried an example as shown in hello android book the same example worked perfectly on the emulator where on my android device (Motorola milestone ) the picture and icon weren't shown
Please tell me what I might be doing wrong guys I need to apply my project back at uni(I was the only one in uni who did it on android and in my country most of pep don't even know what android is so getting help outside of forum's like this is not an option ) so please please help me .
I don't know what app installer you downloaded from the Market, but you shouldn't need it. You should be installing the app to your phone using the same SDK tools you used to install it to the emulator. Ie, using Eclipse or the commandline "adb install" commmand.
I'm assuming you used the SDK tools to install the app to the emulators? In which case, start there. Start with looking at what you're doing different between when you installed unsuccessfully to your phone and when you installed to successfully to the SDK.
In my experiences so far, there should be very few differences between working with the emulator and working with the phone.
Well, something is wrong, but what is hard to tell from your question. What pictures are you talking about? Your drawable resources? My guess would be that your application works in the emulator (you have tested it?), but that it doesn't on the phone you're testing with. Have you checked the logcat output?
If you're developing from Eclipse, why not try a debugging session using the phone rather than the emulator?
Hard to narrow down without more details, but a few notes:
Pontus has a point - what's your logcat output? You can use logcat on a real device. Maybe not yours unless it's rooted, but with many phones you can.
Do you link the drawable to your app in the manifest file?
How do you test on emulator vs. device? Do you right-click the app and choose "Run As -> Android Application"? Do you do that for both emulator and device?
When you run on the device, do you first sign it? If so, can you verify the jar/apk and see the contents? Is the drawable under res/drawable?