I'm trying to use readium 2 library for my android project. I cloned r2-workspace-kotlin repo. I launched the app on some of my test devices. I noticed that on one device the app is unable to render some pages. Instead of what should be a page of the book I get a page saying Webpage not available. The device is running android 7.1.2 but it's not related to android version as I tested the app on emulator running the same version and it worked. Anyone has any ideas how to fix it?
Related
I am new to mobile development, a few days ago i install Xamarin and Android SDK. I have just created a blank app and when i try to run it says built was unsuccessful and shows the above message.
But when i open the main.axml i can see Nexus one with android 7.1 is selected. I did change these option but the same error.
I did try everything mentioned here on stackoverflow and on Xamarin but none worked for me. i did update Xamarin and downgrade JDK to 8 from 9 as it was mentioned somewhere on the blog but still i am out of luck. its been more than 5 days i am trying different solutions and finally i have to put it in front of the professionals.
Its just an empty app not even a single line of code.
I can give teamviewer access if necessary.
Thanks.
You must install an emulator on which you will run the application. Or connect physical device. There is nothing to do with Xamarin or SDK versions. Your app compiles OK. You just need some device (virtual or physical) to run your application.
My question is similar to ionic-mobile-app-gives-white-screen
I have created one ionic app that runs perfectly fine in a browser, but when I convert it into an app I am getting a white screen.
I have already installed the white list plugin and allowed all urls in the config. I also have kept the meta tag.
This is one ionic 2 application.
It runs perfectly in web and on all Android devices when I use ionic 1.
But, I can use Android 5.0 or higher version to run ionic2.
I have tried many methods such as how-to-debug-the-white-screen-of-death-in-your-ionic-app, but i can't inspect button for my debug
chrome inspect.
My android device: genymotion, htc one, running Android 4.3 (API 18).
When using Visual Studio 2015 to develop c++ for Android the emulator only works if you are running a Pro version of Windows, for those using Visual Studio Community who are probably also running on a Home version of windows (like me) the Emulator will not work.
Is there an alternative available that can integrate with the VS debugger?
*** Edit
I have been looking at this list Android emulators although this seems to be aimed at android gaming on PC rather than App development. So was wondering if anyone had managed to integrate one of these with Visual Studio?
Both the below options come with the caveat that I have not used either.
Xamarin Android Player
Apparently Xamarin had issues with the default Android Emulator. Primarily that it was slow, and clunky, and they were getting a lot of complaints about it from Xamarin users (despite it not being their product/fault).
They decided to create their own emulator to get around this, and it can be found here.
It should be noted that (at time of writing) this is still in Preview by the looks of things. So bugs may be present.
From what I can see on the download page, it doesn't appear like you need Xamarin to actually use it. In any case, it's worth a shot.
GenyMotion
Another option is GenyMotion. There is a free version for personal use only (with limited functionality), or a paid option that provides more capability.
Android player link has changed to here: https://developer.xamarin.com/releases/android/android-player/
I had problems starting the android VMs, even after restarting the host. There seems to be some incompatibilities between Windows 10 Home and Virtualbox 5.0.4 that Android player installs. Installing Virtuallbox 5.1.2 after installing Android player seems to have resolved this.
EDIT: I haven't had a chance to test integration with Visual Studio yet.
Everything seems to be working as expected within Visual Studio. Both of the VM devices I created in Android Player are visible in the drop down of the run menu. Visual Studio will start the selected VM when I debug the default blank android app.
The only hiccup is that Visual Studio doesn't wait long enough for the emulator to start before attempting to deploy the app. So I have to start the run again or remember to start the VM from Android Player before debugging.
I have tried all the possible available online solutions to install Google Play services and ARM translation v1.1 on my Genymotion 2.3.0 version with Android Studio but I am not able to flash the downloaded zip. I have also tried multiple emulators 4.2.2 and 4.4.4 Android release version Genymotion devices. I tried the instructions mentioned at the following link :
http://forum.xda-developers.com/showthread.php?t=2528952%5d
Specifically I am stuck at the point It should say "File transfer in progress", once it asks you to flash it click "OK". Since the emulator never asks me to flash the ARM translation file but simply copies it to the /sdcard/download.
I am basically trying to start a login activity with Google Plus. I got the sample code from here. I also tried using the default login activity that is provided but Android Studio but it does not seem to work.
FYI I have a MacBook Pro and recently upgraded my OS to OS X Yosemite.
I managed to solve this myself. This is an issue with Mac only. Following are the errors and there solution :
Error 1. Files copied to /sdcard/downloads
Solution - uncheck the Safri->preferences->general->open "safe" files after downloading.
Why : Safari unzips the downloaded file which renders it useless to be flashed onto Genymotion.
Error 2: Failed to Deploy file
Solution - restart your Macbook (not your Genymotion). This seems to be an issue when you put the macbook to sleep with Genymotion Emulator in ON state.
Why : There seems to be some issue with Genymotion and Android Studio connection after Macbook mwake-up from Sleep state.
I want to be able to test the web based app that I am developing in the new Chrome for Android. I did install the Chrome Beta apk but every time I tried to type a URL in the address bar, the browser crashed saying "Unfortunately Chrome has stopped running".
I don't own a SmartPhone, but I need to test because my client will be using devices running Android 4+
I am running Android Emulator on OSX Lion 10.7.4. My Emulator specs:
Model #: sdk
Android version: 4.1.1
Kernel version: 2.6.29-gc497e41
Build #: sdk-eng 4.1.1 JRO03E 403059 test-keys
Apparently, the only way to get the new Chrome is through the Google Play App, which isn't a default app that comes with the emulator, so I installed and ran the Google Play App by following the instructions from this post here: Google Play on Android 4.0 emulator
I had to do a search for Chrome from within the Play Store App. Once found, it said incompatible with my device and had no button to download it.
Info about the Chrome Browser for Android from the Play site:
CURRENT VERSION:
18.0.1025308
REQUIRES ANDROID:
4.0 and up
Is there anyway to get the latest Chrome running on my emulator? When will Android Emulator developers be able to test and develop in the newly released Chrome for Android?
Response from deejoy at http://blog.apkudo.com/2012/08/08/run-google-play-on-an-emulator-and-pretend-to-be-any-device/
...I did manage to get the latest chrome downloaded and installed on my emulator. However, when I run Chrome on the emulator I'm met with the following error:
[ERROR:context_group.cc(83)] ContextGroup::Initialize failed
because too few vertex attributes supported.
So, what does that mean? Long story short, my emulator (even with OpenGL acceleration) does not support the required number of vertex attributes to run Chrome. You can take a look at Chrome's source code here: http://code.google.com/p/chromium/source/search?q=context_group.cc&origq=context_group.cc&btnG=Search+Trunk
Somewhere in context_group.cc (not necessarily line 83) you'll see an explicit check for the number of available vertex attributes and the offending error message. As far as I know, theres not much you can do (if anything) to get past this error.