Flex 4.6 Mobile App Install - android

I copied a tutorial like the simple Hello World App which I followed and created to try features on in Flex 4.6. It work it the emulator with the Flash Flex 4.6 software but when it cam to using / testing the simple App on a real phone there was a problem.
it installed on the HTC Wildfire S but when it came to running the app, there was a error with the following.
"The application HelloWorld(process air.HelloWorld has stopped unexpectedly. Please try again"
I am new to Flex but this error is making things harder, It seems this is a unknown error the code seem to be all correct I checked it with the tutorial.
The HTC That I tested on has the following os
Android version 2.3.5
Software number 2.13.206.1
Kernel version 2.6.35.10
Do you know any common reason for this error, the firmware is the latest 2.3.5
Thanks

If i could i would just comment this, but anyways...
I have few working Flex mobile apps which i tested on android devices. Yesterday i only had my friends HTC sense 2.3.3 (which i didnt used before) available for testing. None of my working AIR apps did work on that phone. I am always using captive runtime. App size is usually around 10 mb apk, and 20 mb when installed (even small hello world app always have about 20mb when installed with captive runtime). Strange thing is, that apps on HTC sense had only 10 mb after being installed - so there was clearly some problem with deploying captive runtime...
If your hello world works on flash builder simulator, then its probably some problem with device.
You should try another devices.
You should also check, if your app size is around 20mb...

Related

Running Augmented reality apps on Linux using emulator

In continuation with this question. I am asking this question.
I installed Android Studio. I installed Unity 3D. I followed tutorials of Java-Android Studio and Unity. Nothing worked well because of the reason that they need the latest version of ARCore and neither my mobile nor emulator is compatible with it. I am exhausted searching for alternatives.
I didn't find any tutorial or guidance related to developing Augmented Reality Android apps. Please suggest me a reference that works on Ubuntu system without the need of the physical mobile, but with an emulator, if possible.
Note: Please provide a reference that is relatively easy to test small app initially so that I can proceed forward. I am saying this because of the reason that I am working from almost 3 months but didn't run a small AR app either in the emulator or in my mobile (Redmi Note - 4).
You should check 8thWall. It runs on almost all phones and it has SLAM as well. You can not use it with emulator but it has an application called XR Remote in which you can test your code without building for Android or iOS. Minimum requirement for Android is Android Kitkat (4.4) or higher and for iOS Minimum iOS 7.0 or later is required.
As the owner of the question stated 8thWall can not be used with Linux. As an alternative [ARToolKit] can be used. It is an open source AR framework. For more details you can refer here and here

Android equivalent to iOS Simulator

The iOS simulator is great for testing websites locally on various Apple devices. Is there an Android equivalent?
I've tried Android studio, but I seem to have to build a device every time (unless I'm doing it wrong). I'm mainly concerned in seeing the sites in the default Chrome browser (Version 53, 59 etc).
What are you trying to test? An app or a website? If you have to "build a device" every time, you are doing it wrong.
The device emulator that you are using in android studio is the intended way to run android without a physical device. Ensure you have properly installed haxm if you are finding the emulator unbearably slow. It may help.
If you really want to try something else, you could try using the genymotion emulator. It is quite comparable to the official one though.

Cordova app crashing on Samsung Marshmallow phones

I'm trying to teach myself JavaScript by creating an little puzzle/game app with Cordova. I've got a basic prototype thing working, and have successfully got it to build on iPhone, and it runs perfectly.
I have 3 android phones to test with, 1 Marshmallow (BLU branded), 1 Lollipop, and 1 Kitkat... and the app works perfectly on those as well. I sent the app to 2 friends on the other side of the country to test, and it crashes on their Samsung Marshmallow phones ( a Galaxy 7, and a Galaxy Edge 7). It runs for a bit, and then just crashes without any user input.
So, I tried 2 separate crash analytics plugins, Fabric and Crittercism. I can verify that both of these are working, as I can force a crash in the app, and it shows up as a crash report.
But when my friends run the app with the crash analytics, whatever is going on that makes the app blowup, it isn't triggering any reports from Fabric or Crittercism. I've tried to get the android emulator running on my PC, but unfortunately it is an AMD processor, which is missing some necessary virtualization. I can't even get the super slow ARM version of the emulator to run on my PC, it just hangs forever.
I just recently installed cordova, and took all the defaults during setup. So from what I can tell, it should be targeting android API 23 (Marshmallow). But maybe there's some other kind of build issue that is messing things up?
So I'm kind of at a loss of how to debug this problem. Short of finding someone locally who can lend me a Samsung Marshmallow phone to debug with, I can't think of anything else that would work. Does anyone have any ideas?
The ARM emulator is indeed excruciatingly slow. I would suggest a third-party emulator. I use GenyMotion (which uses VirtualBox under the hood). You might have some luck with that. Alternatively, ManyMo is a cloud-based solution that might prove useful.
The system web view used by PhoneGap/Cordova will vary widely across Android devices, which means you can run into different issues across Android versions and device manufacturers. I suggest using the Crosswalk plugin to mitigate those problems. Do note that this will increase the size of your APK and footprint of the installed app on your device.
When the app crashes, does it actually crash to the launcher, or does the app reload itself (or just show a background color)? I wouldn't expect Crashlytics to handle JavaScript issues unless the JavaScript caused the app to crash out to the launcher.

How can websites be tested in Android browsers on Windows?

Do I need to install an emulator of some sort? Are there any online services that offer this? I've found little guidance elsewhere on this matter. I'm on Windows 8, just trying to figure out (locally) why my android users are experiencing issues with an MVC app.
The easiest way would be to download and install the Android SDK and use the emulator to try and reproduce the problem. The SDK has emulator images for all versions of Android, and you can create devices with different screens (resolution/dpi/size), so if your site uses responsive design you can test also how it scales across different devices and whether the problem affects one specific or all Android devices.
However, it is possible that the emulator might not be good enough for reproducing and understanding the problem. The Android SDK images come with the browser that is part of the Android Open Source Project (AOSP). While this browser is technically based on WebKit, it is based on a rather old version of it. Most OEMs that have built Android devices have signed the Google Mobile Services (GMS) license ship on their devices the Google suite of apps which includes the latest version of Chrome, which is based on the most recent WebKit version. The difference in the behavior between the two browsers is rather big.
So if the problem turns out to be with Chrome instead of the AOSP Browser, you will have to buy a real device and test on it. Depending on the budget you have and whether you want a phone or a tablet, you can go with a Nexus 5 ($350 w/o contract), Nexus 7 ($230 wifi only), or a Moto G ($175 w/o contract). Of course, you could also buy Samsung Galaxy S4, HTC One X, or a Moto X, but they all will cost you more.
It might be worth also borrowing from someone a Samsung Galaxy Ace 2, or equivalent low end MDPI device.
well, you can install an android emulator and use the browser there (http://developer.android.com/tools/devices/index.html), but it's extremely slow,
so you should, instead, try Genymotion. It's an android virtual machine and it's pretty smooth. (http://www.genymotion.com/)
another option, is the Opera mobile emulator, but that is specifically for the mobile Opera browser. (http://www.opera.com/developer/mobile-emulator)
if you want a chrome specific approach, try this (https://developers.google.com/chrome-developer-tools/docs/mobile-emulation)
http://developer.android.com/sdk/index.html has the emulators.
… but it may be just as cost-effective to just spring the $40 for a cheap Android tablet with WiFi.

Target-specific emulators for Eclipse in Android?

I'm an Android newbie just getting past "hello world" in Eclipse. I was at the Verizon store today trying out 4 different Android phones for my next upgrade and I realized how DIFFERENT they all are even though they're all 2.1 or 2.2.
Short of buying an expensive collection of Android phones from different vendors, is there a way to EMULATE some of the major phones like HTC Incredible or Droid X in my Eclipse IDE?
How bad is the Android fragmentation problem I read about on blogs? When I write an app for a PC I don't have to worry about whether it's a Toshiba PC or an Acer or a Dell. How much do I need to worry about Droid 2 -vs- Droid X - vs HTC Incredible?
Thanks in advance!
Here is a link to a similar question with information on how to create emulators in Eclipse.
Essentially you just create an Android Virtual Device with the same screen resolution and OS version as the device you want to target.
Here is great blog post by Adam Powell on the official Android Developer Blog about the completely over-hyped fragmentation "issue", and what you can do to make sure your app runs on almost every Android device.

Categories

Resources