If i develop an app for amazon fire stick but I don't have a Fire stick so how can I check my app?
Is there any emulator for Amazon fire stick ?
When you use regular Android Emulator it's not acting as real firestick device. You will get some new issues with your app when running on Fire OS. So better to use real device and connect that through adb.
See this post on the Amazon Developer docs for some pointers on how to get it working in the emulator. There are some limitations, and from experience I'd probably recommend getting one to work with if you're going to be doing much work with it
Yes, you can create an Android TV emulator and run your app inside it. Follow these steps here: https://developer.amazon.com/docs/fire-app-builder/use-an-android-tv-emulator.html
Related
When im run android studio, or run emulator for android studio with manually or with cmd, always get bluescreen.
it say "your pc ran into problem and needs to restart. we're just collecting some error info, and then we'll restart for you"
Stop code: IRQL Not Less or Equal
how can i fix it ?
im trying download another emulator and following tutorial on youtube, but it didn't work
It depends on various factor,
I happened to get this issue because of my old PC with Lesser RAM size(4GB) and to rectify it, I connected my Android phone to PC for debugging/running apps from Android Studio.
You need to enable USB Debugging in your phone for that purpose.
NOTE:
You can view this blog post I made, which addresses the same issue.
https://whysurfswim.com/2015/07/11/sick-of-your-avd-theres-a-alternate-for-it/
I had almost same problem. When I tried to install my app in emulator(Ram 8gb), my emulator crashes but kept running in background. As a result, I was unable to shut down my pc and have to disconnect power for shutting down.
use your phone for debugging your app. you can connect your phone using wifi. link here
Sometimes it happens beacause of outdated drivers, try updating your drivers to latest version, and update the windows 10 to latest version. Also try by deleteing your current emulator device and create new device by enabling software renderer. For lower end pcs like yours I would recommend to use real device instead of emulators ans use ssds for better performances.
I am using AWS Workspaces to build an Android App. Everything works great and the speed with which I am able to work is just wonderful. However, one of the major issue I face is that I am unable to Debug my Apps via using USB debugging.
Now I understand that use of AWS Amazon Workspace in such a scenario is bit unusual but I have to use Workspaces for some reason.
Since Workspaces is a VM, so even the Android Emulator is not working.
Please let me know if any of you encountering similar problem and If you found some solution which can help to debug LIVE.
I am trying to set up multi-app kiosk mode on a Hololens headset and allow access to an app that I will be sideloading onto the Hololens. I've been using these guides to try and create a provisioning package, but I'm stuck on the part where I need to provide an AUMID for the app. This page is only useful for finding the AUMID of an app installed on a computer, how can I find it for an app installed on the Hololens, either once it is installed (using device portal), or from the finished Unity build or app package that I can generate from it?
I found an answer for this today as I was having the exact same problem.
Device portal is the best method for HoloLens that I know of.
Let's say you wanted Feedback Hub in your Multi App Kiosk.
You go to Device Portal > Apps > find your app in the drop down (in this example, feedback hub)
PackageFullName: Microsoft.WindowsFeedbackHub_1.1903.2331.0_x86__8wekyb3d8bbwe
Then you remove the version number and the build architecture. As well as extra underscores.
Microsoft.WindowsFeedbackHub_8wekyb3d8bbwe
Finally add on the !App
Microsoft.WindowsFeedbackHub_8wekyb3d8bbwe!App
If you find a way to find the AUMID from Unity before it's installed I'd like to know it.
I'm experiencing some problems while using the DocumentDB Emulator (v. 1.11.136.2).
I'm able to see the Explorer (https://localhost:8081/_explorer/index.html) but I cannot create any Database\Collection using either the Explorer and the SDK (I tried with the sample code provided by that page and my own code).
I always get:
{"readyState":4,"responseText":"{\"code\":\"ServiceUnavailable\",\"message\":\"Service is currently unavailable.\\r\\nActivityId: 9c9f56f8-91f9-4fad-b592-0c6bd5bbd300\"}","responseJSON":{"code":"ServiceUnavailable","message":"Service is currently unavailable.\r\nActivityId: 9c9f56f8-91f9-4fad-b592-0c6bd5bbd300"},
"status":503,
"statusText":"error"}
I'm running Windows 10. I already tried to restart the PC and reinstall the SDK\Emulator.
To fix this I had to perform a "Reset Data" on the Emulator.
This is probably due to some issue around updating from DocumentDb to Cosmo Db emulator.
Microsoft Support answer:
The failure is when the emulator tries to bring up the network stack.
We have seen this on some customer machines where 3rd network filter
drivers break some of the Windows networking APIs that we use.
Examples of these include drivers installed by Pulse Secure (or
Juniper network). I think we’ve also seen this type of failure with
some 3rd party antivirus products.
Typically uninstalling the 3rd party software should resolve the
issue.
I tried to change ConnectionMode to Gateway as
to
and it worked perfectly
and thank you for your time.
I am using Titanium Appcelerator to write an app for Android, and as compared to Windows, where the emulator was quite stable, in Linux I get the following symptoms:
emulator restart with no reason, sometimes after a runtime error, sometimes right after launching my app, and sometimes just right after booting completely after being launched
emulator informs that "process $1 is not responding", where $1 is generally the system process, but sometimes may be acore, or the calendar. This may happen while installing my app on the emulator, right after loading it, or right after unlocking the screen.
As it is easy to imagine, testing code like this can be quite difficult, so I was wondering, has anyone else stumbled upon this problem, and/or know how it could be solved?
Thank you very much in advance, and pls let me know of any info I should provide.
Leo
You should verify that the emulator is working fine without Appcelerator first. Definitely update to the latest SDK (r8) and create a new emulator AVD and see if the problem is there without Appcelerator.
I think I found a solution, but I don't claim it is universally valid: I just erased the virtual device created under Titanium, changed the project file for it to use SDK 1.4.2, and had it launched again under 1.4.2. It certainly didn't build my app, but at least it created a new virtual device, which I use now to build against 1.5.0, working like a charm so far.
Thanks again Manfred for pointing me in the right direction!